design-sprint

Guides a five-day design sprint to prototype and test product ideas with users.

Updated Jun 27, 2026
One-click install
npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill design-sprint-rachmadideni
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: design-sprint
Source: https://github.com/rachmadideni/ai-staff-assistant/tree/main/.agents/skills/design-sprint
Command: npx skills add https://github.com/rachmadideni/ai-staff-assistant --skill design-sprint-rachmadideni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams facing high-stakes product decisions often get stuck in endless debate or invest months building features nobody wants. This Skill provides a structured five-day process to map the problem, sketch solutions, decide on a direction, build a realistic prototype, and test it with five real users before writing production code. ## Core Features & Use Cases - Day-by-Day Sprint Facilitation: Detailed schedules, exercises, and outputs for each sprint day (Map, Sketch, Decide, Prototype, Test), including time-boxing guidance and role assignments. - User Testing Framework: A five-act interview script, note-taking grid, and pattern-recognition method for extracting reliable signals from five customer interviews. - Supporting References: In-depth guides for facilitation, participant recruiting, remote sprint adaptation, and real case studies from Slack, Blue Bottle, Savioke, and others. - Use Case: A product team debating whether to build a new onboarding flow can run this sprint to prototype two competing approaches on Thursday and watch five target users react on Friday, ending the week with a validated decision instead of a month of meetings. ## Quick Start Ask the assistant to plan a design sprint for your product challenge, starting with Monday's long-term goal, sprint questions, and customer journey map.

Frequently Asked Questions about design-sprint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a design sprint for a product idea?â–¼

Follow the five-day structure: Monday map the problem and pick a target, Tuesday sketch solutions individually, Wednesday critique and storyboard the winner, Thursday build a realistic facade prototype, and Friday test with five target users. A Decider with authority must be present all week.

How many users should I test in a design sprint?â–¼

Test with five users on Friday. Patterns emerge after three to five interviews and returns diminish after five, while five one-hour slots fit a single day. Recruit six participants to absorb a likely no-show.

Can a design sprint be run remotely with a distributed team?â–¼

Yes, remote sprints work using Miro or FigJam for whiteboarding, Zoom for sync sessions, and Figma for prototyping. Shift individual exercises like sketching to async work, limit sync blocks to 90 minutes, and adjust the schedule for time zone overlap.

When should you not run a design sprint?â–¼

Skip the sprint when the problem and solution are obvious and you just need to execute, when the team is not bought in, or when the Decider cannot commit to the full week. Sprints are for high-stakes, uncertain decisions, not routine work.

What fidelity should a design sprint prototype have?â–¼

Aim for Goldilocks fidelity: realistic enough to get honest reactions but fake underneath. Use Figma, Keynote, or PowerPoint click-throughs rather than working code, and build only what Friday's test will touch.