design-sprint
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 int
npx skills add wondelai/skills --skill design-sprint --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Design Sprint Framework A five-day process for answering critical business questions through design, prototyping, and testing ideas with customers. Developed at Google Ventures and used by Google, Slack, Airbnb, and hundreds of startups. ## Core Principle **Compress months of debate, design, and testing into one week — and test with real users before writing any production code.** The sprint replaces endless discussion with a fixed Monday-to-Friday spine, hard time-boxes, and a single Decider, so a high-stakes product question gets a real answer in five days instead of five months. ## Scoring **Goal: 10/10.** Score a sprint plan or execution by awarding 1 point for each item present and correct (10 total). Report the score and the missing items needed to reach 10/10. 1. Decider committed for the full week; one Sprint Master facilitating. 2. Monday produces a target customer and moment (not a vague "test the product"). 3. Hard time-boxes used (Crazy 8s in 8 min, 10am-5pm days, no open-ended sessions). 4. Solution sketches done alone and anonymous — no group brainstorming. 5. Wednesday ends with a single Decider Supervote, not consensus. 6. Storyboard specified before any prototype
- Core Principle
- Scoring
- The 5-Day Sprint Process
- Monday: Map
- Morning: Start at the End
- Afternoon: Map the Challenge
- End of Day: Pick a Target
- Tuesday: Sketch
- Morning: Lightning Demos
- Afternoon: The Four-Step Sketch
- Wednesday: Decide
- Morning: Sticky Decision
- Afternoon: Rumble or All-in-One
- Thursday: Prototype
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 int
How do I install it?
Run `npx skills add wondelai/skills --skill design-sprint --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From wondelai/skills, a repository with 1,835 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.