design-sprint-plan — Claude Code skill: what it does, how to install
Plans structured design sprints to move from a challenge statement to a tested prototype in days. Ideal when you need to compress discovery work into a single week.
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a claude-codeWhat design-sprint-plan does
This skill guides the planning and facilitation of design sprints using the classic five-day framework. Day 1 focuses on understanding the problem and mapping the user journey. Days 2 and 3 cover Crazy 8s sketches and storyboarding the prototype flow. On Day 4 the team builds a realistic facade prototype, and Day 5 is reserved for five user test interviews.
It also provides templates for sprint variations, including 2–3 day mini sprints, remote formats, and discovery sprints limited to the first two days. When an organization needs continuous team cadence rather than an intensive workshop, the author points to team-workflow instead.
The framework requires a cross-functional squad of 5 to 7 people and an active decision maker in the room. Without pre-recruited test users for Day 5 and cleared calendars, the sprint will stall before testing begins.
What it helps with
- map out a 5-day design sprint schedule from challenge to testing
- adapt sprint timelines for remote teams or 2-3 day mini sprints
- prepare team checklists and participant recruitment
- organize prototype storyboarding and assign day 4 production roles
Example prompts for the agent
- Create a 5-day design sprint schedule to test our new onboarding flow
- Set up a 3-day mini sprint plan for a remote product team
- Show the planning checklist and roles needed before starting sprint week
How to install design-sprint-plan
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a claude-code2Manually: put the files in place
~/.claude/skills/design-sprint-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/design-sprint-plan/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a codex2Manually: put the files in place
.agents/skills/design-sprint-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a cursor2Manually: put the files in place
.cursor/skills/design-sprint-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Owl-Listener/designer-skills design-sprint-plan2Manually: put the files in place
.github/skills/design-sprint-plan/SKILL.md1Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/Owl-Listener/designer-skills --path design-ops/skills/design-sprint-planManually: put the files in place
.devin/skills/design-sprint-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about design-sprint-plan
How do I install design-sprint-plan in Claude Code?
Run npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a claude-code. This copies the skill file to ~/.claude/skills/design-sprint-plan/SKILL.md.
What does design-sprint-plan do?
It equips the agent with facilitation steps, scheduling templates, and rules for running design sprints. It details daily milestones from problem framing to running five user test interviews.
What is the difference between design-sprint-plan and team-workflow?
The design-sprint-plan skill compresses discovery and prototyping into a single week. For sustained team cadence and ongoing operational workflows, the repository provides team-workflow.
Source text
SKILL.md · MIT
--- name: design-sprint-plan description: Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use `team-workflow`. --- # Design 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
© Owl-Listener · MIT · Owl-Listener/designer-skills