Design Sprint Plan
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`.
Install
/plugin marketplace add Owl-Listener/designer-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/designer-skills --skill design-sprint-plangit clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-ops/skills/design-sprint-plan ~/.claude/skills/design-sprint-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Details
- Skill name
design-sprint-plan- Repository
- Owl-Listener/designer-skills
- Path
design-ops/skills/design-sprint-plan/SKILL.md- License
- MIT
- Repo updated
- 5 September 2026
FAQ
What does the Design Sprint Plan skill do?
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`.
How do I install the Design Sprint Plan skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Design Sprint Plan popular?
It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.
Related skills
A B Test Design
3.4kOwl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Accessibility Audit
3.4kOwl-Listener/designer-skills
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Accessibility Test Plan
3.4kOwl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Journey Map
3.4kOwl-Listener/designer-skills
Map one persona's end-to-end experience with stages, touchpoints, emotions, and pain points. Use when improving an existing experience. For the multi-channel ecosystem use `experience-map` (ux-strategy); for screen-level paths use `user-flow-diagram` (prototyping-testing).
Design QA Checklist
3.4kOwl-Listener/designer-skills
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use `handoff-spec`.
Prototype Strategy
3.4kOwl-Listener/designer-skills
Choose prototype fidelity and method to match the design question and the decision at stake. Use before building a prototype. For what to test once it exists, use `test-scenario`.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.