[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7389WZCBK18P9ABEECF0FVD":3,"skill-same:01M7389WZCBK18P9ABEECF0FVD":87},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7389WZCBK18P9ABEECF0FVD","design-sprint",null,"Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development. Use when: **New product concepts** that need validation before building; **Big feature decisions** with significant investment required; **Stuck teams** needing to break through analysis paralysis; **Startup pivots** when direction is uncertain; **High-risk bets** where failure is expensive","roohe\u002Fagentic-super-skills","roohe","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99054084?v=4","01M734WCDFP6RZVT5CNM00QR26","01M734WCE4BD0T4NZS5PCV9V5F",10,"MIT","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: design-sprint\ndescription: \"Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development. Use when: **New product concepts** that need validation before building; **Big feature decisions** with significant investment required; **Stuck teams** needing to break through analysis paralysis; **Startup pivots** when direction is uncertain; **High-risk bets** where failure is expensive\"\nlicense: MIT\nmetadata:\n  author: ClawFu\n  version: 1.0.0\n  mcp-server: \"@clawfu\u002Fmcp-skills\"\n---\n\n# Design Sprint\n\n> Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development.\n\n## When to Use This Skill\n\n- **New product concepts** that need validation before building\n- **Big feature decisions** with significant investment required\n- **Stuck teams** needing to break through analysis paralysis\n- **Startup pivots** when direction is uncertain\n- **High-risk bets** where failure is expensive\n- **Cross-functional alignment** when teams disagree on direction\n\n## Methodology Foundation\n\n| Aspect | Details |\n|--------|---------|\n| **Source** | Jake Knapp - Sprint (2016), developed at Google Ventures |\n| **Core Principle** | \"5 days to go from problem to tested solution. Prototype and test with real users instead of debating and building.\" |\n| **Validation** | Used in 150+ startups by GV, adopted by teams at Google, Slack, Uber, IDEO |\n| **Why This Matters** | Months of work compressed into a week. Learn in 5 days what would take months to discover after launch. |\n\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Structures video workflow | Final creative vision |\n| Suggests shot compositions | Equipment selection |\n| Creates storyboard templates | Brand aesthetics |\n| Generates script frameworks | Final approval |\n| Identifies technical requirements | Budget allocation |\n\n## What This Skill Does\n\n1. **Structures a 5-day process** - Monday to Friday, full schedule\n2. **Facilitates divergent thinking** - Generate many ideas\n3. **Enables rapid prototyping** - Realistic but fake\n4. **Validates with real users** - Test on Friday\n5. **Aligns teams quickly** - Shared understanding and decision\n6. **Reduces risk** - Learn before you build\n\n## How to Use\n\n### Plan a Design Sprint\n```\nI want to run a design sprint to solve [challenge].\nHelp me plan the 5-day schedule and prepare materials.\nTeam: [who's involved]\n```\n\n### Run a Specific Sprint Day\n```\nWe're on [Day] of our design sprint.\nGuide me through today's activities for [challenge].\n```\n\n### Adapt for Remote\u002FCompressed Sprint\n```\nI need to run a design sprint remotely [or: in 3 days instead of 5].\nHelp me adapt the methodology.\n```\n\n## Instructions\n\n### Step 1: Understand the Sprint Overview\n\n```\n## The 5-Day Sprint\n\n### Why 5 Days?\n\n**Day 1 (Monday): Map**\nUnderstand the problem and pick a target\n\n**Day 2 (Tuesday): Sketch**\nGenerate solutions individually\n\n**Day 3 (Wednesday): Decide**\nChoose the best solution\n\n**Day 4 (Thursday): Prototype**\nBuild a realistic facade\n\n**Day 5 (Friday): Test**\nGet real user feedback\n\n### The Philosophy\n\n**Before sprints:**\n- Debate ideas for weeks\n- Build something over months\n- Launch and hope\n- Discover problems late\n\n**With sprints:**\n- 1 day to understand\n- 2 days to generate and decide\n- 1 day to prototype\n- 1 day to validate\n- Learn before building\n\n### What You Need\n\n**Team (7 or fewer):**\n- Decider (authority to make calls)\n- Facilitator (runs the sprint)\n- Product person\n- Designer\n- Engineer\n- Domain expert\n- Customer-facing person\n\n**Space:**\n- Dedicated room for 5 days\n- Whiteboards or wall space\n- Post-its, markers, dot stickers\n\n**Prep:**\n- 5 user interviews scheduled for Friday\n- Sprint challenge defined\n- Long-term goal agreed\n```\n\n---\n\n### Step 2: Day-by-Day Activities\n\n```\n## Monday: Map\n\n### Goal\nUnderstand the problem. Pick where to focus.\n\n### Schedule\n\n**10:00 - Long-term goal**\n\"Where do we want to be in 6 months \u002F 2 years?\"\nWrite on whiteboard. Get Decider agreement.\n\n**10:30 - Sprint questions**\n\"What could go wrong? What do we need to learn?\"\nTurn fears into questions.\n\"Will users understand our value prop?\"\n\"Can we convert free users to paid?\"\n\n**11:00 - Make a map**\nCustomer journey map:\n```\n[Actor] → [Action 1] → [Action 2] → [Goal]\n               ↓            ↓\n         [Touchpoint]  [Touchpoint]\n```\n\nSimple is better. Show how customers interact.\n\n**1:00 - Ask the experts**\nInterview team members and stakeholders.\n20 minutes each. \"How Might We\" notes.\n\n**How Might We (HMW):**\nTurn problems into opportunities.\nProblem: \"Users don't understand pricing\"\nHMW: \"How might we make pricing instantly clear?\"\n\n**3:30 - Organize HMWs**\nAffinity map the HMW notes.\nDot vote on most important.\n\n**4:30 - Pick a target**\nChoose ONE part of the map to focus on.\nDecider makes the call.\n\n### Monday Output\n- Long-term goal on wall\n- Sprint questions on wall\n- Map on wall\n- Target circled on map\n```\n\n---\n\n```\n## Tuesday: Sketch\n\n### Goal\nGenerate solutions. Everyone contributes.\n\n### Schedule\n\n**10:00 - Lightning demos**\nShow inspiring solutions from other products\u002Findustries.\n3 minutes each. Capture \"Big Ideas\" on post-its.\n\n**11:30 - Divide or swarm**\nIf multiple targets, assign team members to each.\nIf one target, everyone tackles it.\n\n**1:00 - Four-step sketch (individual work)**\n\n**Step 1: Notes (20 min)**\nWalk around room. Take notes on what's there.\nReview goals, map, HMWs, demos.\n\n**Step 2: Ideas (20 min)**\nWrite rough ideas. No polish.\nQuantity over quality.\n\n**Step 3: Crazy 8s (8 min)**\nFold paper into 8 sections.\n1 minute per section: sketch a variation.\nForces rapid iteration.\n\n**Step 4: Solution sketch (30-90 min)**\nCreate a 3-panel storyboard.\nSelf-explanatory (words + pictures).\nAnonymous (no names).\n\n**Key rules:**\n- Work alone (no groupthink)\n- No collaboration yet\n- Keep sketches anonymous\n- Must be self-explanatory\n\n### Tuesday Output\n- Solution sketches from each person\n- Posted on wall, face out\n```\n\n---\n\n```\n## Wednesday: Decide\n\n### Goal\nChoose one solution to prototype.\n\n### Schedule\n\n**10:00 - Art museum**\nPost all sketches on wall.\nTeam walks around in silence (no pitching).\n\n**10:30 - Heat map**\nDot vote silently on interesting parts.\nNo discussion. Cluster votes reveal consensus.\n\n**11:00 - Speed critique**\n3 minutes per sketch.\nFacilitator narrates. Team discusses.\nCapture standout ideas.\n\n**11:45 - Straw poll**\nEach person votes for ONE solution.\n(Not binding, just gauging sentiment)\n\n**12:00 - Supervote**\nDecider gets 3 special votes.\nDecider's votes decide what gets prototyped.\n\n**Why Decider decides:**\n- Faster than consensus\n- One person is accountable\n- Avoids design-by-committee\n\n**1:30 - Rumble or All-in-one?**\nIf votes cluster on one idea: All-in-one prototype\nIf votes split: Can we combine? Or do we rumble (test both)?\n\n**2:00 - Storyboard**\nDraw the prototype frame-by-frame.\nWhat does the user see at each step?\n\n```\n[Frame 1]    [Frame 2]    [Frame 3]    [Frame 4]\nOpening      Key action   Result       End state\nscene\n```\n\n15-20 frames typical. Detail matters.\n\n### Wednesday Output\n- Winner(s) chosen\n- Detailed storyboard ready for prototype\n```\n\n---\n\n```\n## Thursday: Prototype\n\n### Goal\nBuild something real enough to test.\n\n### Schedule\n\n**Full day: Build the prototype**\n\n### The Prototype Mindset\n\n**Not building:**\n- A real product\n- Code\n- Anything that works\n\n**Building:**\n- A facade\n- Realistic enough to get real reactions\n- Goldilocks quality (just right)\n\n### Goldilocks Quality\n\n**Too low:** User can't engage, doesn't feel real\n**Too high:** Takes too long, you get attached\n**Just right:** Real enough to react to, fake enough to be fast\n\n### Division of Labor\n\n**Makers (2+):**\nBuild the screens\u002Fassets\n\n**Stitcher (1):**\nAssemble into clickable flow\n\n**Writer (1):**\nAll the copy and content\n\n**Asset collector (1):**\nStock photos, logos, icons\n\n**Interviewer (1):**\nPrep Friday's interview script\n\n### Tools\n\n| Prototype Type | Tools |\n|----------------|-------|\n| Digital product | Figma, Keynote, InVision |\n| Physical product | 3D print, foam, paper |\n| Service | Role-play script, fake storefront |\n| Marketing | Landing page, fake ads |\n\n### Thursday Tips\n\n- Start with hardest screens first\n- Writer writes real copy (not Lorem Ipsum)\n- Error states matter\n- Have something testable by 3pm\n- Do a trial run at 4pm\n- Fix issues before Friday\n\n### Thursday Output\n- Clickable\u002Fusable prototype\n- Interview script ready\n- 5 users confirmed for Friday\n```\n\n---\n\n```\n## Friday: Test\n\n### Goal\nLearn from real users.\n\n### Schedule\n\n**9:00 - Prep**\n- Prototype working\n- Interview room ready\n- Observation room set up (team watches)\n\n**10:00-3:00 - Five user interviews**\n1 hour each. 30 minutes between.\n\n**Interview structure:**\n1. Friendly welcome (5 min)\n2. Context questions (10 min)\n3. Prototype walkthrough (40 min)\n4. Debrief (5 min)\n\n**3:30-5:00 - Review and learn**\n- Look for patterns\n- What worked?\n- What didn't?\n- What surprised us?\n\n### Watching the Interviews\n\n**Team watches from another room**\n- Video feed or live stream\n- No interrupting\n\n**Note-taking:**\nEach watcher takes notes on:\n- Positive reactions (+)\n- Negative reactions (-)\n- Quotes\n- Questions\n\n**Use a grid:**\n```\n           | User 1 | User 2 | User 3 | User 4 | User 5\n-----------|--------|--------|--------|--------|--------\nFeature A  | + Easy | + Easy | - Conf | + Easy | + Easy\nFeature B  | - Lost | - Lost | - Lost | + OK   | - Lost\n```\n\nPatterns become obvious.\n\n### 5 Is Enough\n\nWhy 5 users?\n- 85% of issues found with 5 users\n- Diminishing returns after 5\n- Can recruit in a week\n- One day of testing\n\n### Friday Output\n- Patterns documented\n- Decisions on what to build\n- Next steps clear\n```\n\n---\n\n### Step 3: After the Sprint\n\n```\n## What Happens Next\n\n### Possible Outcomes\n\n**1. Big hit (everything worked)**\n- Move to build with confidence\n- Scope based on prototype\n- High conviction, low risk\n\n**2. Flawed but promising**\n- Know what to fix\n- Might need mini-sprint on problem area\n- Build core, iterate on issues\n\n**3. Mixed results**\n- Some things worked, some didn't\n- Consider pivot or scope reduction\n- Another sprint on specific problem?\n\n**4. Complete miss**\n- Wrong problem or wrong solution\n- Better to know now than after building\n- Reframe and try again\n\n### Turn Learning into Action\n\n**If building:**\n1. Turn storyboard into spec\n2. Engineers can start from prototype\n3. Validated design reduces back-and-forth\n\n**If pivoting:**\n1. What did we learn?\n2. What's the new hypothesis?\n3. Next sprint or different approach?\n\n### Document the Sprint\n\n**Sprint summary:**\n- The challenge we addressed\n- What we tested\n- What we learned\n- Decisions made\n- Next steps\n\n**Keep the artifacts:**\n- Photos of walls\n- The prototype\n- User test videos (gold!)\n```\n\n---\n\n## Examples\n\n### Example 1: Planning a Sprint\n\n**Input:**\n> \"We're a B2B SaaS company considering a major redesign of our dashboard. Should we run a design sprint?\"\n\n**Output:**\n\n## Sprint Assessment: Dashboard Redesign\n\n### Is This Right for a Sprint?\n\n**Sprint works well when:**\n- ✓ High stakes (major investment if wrong)\n- ✓ Uncertainty (don't know if design will work)\n- ✓ Can prototype (digital product, easy to fake)\n- ✓ Users available (can recruit B2B users)\n\n**Sprint less ideal when:**\n- Solution is obvious (just build it)\n- Can't prototype (deep technical problem)\n- No user access (government contracts, etc.)\n\n**Verdict:** Good sprint candidate.\n\n### Sprint Setup\n\n**Challenge:**\n\"Design a dashboard that helps users accomplish [key job] in half the time.\"\n\n**Long-term goal:**\n\"Users choose us over competitors because our dashboard makes them more effective.\"\n\n**Sprint questions:**\n- Will users understand the new layout?\n- Can users find the data they need quickly?\n- Will the new design scale to power users?\n- Does this work on smaller screens?\n\n### Team Composition\n\n| Role | Person | Why |\n|------|--------|-----|\n| Decider | Head of Product | Authority to commit |\n| Facilitator | External\u002FDesign lead | Runs the process |\n| Designer | UI Designer | Creates prototype |\n| Engineer | Senior Dev | Feasibility gut-check |\n| Customer Success | CS Lead | User knowledge |\n| Sales | AE | Prospect objections |\n| Data | Analyst | Usage patterns |\n\n### Recruiting Users\n\n**Target:** 5 current users who use dashboard daily\n\n**Criteria:**\n- Mix of power users and regular users\n- Different company sizes\n- Active in last 30 days\n\n**Incentive:** $100 gift card for 1-hour session\n\n**Schedule:** Friday 9am, 10:30am, 12pm, 2pm, 3:30pm\n\n### Materials Prep\n\n**Before Monday:**\n- [ ] Room booked for full week\n- [ ] Whiteboard or wall space (lots)\n- [ ] Post-its (4 colors), markers, dots\n- [ ] Snacks and lunch plan\n- [ ] Prototype tool ready (Figma account)\n- [ ] User interviews confirmed\n- [ ] Current analytics pulled\n- [ ] Competitor dashboards screenshotted\n\n---\n\n### Example 2: Running Wednesday Decide\n\n**Input:**\n> \"We're on Wednesday of our sprint. We have 6 solution sketches. Walk me through making a decision.\"\n\n**Output:**\n\n## Wednesday Decide: Step-by-Step\n\n### Morning Setup\n\n**Materials ready:**\n- All 6 sketches posted on wall (face out)\n- Timer\n- Dot stickers (regular + 3 special for Decider)\n- Whiteboard for notes\n\n### 10:00 - Art Museum (20 min)\n\n**Instructions to team:**\n\"We're going to look at all solutions silently. No talking, no explaining.\nWalk around. Look at each sketch. Take notes on what catches your eye.\nThe sketches should speak for themselves.\"\n\n**Timer:** 20 minutes\n\n**If someone talks:** Gently remind: \"Save it for the critique.\"\n\n### 10:30 - Heat Map (15 min)\n\n**Instructions:**\n\"Now we'll vote on interesting parts. Not whole solutions—specific elements.\nEach person gets lots of dots. Put dots on anything you like.\nOne dot per interesting thing. Still no talking.\"\n\n**What happens:**\nClusters form. Some areas have lots of dots. Some have none.\nThis shows where the energy is without anyone pitching.\n\n### 11:00 - Speed Critique (3 min per sketch)\n\n**Process for each sketch:**\n\n**1. Facilitator narrates (1 min):**\n\"Okay, looking at this solution. I see the user arrives at [X],\nthen clicks [Y], and gets to [Z]. The key idea seems to be [A].\"\n\n**2. Call out concerns (1 min):**\n\"Any concerns or questions the team sees? Not debates—just note them.\"\nWrite concerns on post-its near the sketch.\n\n**3. Creator reveals (30 sec):**\n\"Whose sketch is this? Anything we missed?\"\nCreator can correct misunderstandings. No selling.\n\n**4. Capture big ideas (30 sec):**\n\"Any big ideas to capture from this one?\"\nWrite on \"Big Ideas\" whiteboard.\n\n**Move through all 6 sketches.** Keep it tight.\n\n### 11:45 - Straw Poll (5 min)\n\n**Instructions:**\n\"Now you each vote for ONE solution—the one you think we should prototype.\nThis isn't binding. It shows me where the team's thinking is.\nWrite your vote on a sticky note. I'll collect them.\"\n\n**Reveal the votes:**\n\"We have 3 votes for Sketch B, 2 for Sketch D, 1 for Sketch A.\"\n\n### 12:00 - Supervote (10 min)\n\n**Instructions to Decider:**\n\"[Decider name], you now have 3 special votes. These are the deciding votes.\nYou can put all 3 on one sketch, or spread them.\nWhere your votes go, we prototype.\"\n\n**Decider votes.** Team watches.\n\n**Announce:**\n\"We're prototyping Sketch B. This is our direction.\"\n\n### 12:15 - Rumble Check\n\n**If votes split:** Consider testing two approaches.\n**If aligned:** Go all-in on winner.\n\n**Decision:** \"We're doing an all-in-one on Sketch B, incorporating\nthe navigation idea from Sketch D.\"\n\n### 1:30 - Storyboard\n\n**Setup:** Large paper or whiteboard. 15-20 empty frames.\n\n**Question 1:** \"What's the opening scene? Where does the user start?\"\n\nDraw Frame 1 together. Facilitator draws, team directs.\n\n**Question 2:** \"What happens next? What do they do?\"\n\nContinue frame by frame. Include:\n- Every screen\n- Every click\u002Ftap\n- Key copy (headlines, buttons)\n- Error states if needed\n\n**Tip:** \"Is there anything between Frame 4 and Frame 5? Any step we're missing?\"\n\n### End of Wednesday\n\n**Output:**\n- Winner chosen\n- Storyboard complete\n- Team aligned\n- Ready to build tomorrow\n\n---\n\n### Example 3: Remote\u002FCompressed Sprint\n\n**Input:**\n> \"We need to run a sprint but team is remote and we only have 3 days. How do we adapt?\"\n\n**Output:**\n\n## Compressed Remote Sprint (3 Days)\n\n### Adaptation Principles\n\n**Remote changes:**\n- Video calls instead of in-person\n- Digital whiteboard (Miro, Figma, Mural)\n- Async pre-work to save synchronous time\n- More breaks (video fatigue)\n\n**Compressed changes:**\n- Combine Monday AM + PM\n- Combine sketching with deciding\n- Prototype faster (Goldilocks, not gold)\n- May test with 3 users instead of 5\n\n### Pre-Sprint Async Work (Day 0)\n\n**Before the sprint starts:**\n\n1. **Expert interviews:** Record async Loom videos\n2. **Lightning demos:** Team submits inspiration in shared doc\n3. **HMW notes:** Start collecting in Miro board\n4. **User recruiting:** Confirm Day 3 testers\n\n**Time saved:** ~3 hours of Day 1\n\n### Day 1: Map + Sketch (Full Day)\n\n**9:00-9:30 - Sprint setup**\n- Video call, cameras on\n- Intro, ground rules\n- Review pre-work\n\n**9:30-10:30 - Long-term goal + Sprint questions**\n- Miro board for collaborative editing\n- Decider confirms goal\n\n**10:30-11:30 - Build the map**\n- One person shares screen and draws\n- Team directs\n- Pick target\n\n**11:30-12:00 - Organize HMWs**\n- Digital dot voting in Miro\n- Affinity clustering\n\n**BREAK (1 hour)**\n\n**1:00-2:30 - Lightning demo review + Notes**\n- Review pre-submitted demos\n- Take individual notes (async)\n\n**2:30-3:00 - Crazy 8s**\n- Everyone works locally\n- Screenshot and upload to Miro\n\n**3:00-5:00 - Solution sketch**\n- Work individually\n- Upload final sketch to Miro by EOD\n\n### Day 2: Decide + Prototype (Full Day)\n\n**9:00-10:00 - Art museum + Heat map**\n- Async review of sketches in Miro (cameras off, 30 min)\n- Reconvene for dot voting\n\n**10:00-11:00 - Speed critique**\n- 5 min per sketch (compressed)\n- Facilitator shares screen, narrates\n\n**11:00-11:30 - Straw poll + Supervote**\n- Digital voting\n- Decider decides\n\n**11:30-12:00 - Storyboard start**\n- Collaborative in Miro\n- Sketch key frames\n\n**BREAK (1 hour)**\n\n**1:00-5:00 - Prototype build**\n- Team splits: Makers, Stitcher, Writer\n- Slack channel for coordination\n- Check-in at 3pm\n- Trial run at 4:30pm\n\n### Day 3: Test (Half Day)\n\n**9:00-12:00 - User tests**\n- 3 users (compressed from 5)\n- 45 min each\n- Video recorded\n- Team watches via Zoom\n\n**1:00-2:00 - Pattern review**\n- Debrief call\n- What worked? What didn't?\n- Decisions captured\n\n**2:00-3:00 - Next steps**\n- Document learnings\n- Plan post-sprint action\n\n### Remote Sprint Tips\n\n**Video fatigue:**\n- Cameras optional during solo work\n- 10-min breaks every 90 min\n- Lunch is a real break\n\n**Digital whiteboard:**\n- Assign one person to \"drive\" shared board\n- Use templates to save setup time\n- Practice tool before sprint\n\n**Time zones:**\n- Core hours when everyone overlaps\n- Async pre-work for offset zones\n\n**Prototype tools:**\n- Figma (collaborative)\n- Can share prototype link for testing\n\n---\n\n## Checklists & Templates\n\n### Sprint Prep Checklist\n\n```\n## 2 Weeks Before\n\n### People\n□ Decider confirmed and calendar blocked\n□ Sprint team identified (5-7 people)\n□ Facilitator assigned\n□ External experts identified for Monday\n\n### Logistics\n□ Room booked (or video call setup)\n□ User recruitment started\n\n### Challenge\n□ Sprint challenge drafted\n□ Long-term goal discussed with Decider\n\n## 1 Week Before\n\n### Users\n□ 5 users confirmed for Friday\n□ Screener criteria applied\n□ Calendar invites sent\n□ Incentives arranged\n\n### Materials\n□ Whiteboards\u002Fwall space ready\n□ Post-its, markers, dots ordered\n□ Prototype tool tested\n□ Recording setup for Friday\n\n### Content\n□ Lightning demo examples collected\n□ Current data\u002Fanalytics pulled\n□ Competitor research gathered\n\n## Day Before\n\n□ Room setup complete\n□ Agenda posted\n□ Materials laid out\n□ Friday interview schedule confirmed\n□ Trial run of video\u002Frecording\n```\n\n---\n\n### Interview Script Template\n\n```\n## Friday User Test Script\n\n### Welcome (5 min)\n\"Thanks for coming in! I'm [name], and I'll be walking you\nthrough some ideas we're exploring. This is NOT a test of you—\nwe're testing our ideas.\n\nPlease think out loud. Tell me what you're seeing, what you're\nthinking, even if it's 'this is confusing.'\n\nYour honest feedback helps us make this better.\nThere are no wrong answers. Ready?\"\n\n### Context Questions (10 min)\n\"Before I show you anything...\"\n\n- \"Tell me about your role. What do you do day to day?\"\n- \"How do you currently handle [problem area]?\"\n- \"What's most challenging about that?\"\n- \"What tools do you use?\"\n\n### Prototype Walkthrough (40 min)\n\"I'm going to show you something we're working on.\nIt's just a prototype—not everything works.\nTalk me through what you see and what you'd do.\"\n\n[Show prototype]\n\n**As they explore:**\n- \"What are you thinking?\"\n- \"What would you do next?\"\n- \"What did you expect to happen?\"\n- \"Is this what you expected to see?\"\n\n**When they struggle:**\n- \"What's confusing?\"\n- \"What would make this clearer?\"\n- Don't rescue them. Let them figure it out.\n\n### Debrief (5 min)\n\"Thanks for walking through that.\"\n\n- \"If you could change one thing, what would it be?\"\n- \"How does this compare to how you do things today?\"\n- \"Anything else I should know?\"\n\n### Close\n\"Thank you so much! Your feedback is incredibly valuable.\"\n```\n\n---\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Structuring video production workflows\n- Creating storyboard frameworks\n- Suggesting technical approaches\n- Providing creative direction templates\n\n### What This Skill Cannot Do\n- Replace professional videography\n- Edit video files directly\n- Make final creative judgments\n- Guarantee audience engagement\n\n## References\n\n- Knapp, Jake. \"Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days\" (2016)\n- Google Ventures Sprint methodology\n- AJ&Smart sprint facilitation resources\n- IDEO design thinking background\n\n## Related Skills\n\n- [product-discovery](..\u002Fproduct-discovery\u002F) - Ongoing discovery\n- [shape-up](..\u002Fshape-up\u002F) - Building methodology\n- [lean-canvas](..\u002F..\u002Fvalidation\u002Flean-canvas\u002F) - Business model validation\n- [mom-test](..\u002F..\u002Fvalidation\u002Fmom-test\u002F) - Interview techniques\n\n---\n\n## Skill Metadata\n\n\n- **Mode**: cyborg\n```yaml\nname: design-sprint\ncategory: product\nsubcategory: methodology\nversion: 1.0\nauthor: MKTG Skills\nsource_expert: Jake Knapp\nsource_work: Sprint\ndifficulty: intermediate\nestimated_value: $20,000+ facilitation engagement\ntags: [design sprint, GV, Google Ventures, prototyping, validation, 5 days, innovation]\ncreated: 2026-01-25\nupdated: 2026-01-25\n```\n","# Design Sprint\n\n> Test big ideas in just 5 days. Apply Google Ventures' proven methodology to go from problem to validated prototype without months of development.\n\n## When to Use This Skill\n\n- **New product concepts** that need validation before building\n- **Big feature decisions** with significant investment required\n- **Stuck teams** needing to break through analysis paralysis\n- **Startup pivots** when direction is uncertain\n- **High-risk bets** where failure is expensive\n- **Cross-functional alignment** when teams disagree on direction\n\n## Methodology Foundation\n\n| Aspect | Details |\n|--------|---------|\n| **Source** | Jake Knapp - Sprint (2016), developed at Google Ventures |\n| **Core Principle** | \"5 days to go from problem to tested solution. Prototype and test with real users instead of debating and building.\" |\n| **Validation** | Used in 150+ startups by GV, adopted by teams at Google, Slack, Uber, IDEO |\n| **Why This Matters** | Months of work compressed into a week. Learn in 5 days what would take months to discover after launch. |\n\n\n## What Claude Does vs What You Decide\n\n| Claude Does | You Decide |\n|-------------|------------|\n| Structures video workflow | Final creative vision |\n| Suggests shot compositions | Equipment selection |\n| Creates storyboard templates | Brand aesthetics |\n| Generates script frameworks | Final approval |\n| Identifies technical requirements | Budget allocation |\n\n## What This Skill Does\n\n1. **Structures a 5-day process** - Monday to Friday, full schedule\n2. **Facilitates divergent thinking** - Generate many ideas\n3. **Enables rapid prototyping** - Realistic but fake\n4. **Validates with real users** - Test on Friday\n5. **Aligns teams quickly** - Shared understanding and decision\n6. **Reduces risk** - Learn before you build\n\n## How to Use\n\n### Plan a Design Sprint\n```\nI want to run a design sprint to solve [challenge].\nHelp me plan the 5-day schedule and prepare materials.\nTeam: [who's involved]\n```\n\n### Run a Specific Sprint Day\n```\nWe're on [Day] of our design sprint.\nGuide me through today's activities for [challenge].\n```\n\n### Adapt for Remote\u002FCompressed Sprint\n```\nI need to run a design sprint remotely [or: in 3 days instead of 5].\nHelp me adapt the methodology.\n```\n\n## Instructions\n\n### Step 1: Understand the Sprint Overview\n\n```\n## The 5-Day Sprint\n\n### Why 5 Days?\n\n**Day 1 (Monday): Map**\nUnderstand the problem and pick a target\n\n**Day 2 (Tuesday): Sketch**\nGenerate solutions individually\n\n**Day 3 (Wednesday): Decide**\nChoose the best solution\n\n**Day 4 (Thursday): Prototype**\nBuild a realistic facade\n\n**Day 5 (Friday): Test**\nGet real user feedback\n\n### The Philosophy\n\n**Before sprints:**\n- Debate ideas for weeks\n- Build something over months\n- Launch and hope\n- Discover problems late\n\n**With sprints:**\n- 1 day to understand\n- 2 days to generate and decide\n- 1 day to prototype\n- 1 day to validate\n- Learn before building\n\n### What You Need\n\n**Team (7 or fewer):**\n- Decider (authority to make calls)\n- Facilitator (runs the sprint)\n- Product person\n- Designer\n- Engineer\n- Domain expert\n- Customer-facing person\n\n**Space:**\n- Dedicated room for 5 days\n- Whiteboards or wall space\n- Post-its, markers, dot stickers\n\n**Prep:**\n- 5 user interviews scheduled for Friday\n- Sprint challenge defined\n- Long-term goal agreed\n```\n\n---\n\n### Step 2: Day-by-Day Activities\n\n```\n## Monday: Map\n\n### Goal\nUnderstand the problem. Pick where to focus.\n\n### Schedule\n\n**10:00 - Long-term goal**\n\"Where do we want to be in 6 months \u002F 2 years?\"\nWrite on whiteboard. Get Decider agreement.\n\n**10:30 - Sprint questions**\n\"What could go wrong? What do we need to learn?\"\nTurn fears into questions.\n\"Will users understand our value prop?\"\n\"Can we convert free users to paid?\"\n\n**11:00 - Make a map**\nCustomer journey map:\n```\n[Actor] → [Action 1] → [Action 2] → [Goal]\n               ↓            ↓\n         [Touchpoint]  [Touchpoint]\n```\n\nSimple is better. Show how customers interact.\n\n**1:00 - Ask the experts**\nInterview team members and stakeholders.\n20 minutes each. \"How Might We\" notes.\n\n**How Might We (HMW):**\nTurn problems into opportunities.\nProblem: \"Users don't understand pricing\"\nHMW: \"How might we make pricing instantly clear?\"\n\n**3:30 - Organize HMWs**\nAffinity map the HMW notes.\nDot vote on most important.\n\n**4:30 - Pick a target**\nChoose ONE part of the map to focus on.\nDecider makes the call.\n\n### Monday Output\n- Long-term goal on wall\n- Sprint questions on wall\n- Map on wall\n- Target circled on map\n```\n\n---\n\n```\n## Tuesday: Sketch\n\n### Goal\nGenerate solutions. Everyone contributes.\n\n### Schedule\n\n**10:00 - Lightning demos**\nShow inspiring solutions from other products\u002Findustries.\n3 minutes each. Capture \"Big Ideas\" on post-its.\n\n**11:30 - Divide or swarm**\nIf multiple targets, assign team members to each.\nIf one target, everyone tackles it.\n\n**1:00 - Four-step sketch (individual work)**\n\n**Step 1: Notes (20 min)**\nWalk around room. Take notes on what's there.\nReview goals, map, HMWs, demos.\n\n**Step 2: Ideas (20 min)**\nWrite rough ideas. No polish.\nQuantity over quality.\n\n**Step 3: Crazy 8s (8 min)**\nFold paper into 8 sections.\n1 minute per section: sketch a variation.\nForces rapid iteration.\n\n**Step 4: Solution sketch (30-90 min)**\nCreate a 3-panel storyboard.\nSelf-explanatory (words + pictures).\nAnonymous (no names).\n\n**Key rules:**\n- Work alone (no groupthink)\n- No collaboration yet\n- Keep sketches anonymous\n- Must be self-explanatory\n\n### Tuesday Output\n- Solution sketches from each person\n- Posted on wall, face out\n```\n\n---\n\n```\n## Wednesday: Decide\n\n### Goal\nChoose one solution to prototype.\n\n### Schedule\n\n**10:00 - Art museum**\nPost all sketches on wall.\nTeam walks around in silence (no pitching).\n\n**10:30 - Heat map**\nDot vote silently on interesting parts.\nNo discussion. Cluster votes reveal consensus.\n\n**11:00 - Speed critique**\n3 minutes per sketch.\nFacilitator narrates. Team discusses.\nCapture standout ideas.\n\n**11:45 - Straw poll**\nEach person votes for ONE solution.\n(Not binding, just gauging sentiment)\n\n**12:00 - Supervote**\nDecider gets 3 special votes.\nDecider's votes decide what gets prototyped.\n\n**Why Decider decides:**\n- Faster than consensus\n- One person is accountable\n- Avoids design-by-committee\n\n**1:30 - Rumble or All-in-one?**\nIf votes cluster on one idea: All-in-one prototype\nIf votes split: Can we combine? Or do we rumble (test both)?\n\n**2:00 - Storyboard**\nDraw the prototype frame-by-frame.\nWhat does the user see at each step?\n\n```\n[Frame 1]    [Frame 2]    [Frame 3]    [Frame 4]\nOpening      Key action   Result       End state\nscene\n```\n\n15-20 frames typical. Detail matters.\n\n### Wednesday Output\n- Winner(s) chosen\n- Detailed storyboard ready for prototype\n```\n\n---\n\n```\n## Thursday: Prototype\n\n### Goal\nBuild something real enough to test.\n\n### Schedule\n\n**Full day: Build the prototype**\n\n### The Prototype Mindset\n\n**Not building:**\n- A real product\n- Code\n- Anything that works\n\n**Building:**\n- A facade\n- Realistic enough to get real reactions\n- Goldilocks quality (just right)\n\n### Goldilocks Quality\n\n**Too low:** User can't engage, doesn't feel real\n**Too high:** Takes too long, you get attached\n**Just right:** Real enough to react to, fake enough to be fast\n\n### Division of Labor\n\n**Makers (2+):**\nBuild the screens\u002Fassets\n\n**Stitcher (1):**\nAssemble into clickable flow\n\n**Writer (1):**\nAll the copy and content\n\n**Asset collector (1):**\nStock photos, logos, icons\n\n**Interviewer (1):**\nPrep Friday's interview script\n\n### Tools\n\n| Prototype Type | Tools |\n|----------------|-------|\n| Digital product | Figma, Keynote, InVision |\n| Physical product | 3D print, foam, paper |\n| Service | Role-play script, fake storefront |\n| Marketing | Landing page, fake ads |\n\n### Thursday Tips\n\n- Start with hardest screens first\n- Writer writes real copy (not Lorem Ipsum)\n- Error states matter\n- Have something testable by 3pm\n- Do a trial run at 4pm\n- Fix issues before Friday\n\n### Thursday Output\n- Clickable\u002Fusable prototype\n- Interview script ready\n- 5 users confirmed for Friday\n```\n\n---\n\n```\n## Friday: Test\n\n### Goal\nLearn from real users.\n\n### Schedule\n\n**9:00 - Prep**\n- Prototype working\n- Interview room ready\n- Observation room set up (team watches)\n\n**10:00-3:00 - Five user interviews**\n1 hour each. 30 minutes between.\n\n**Interview structure:**\n1. Friendly welcome (5 min)\n2. Context questions (10 min)\n3. Prototype walkthrough (40 min)\n4. Debrief (5 min)\n\n**3:30-5:00 - Review and learn**\n- Look for patterns\n- What worked?\n- What didn't?\n- What surprised us?\n\n### Watching the Interviews\n\n**Team watches from another room**\n- Video feed or live stream\n- No interrupting\n\n**Note-taking:**\nEach watcher takes notes on:\n- Positive reactions (+)\n- Negative reactions (-)\n- Quotes\n- Questions\n\n**Use a grid:**\n```\n           | User 1 | User 2 | User 3 | User 4 | User 5\n-----------|--------|--------|--------|--------|--------\nFeature A  | + Easy | + Easy | - Conf | + Easy | + Easy\nFeature B  | - Lost | - Lost | - Lost | + OK   | - Lost\n```\n\nPatterns become obvious.\n\n### 5 Is Enough\n\nWhy 5 users?\n- 85% of issues found with 5 users\n- Diminishing returns after 5\n- Can recruit in a week\n- One day of testing\n\n### Friday Output\n- Patterns documented\n- Decisions on what to build\n- Next steps clear\n```\n\n---\n\n### Step 3: After the Sprint\n\n```\n## What Happens Next\n\n### Possible Outcomes\n\n**1. Big hit (everything worked)**\n- Move to build with confidence\n- Scope based on prototype\n- High conviction, low risk\n\n**2. Flawed but promising**\n- Know what to fix\n- Might need mini-sprint on problem area\n- Build core, iterate on issues\n\n**3. Mixed results**\n- Some things worked, some didn't\n- Consider pivot or scope reduction\n- Another sprint on specific problem?\n\n**4. Complete miss**\n- Wrong problem or wrong solution\n- Better to know now than after building\n- Reframe and try again\n\n### Turn Learning into Action\n\n**If building:**\n1. Turn storyboard into spec\n2. Engineers can start from prototype\n3. Validated design reduces back-and-forth\n\n**If pivoting:**\n1. What did we learn?\n2. What's the new hypothesis?\n3. Next sprint or different approach?\n\n### Document the Sprint\n\n**Sprint summary:**\n- The challenge we addressed\n- What we tested\n- What we learned\n- Decisions made\n- Next steps\n\n**Keep the artifacts:**\n- Photos of walls\n- The prototype\n- User test videos (gold!)\n```\n\n---\n\n## Examples\n\n### Example 1: Planning a Sprint\n\n**Input:**\n> \"We're a B2B SaaS company considering a major redesign of our dashboard. Should we run a design sprint?\"\n\n**Output:**\n\n## Sprint Assessment: Dashboard Redesign\n\n### Is This Right for a Sprint?\n\n**Sprint works well when:**\n- ✓ High stakes (major investment if wrong)\n- ✓ Uncertainty (don't know if design will work)\n- ✓ Can prototype (digital product, easy to fake)\n- ✓ Users available (can recruit B2B users)\n\n**Sprint less ideal when:**\n- Solution is obvious (just build it)\n- Can't prototype (deep technical problem)\n- No user access (government contracts, etc.)\n\n**Verdict:** Good sprint candidate.\n\n### Sprint Setup\n\n**Challenge:**\n\"Design a dashboard that helps users accomplish [key job] in half the time.\"\n\n**Long-term goal:**\n\"Users choose us over competitors because our dashboard makes them more effective.\"\n\n**Sprint questions:**\n- Will users understand the new layout?\n- Can users find the data they need quickly?\n- Will the new design scale to power users?\n- Does this work on smaller screens?\n\n### Team Composition\n\n| Role | Person | Why |\n|------|--------|-----|\n| Decider | Head of Product | Authority to commit |\n| Facilitator | External\u002FDesign lead | Runs the process |\n| Designer | UI Designer | Creates prototype |\n| Engineer | Senior Dev | Feasibility gut-check |\n| Customer Success | CS Lead | User knowledge |\n| Sales | AE | Prospect objections |\n| Data | Analyst | Usage patterns |\n\n### Recruiting Users\n\n**Target:** 5 current users who use dashboard daily\n\n**Criteria:**\n- Mix of power users and regular users\n- Different company sizes\n- Active in last 30 days\n\n**Incentive:** $100 gift card for 1-hour session\n\n**Schedule:** Friday 9am, 10:30am, 12pm, 2pm, 3:30pm\n\n### Materials Prep\n\n**Before Monday:**\n- [ ] Room booked for full week\n- [ ] Whiteboard or wall space (lots)\n- [ ] Post-its (4 colors), markers, dots\n- [ ] Snacks and lunch plan\n- [ ] Prototype tool ready (Figma account)\n- [ ] User interviews confirmed\n- [ ] Current analytics pulled\n- [ ] Competitor dashboards screenshotted\n\n---\n\n### Example 2: Running Wednesday Decide\n\n**Input:**\n> \"We're on Wednesday of our sprint. We have 6 solution sketches. Walk me through making a decision.\"\n\n**Output:**\n\n## Wednesday Decide: Step-by-Step\n\n### Morning Setup\n\n**Materials ready:**\n- All 6 sketches posted on wall (face out)\n- Timer\n- Dot stickers (regular + 3 special for Decider)\n- Whiteboard for notes\n\n### 10:00 - Art Museum (20 min)\n\n**Instructions to team:**\n\"We're going to look at all solutions silently. No talking, no explaining.\nWalk around. Look at each sketch. Take notes on what catches your eye.\nThe sketches should speak for themselves.\"\n\n**Timer:** 20 minutes\n\n**If someone talks:** Gently remind: \"Save it for the critique.\"\n\n### 10:30 - Heat Map (15 min)\n\n**Instructions:**\n\"Now we'll vote on interesting parts. Not whole solutions—specific elements.\nEach person gets lots of dots. Put dots on anything you like.\nOne dot per interesting thing. Still no talking.\"\n\n**What happens:**\nClusters form. Some areas have lots of dots. Some have none.\nThis shows where the energy is without anyone pitching.\n\n### 11:00 - Speed Critique (3 min per sketch)\n\n**Process for each sketch:**\n\n**1. Facilitator narrates (1 min):**\n\"Okay, looking at this solution. I see the user arrives at [X],\nthen clicks [Y], and gets to [Z]. The key idea seems to be [A].\"\n\n**2. Call out concerns (1 min):**\n\"Any concerns or questions the team sees? Not debates—just note them.\"\nWrite concerns on post-its near the sketch.\n\n**3. Creator reveals (30 sec):**\n\"Whose sketch is this? Anything we missed?\"\nCreator can correct misunderstandings. No selling.\n\n**4. Capture big ideas (30 sec):**\n\"Any big ideas to capture from this one?\"\nWrite on \"Big Ideas\" whiteboard.\n\n**Move through all 6 sketches.** Keep it tight.\n\n### 11:45 - Straw Poll (5 min)\n\n**Instructions:**\n\"Now you each vote for ONE solution—the one you think we should prototype.\nThis isn't binding. It shows me where the team's thinking is.\nWrite your vote on a sticky note. I'll collect them.\"\n\n**Reveal the votes:**\n\"We have 3 votes for Sketch B, 2 for Sketch D, 1 for Sketch A.\"\n\n### 12:00 - Supervote (10 min)\n\n**Instructions to Decider:**\n\"[Decider name], you now have 3 special votes. These are the deciding votes.\nYou can put all 3 on one sketch, or spread them.\nWhere your votes go, we prototype.\"\n\n**Decider votes.** Team watches.\n\n**Announce:**\n\"We're prototyping Sketch B. This is our direction.\"\n\n### 12:15 - Rumble Check\n\n**If votes split:** Consider testing two approaches.\n**If aligned:** Go all-in on winner.\n\n**Decision:** \"We're doing an all-in-one on Sketch B, incorporating\nthe navigation idea from Sketch D.\"\n\n### 1:30 - Storyboard\n\n**Setup:** Large paper or whiteboard. 15-20 empty frames.\n\n**Question 1:** \"What's the opening scene? Where does the user start?\"\n\nDraw Frame 1 together. Facilitator draws, team directs.\n\n**Question 2:** \"What happens next? What do they do?\"\n\nContinue frame by frame. Include:\n- Every screen\n- Every click\u002Ftap\n- Key copy (headlines, buttons)\n- Error states if needed\n\n**Tip:** \"Is there anything between Frame 4 and Frame 5? Any step we're missing?\"\n\n### End of Wednesday\n\n**Output:**\n- Winner chosen\n- Storyboard complete\n- Team aligned\n- Ready to build tomorrow\n\n---\n\n### Example 3: Remote\u002FCompressed Sprint\n\n**Input:**\n> \"We need to run a sprint but team is remote and we only have 3 days. How do we adapt?\"\n\n**Output:**\n\n## Compressed Remote Sprint (3 Days)\n\n### Adaptation Principles\n\n**Remote changes:**\n- Video calls instead of in-person\n- Digital whiteboard (Miro, Figma, Mural)\n- Async pre-work to save synchronous time\n- More breaks (video fatigue)\n\n**Compressed changes:**\n- Combine Monday AM + PM\n- Combine sketching with deciding\n- Prototype faster (Goldilocks, not gold)\n- May test with 3 users instead of 5\n\n### Pre-Sprint Async Work (Day 0)\n\n**Before the sprint starts:**\n\n1. **Expert interviews:** Record async Loom videos\n2. **Lightning demos:** Team submits inspiration in shared doc\n3. **HMW notes:** Start collecting in Miro board\n4. **User recruiting:** Confirm Day 3 testers\n\n**Time saved:** ~3 hours of Day 1\n\n### Day 1: Map + Sketch (Full Day)\n\n**9:00-9:30 - Sprint setup**\n- Video call, cameras on\n- Intro, ground rules\n- Review pre-work\n\n**9:30-10:30 - Long-term goal + Sprint questions**\n- Miro board for collaborative editing\n- Decider confirms goal\n\n**10:30-11:30 - Build the map**\n- One person shares screen and draws\n- Team directs\n- Pick target\n\n**11:30-12:00 - Organize HMWs**\n- Digital dot voting in Miro\n- Affinity clustering\n\n**BREAK (1 hour)**\n\n**1:00-2:30 - Lightning demo review + Notes**\n- Review pre-submitted demos\n- Take individual notes (async)\n\n**2:30-3:00 - Crazy 8s**\n- Everyone works locally\n- Screenshot and upload to Miro\n\n**3:00-5:00 - Solution sketch**\n- Work individually\n- Upload final sketch to Miro by EOD\n\n### Day 2: Decide + Prototype (Full Day)\n\n**9:00-10:00 - Art museum + Heat map**\n- Async review of sketches in Miro (cameras off, 30 min)\n- Reconvene for dot voting\n\n**10:00-11:00 - Speed critique**\n- 5 min per sketch (compressed)\n- Facilitator shares screen, narrates\n\n**11:00-11:30 - Straw poll + Supervote**\n- Digital voting\n- Decider decides\n\n**11:30-12:00 - Storyboard start**\n- Collaborative in Miro\n- Sketch key frames\n\n**BREAK (1 hour)**\n\n**1:00-5:00 - Prototype build**\n- Team splits: Makers, Stitcher, Writer\n- Slack channel for coordination\n- Check-in at 3pm\n- Trial run at 4:30pm\n\n### Day 3: Test (Half Day)\n\n**9:00-12:00 - User tests**\n- 3 users (compressed from 5)\n- 45 min each\n- Video recorded\n- Team watches via Zoom\n\n**1:00-2:00 - Pattern review**\n- Debrief call\n- What worked? What didn't?\n- Decisions captured\n\n**2:00-3:00 - Next steps**\n- Document learnings\n- Plan post-sprint action\n\n### Remote Sprint Tips\n\n**Video fatigue:**\n- Cameras optional during solo work\n- 10-min breaks every 90 min\n- Lunch is a real break\n\n**Digital whiteboard:**\n- Assign one person to \"drive\" shared board\n- Use templates to save setup time\n- Practice tool before sprint\n\n**Time zones:**\n- Core hours when everyone overlaps\n- Async pre-work for offset zones\n\n**Prototype tools:**\n- Figma (collaborative)\n- Can share prototype link for testing\n\n---\n\n## Checklists & Templates\n\n### Sprint Prep Checklist\n\n```\n## 2 Weeks Before\n\n### People\n□ Decider confirmed and calendar blocked\n□ Sprint team identified (5-7 people)\n□ Facilitator assigned\n□ External experts identified for Monday\n\n### Logistics\n□ Room booked (or video call setup)\n□ User recruitment started\n\n### Challenge\n□ Sprint challenge drafted\n□ Long-term goal discussed with Decider\n\n## 1 Week Before\n\n### Users\n□ 5 users confirmed for Friday\n□ Screener criteria applied\n□ Calendar invites sent\n□ Incentives arranged\n\n### Materials\n□ Whiteboards\u002Fwall space ready\n□ Post-its, markers, dots ordered\n□ Prototype tool tested\n□ Recording setup for Friday\n\n### Content\n□ Lightning demo examples collected\n□ Current data\u002Fanalytics pulled\n□ Competitor research gathered\n\n## Day Before\n\n□ Room setup complete\n□ Agenda posted\n□ Materials laid out\n□ Friday interview schedule confirmed\n□ Trial run of video\u002Frecording\n```\n\n---\n\n### Interview Script Template\n\n```\n## Friday User Test Script\n\n### Welcome (5 min)\n\"Thanks for coming in! I'm [name], and I'll be walking you\nthrough some ideas we're exploring. This is NOT a test of you—\nwe're testing our ideas.\n\nPlease think out loud. Tell me what you're seeing, what you're\nthinking, even if it's 'this is confusing.'\n\nYour honest feedback helps us make this better.\nThere are no wrong answers. Ready?\"\n\n### Context Questions (10 min)\n\"Before I show you anything...\"\n\n- \"Tell me about your role. What do you do day to day?\"\n- \"How do you currently handle [problem area]?\"\n- \"What's most challenging about that?\"\n- \"What tools do you use?\"\n\n### Prototype Walkthrough (40 min)\n\"I'm going to show you something we're working on.\nIt's just a prototype—not everything works.\nTalk me through what you see and what you'd do.\"\n\n[Show prototype]\n\n**As they explore:**\n- \"What are you thinking?\"\n- \"What would you do next?\"\n- \"What did you expect to happen?\"\n- \"Is this what you expected to see?\"\n\n**When they struggle:**\n- \"What's confusing?\"\n- \"What would make this clearer?\"\n- Don't rescue them. Let them figure it out.\n\n### Debrief (5 min)\n\"Thanks for walking through that.\"\n\n- \"If you could change one thing, what would it be?\"\n- \"How does this compare to how you do things today?\"\n- \"Anything else I should know?\"\n\n### Close\n\"Thank you so much! Your feedback is incredibly valuable.\"\n```\n\n---\n\n## Skill Boundaries\n\n### What This Skill Does Well\n- Structuring video production workflows\n- Creating storyboard frameworks\n- Suggesting technical approaches\n- Providing creative direction templates\n\n### What This Skill Cannot Do\n- Replace professional videography\n- Edit video files directly\n- Make final creative judgments\n- Guarantee audience engagement\n\n## References\n\n- Knapp, Jake. \"Sprint: How to Solve Big Problems and Test New Ideas in Just Five Days\" (2016)\n- Google Ventures Sprint methodology\n- AJ&Smart sprint facilitation resources\n- IDEO design thinking background\n\n## Related Skills\n\n- [product-discovery](..\u002Fproduct-discovery\u002F) - Ongoing discovery\n- [shape-up](..\u002Fshape-up\u002F) - Building methodology\n- [lean-canvas](..\u002F..\u002Fvalidation\u002Flean-canvas\u002F) - Business model validation\n- [mom-test](..\u002F..\u002Fvalidation\u002Fmom-test\u002F) - Interview techniques\n\n---\n\n## Skill Metadata\n\n\n- **Mode**: cyborg\n```yaml\nname: design-sprint\ncategory: product\nsubcategory: methodology\nversion: 1.0\nauthor: MKTG Skills\nsource_expert: Jake Knapp\nsource_work: Sprint\ndifficulty: intermediate\nestimated_value: $20,000+ facilitation engagement\ntags: [design sprint, GV, Google Ventures, prototyping, validation, 5 days, innovation]\ncreated: 2026-01-25\nupdated: 2026-01-25\n```\n",{"name":5,"license":14,"metadata":23,"description":7},{"author":24,"version":25,"mcp-server":26},"ClawFu","1.0.0","@clawfu\u002Fmcp-skills","master","f483e54f3ad5f202a77d45f2e57f8d970b71195f","skills_library\u002Fdesign-sprint",2,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills","https:\u002F\u002Fgithub.com\u002Froohe","yoou.link","2026-05-19 15:56:07",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add roohe\u002Fagentic-super-skills --skill design-sprint",{"tool":41,"command":42},"bunx","bunx skills add roohe\u002Fagentic-super-skills --skill design-sprint",{"tool":44,"command":45},"pnpm","pnpm dlx skills add roohe\u002Fagentic-super-skills --skill design-sprint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002FSKILL.md",true,[49,55,59,63,67,71,75,79,83],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcase-studies.md","REFERENCE","参考文档",21682,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Fcase-studies.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Ffacilitation.md",13495,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Ffacilitation.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ffriday.md",13805,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Ffriday.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmonday.md",12074,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Fmonday.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Frecruiting.md",13059,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Frecruiting.md",{"path":72,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fremote-sprints.md",16477,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Fremote-sprints.md",{"path":76,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fthursday.md",12204,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Fthursday.md",{"path":80,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":81,"sourceHtmlUrl":82},"references\u002Ftuesday.md",11657,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Ftuesday.md",{"path":84,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002Fwednesday.md",11765,"https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fdesign-sprint\u002Freferences\u002Fwednesday.md",[88,95,102,109,116,123],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":18},"01M73D865CZME2FCMKA4PQM348","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":18},"01M73D7Z64J4ABWZJD7P44XBBF","youtube-downloader","Download and process YouTube content for research. Use when: downloading competitor videos for analysis; extracting audio for podcasts; getting transcripts for content repurposing; archiving webinars; research content curation","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyoutube-downloader\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":18},"01M73D7K8778TGZV3GJFR3703D","yc-pitch-deck","Create a compelling startup pitch deck that follows the structure proven to raise billions from top investors. Master the YC and Sequoia formats that get founders funded. Use when: **Fundraising** to create investor pitch decks; **YC application** to structure your narrative; **Demo Day prep** to craft your 2-minute pitch; **Angel investors** to communicate your opportunity; **Partnership pitches** to structure compelling asks","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fyc-pitch-deck\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":18},"01M73D70KJSE0E8Z28YMNNRT04","x-twitter-scraper","Use when the user needs X (Twitter) data or confirmation-gated X actions through Xquik: tweet search, user lookup, follower extraction, media download, monitoring, webhooks, MCP, SDKs, posting, likes, DMs, and profile updates. Requires a Xquik API key. Never ask for X login material.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fx-twitter-scraper\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":18},"01M73D6ED01GV077R7K4NZNFZJ","write-vignette","Create R package vignettes using R Markdown or Quarto. Covers vignette setup, YAML configuration, code chunk options, building and testing, and CRAN requirements for vignettes. Use when adding a Getting Started tutorial, documenting complex workflows spanning multiple functions, creating domain-specific guides, or when CRAN submission requires user-facing documentation beyond function help pages.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-vignette\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":18},"01M73D69YJR0BK3NFHE0CYG3EF","write-validation-documentation","Write IQ\u002FOQ\u002FPQ validation documentation for computerized systems in regulated environments. Covers protocols, reports, test scripts, deviation handling, and approval workflows. Use when validating R or other software for regulated use, preparing for a regulatory audit, documenting qualification of computing environments, or creating and updating validation protocols and reports for new or re-qualified systems.","https:\u002F\u002Fgithub.com\u002Froohe\u002Fagentic-super-skills\u002Fblob\u002Fmaster\u002Fskills_library\u002Fwrite-validation-documentation\u002FSKILL.md",[],[]]