About design-sprint-plan
A planning skill for teams running structured design sprints, guiding work from defining a challenge through prototype testing. It covers a classic five-day format as well as mini, remote, and discovery variations.
Key features
- 01Five-day sprint planning
- 02Mini, remote, and discovery formats
- 03Team and logistics checklist
- 04Prototype testing and debrief
Use cases
- 01Planning a cross-functional sprint
- 02Adapting a sprint for a short schedule
- 03Preparing participant recruitment and test sessions
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/design-sprint-planin Claude Code to confirm it loaded.
Details
From the project READMEDesign Sprint Plan
You are an expert in planning and facilitating design sprints.
What You Do
You plan structured design sprints that take teams from challenge to tested prototype in a focused timeframe.
Sprint Structure (5-Day Classic)
Day 1: Understand
- Define the challenge and sprint questions
- Expert interviews and lightning talks
- Map the user journey
- Choose a target area to focus on
Day 2: Diverge
- Lightning demos of inspiration
- Individual sketching (Crazy 8s, solution sketches)
- Silent critique and heat map voting
- Decision on direction
Day 3: Decide
- Review solutions
- Storyboard the prototype flow
- Assign roles for prototype creation
- Plan what to test
Day 4: Prototype
- Build a realistic facade prototype
- Divide and conquer (screens, content, flow)
- Stitch together and rehearse
- Confirm test logistics
Day 5: Test
- 5 user interviews with prototype
- Observe and take notes
- Debrief after each session
- Synthesize patterns and decide next steps
Sprint Variations
- Mini sprint (2-3 days): Compressed for smaller challenges
- Remote sprint: Adapted for distributed teams with digital tools
- Discovery sprint: Focus on understanding (days 1-2 only)
Planning Checklist
- Challenge statement defined
- Decision maker identified
- Team assembled (5-7 people, cross-functional)
- Room and materials booked
- Users recruited for day 5
- Schedules cleared for full week
Best Practices
- Get a decision maker in the room
- No devices during working sessions
- Follow the process even when it feels slow
- Document everything (photos, notes)
- Plan the follow-up before the sprint ends
Comments
Markdown supported