Agent skill · wondelai
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 interviews, see mom-test.
What it needs
About 9k tokens when loaded.
What this skill does
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 is built. 7. Prototype is a Goldilocks-fidelity facade, testable in 5-15 min, with a trial run done. 8. Exactly 5 target users recruited via screener (6 scheduled to absorb a no-show). 9. Friday uses the Five-Act Interview; users interpret the prototype unexplained. 10. End-of-sprint debrief converts the +/-/~ pattern grid into a decision on next steps. A plan missing the Decider, real users, or a same-day prototype caps at 6 — those are the failure modes the sprint exists to prevent. The 5-Day Sprint Process Prerequisites: a big challenge worth a week's focus; the right team (Decider plus 4-7 people with diverse expertise); five full days (10am-5pm) with no interruptions; a dedicated room with whiteboards. One Sprint Master facilitates, keeps time, and manages energy. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills wondelai/design-sprint--03c67f