design-sprint
design sprint
What it does
- Long-term goal: Write the optimistic answer to "What do we want to be true in 2 years?" — e.g., "Customers use our product daily."
- Sprint questions: List obstacles and unknowns as questions on the whiteboard, whole team contributing — e.g., "Will customers trust us with payment info?"
- Ask the Experts: Interview teammates with specialized knowledge (CEO, design, engineering, support, sales); capture notes on the whiteboard.
- Divide or swarm: Split the map between people if it has multiple parts; otherwise everyone tackles the same critical problem (most sprints swarm).
- Art museum: Tape sketches to the wall; review silently (no talking) and mark interesting parts with dot stickers.
- Straw poll: Each person votes for one solution with one sentence of rationale (non-binding).
- Supervote: The Decider gets three large dots; their decision wins.
Requirements & configuration
- Goal: Build a realistic facade in one day — you need something to test on Friday.
- Don't run when: the problem and solution are obvious and you just need to execute, the team isn't bought in, or you can't get the Decider for the full week.
- See references/case-studies.md for worked sprint walk-throughs (Slack, Blue Bottle Coffee, Savioke and more) when you need a concrete precedent for how a sprint played out in a domain like yours.
Derived from the skill's own SKILL.md documentation · extracted 2026-07-23
design-sprint FAQ
What does the design-sprint skill do?
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product decision, or wants to de-risk a costly idea before investing in development. Covers mapping, sketching, deciding, prototyping, and testing across Monday-Friday. For ongoing experimentation and MVPs, see lean-startup. For customer job analysis, see jobs-to-be-done. For non-leading user interviews, see mom-test. Long-term goal: Write the optimistic answer to "What do we want to be true in 2 years?" — e.g., "Customers use our product daily." Sprint questions: List obstacles and unknowns as questions on the whiteboard, whole team contributing — e.g., "Will customers trust us with payment info?"
What does design-sprint require?
Goal: Build a realistic facade in one day — you need something to test on Friday. Don't run when: the problem and solution are obvious and you just need to execute, the team isn't bought in, or you can't get the Decider for the full week. See references/case-studies.md for worked sprint walk-throughs (Slack, Blue Bottle Coffee, Savioke and more) when you need a concrete precedent for how a sprint played out in a domain like yours.
How do I install design-sprint?
Run: npx -y skills add https://github.com/wondelai/skills --skill design-sprint --agent claude-code — the source lives at github.com/wondelai/skills.
Maintain design-sprint?
Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.
[design-sprint on getagentictools](https://getagentictools.com/skills/wondelai-skills-design-sprint?ref=badge) npx agentictools info skills/wondelai-skills-design-sprint The second line is the CLI lookup for this page — handy in READMEs and docs.
