design-sprint

design-sprint is a command for Claude Code from Adityaraj0421/naksha-studio. It costs 30 tokens per session (2,579 once invoked), scanned A, original, MIT.

A five-step design process for understanding a problem, exploring ideas, choosing a direction, making a prototype, and planning tests. A prototype is an early version used to check an idea before building it fully.

In plain words
What is it for?
Use it to frame product problems, generate and compare solutions, plan a quick prototype, and prepare user testing.
Why use it?
It gives a team a clear way to move from an unclear design problem to a testable solution. It also makes decisions and next steps explicit.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

Good fit Use it to frame product problems, generate and compare solutions, plan a quick prototype, and prepare user testing.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Adityaraj0421/naksha-studio
Claude Code
/plugin install naksha-studio

Made for: Claude Code.

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for design-sprint

README.md
[![agentmods](https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-sprint/github.svg)](https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-sprint)
Your own site
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-sprint"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-sprint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for design-sprint

Your own site · 80×15
<a href="https://agentmods.dev/commands/adityaraj0421/naksha-studio/design-sprint"><img src="https://agentmods.dev/badge/commands/adityaraj0421/naksha-studio/design-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,579 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00030 $0.02579
Opus 5 $0.00015 $0.01290
Sonnet 5 $0.00006 $0.00516
Haiku 4.5 $0.00003 $0.00258

Measured 9d ago against content hash b9ac2d80caa6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

design-sprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/design-sprint.md · 346 lines

How it starts

The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/design-sprint

You are facilitating a design sprint — a structured, time-boxed process for rapidly solving design problems. Adapted from the Google Ventures design sprint methodology for AI-assisted design.

Input: $ARGUMENTS

Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/product-designer.md for product strategy, ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ux-designer.md for UX methodology, and ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ux-researcher.md for research frameworks.

The 5 Phases

Phase 1: UNDERSTAND    → Map the problem space
Phase 2: DIVERGE       → Generate multiple solutions
Phase 3: DECIDE        → Pick the strongest direction
Phase 4: PROTOTYPE     → Build a testable solution
Phase 5: VALIDATE      → Create a testing plan

Phase 1: UNDERSTAND (Map the Problem)

1.1 Problem Statement

Structure the user's input into a clear problem statement:

## Problem Statement

**Who**: [Target users]
**What**: [The problem they face]
**Where**: [Context — when/where does this happen]
**Why it matters**: [Business/user impact]
**Current state**: [How it's handled today, if at all]

### Long-Term Goal
"In [timeframe], [users] will be able to [outcome] instead of [current pain]."

### Sprint Question
"Can we [specific hypothesis to test]?"

1.2 User Journey Map

Map the current user experience:

### User Journey: [Persona Name]

| Stage | Action | Thinking | Feeling | Pain Points |
|-------|--------|---------|---------|-------------|
| Discover | [how they find the product] | | | |
| Evaluate | [how they assess value] | | | |
| Onboard | [first experience] | | | |
| Use | [core task flow] | | | |
| Return | [what brings them back] | | | |

1.3 Opportunity Map

Identify the highest-impact areas:

### Opportunity Mapping

| Opportunity | User Impact | Business Impact | Effort | Score |
|-------------|------------|-----------------|--------|-------|
| [Opp 1] | High | High | Medium | ⭐⭐⭐ |
| [Opp 2] | Medium | High | Low | ⭐⭐⭐ |
| [Opp 3] | High | Medium | High | ⭐⭐ |

**Selected Focus**: [highest-scored opportunity]

Read the full file on GitHub · 346 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 346 lines · 30 tokens per session scan A b9ac2d80caa6

Subscribe to this mod's changes

design-sprint is a command published in the GitHub repository Adityaraj0421/naksha-studio (317 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 2,579 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.