Skip to main content
skill CX Codex

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.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Owl-Listener/designer-skills --skill design-sprint-plan -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/design-sprint-plan/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/design-sprint-plan/

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

Similar skills

Everything for Design →

From the same set111

critique-typography Audits typography on a rendered screen: scale usage, readability, consistency and token compliance. Useful during UI review. CX Codex +1 2,000installs version-control-strategy Defines version control strategies for design files, component libraries, and tokens. It helps teams stop chaotic file history and establish clear release routines. CX Codex +1 2,000installs critique-visual-hierarchy This skill reviews a rendered screen across four dimensions and tells you where the eye actually lands. Useful when attention goes to the wrong place. CX Codex +1 2,000installs click-test-plan Turns a findability question into a test plan: where users click first and whether they locate items in your navigation. Useful when a design is ready but untested. CX Codex +1 2,000installs design-system-adoption Builds an adoption strategy and enablement materials when teams are bypassing an existing design system. It helps plan education, migration support and measurement. CX Codex +1 2,000installs summarize-interview Turns a single interview transcript into themes, quotes and follow-up tasks, in a format you can hand to stakeholders. CX Codex +1 2,000installs team-workflow Designs an operating cadence for design teams, covering task tracking, regular rituals, and developer handoff. Helpful when day-to-day design collaboration lacks structure. CX Codex +1 2,000installs opportunity-framework Turns a pile of possible improvements into a ranked roadmap using impact-effort and RICE. Handy when ideas outnumber capacity. CX Codex +1 2,000installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor