Workflow Design Sprint

Run the Design Sprint workflow (5-day prototype-and-test arc producing a Decider's build/iterate/pivot/stop call)

Published by @product-on-purpose·0 agent reads / 30d·0 saves·

Run the Design Sprint, a structured five-day workshop (Knapp/Zeratsky/Kowitz) that takes a single challenge from blank-page Monday to a validated-or-invalidated Friday, grounded in five customer interviews against a one-day prototype.

This workflow chains the 7 tool-design-sprint-* skills in their canonical sequence, with tool-note-and-vote invoked at decision moments (the Monday HMW heat-map and optional target supervote, and the Wednesday heat-map plus straw poll). For each step, read the skill instructions and follow them.

Note: Design Sprint is a workshop methodology, NOT an agile / Scrum sprint. For pm-skills' agile sprint planning, use /workflow-sprint-planning.

Workflow Steps

Step 1: Readiness

Use the tool-design-sprint-readiness skill from skills/tool-design-sprint-readiness/SKILL.md to diagnose whether the team should run a Design Sprint now, postpone, or do prerequisite work first.

Step 2: Brief

Use the tool-design-sprint-brief skill from skills/tool-design-sprint-brief/SKILL.md to lock the challenge, sprint questions, team, customer recruiting plan, prototype medium, interview format, and success criteria before Monday.

Step 3: Map and Target (Monday)

Use the tool-design-sprint-map-and-target skill from skills/tool-design-sprint-map-and-target/SKILL.md to produce the long-term goal, sprint questions, customer/system map, HMW cluster board, and the Decider's target moment.

Step 4: Sketch (Tuesday)

Use the tool-design-sprint-sketch skill from skills/tool-design-sprint-sketch/SKILL.md to structure lightning demos and the four-step independent solution sketch protocol.

Step 5: Decide and Storyboard (Wednesday)

Use the tool-design-sprint-decide-and-storyboard skill from skills/tool-design-sprint-decide-and-storyboard/SKILL.md to run the art-museum layout, heat map, speed critique, straw poll, Decider supervote, and storyboard.

Step 6: Prototype Plan (Thursday morning)

Use the tool-design-sprint-prototype-plan skill from skills/tool-design-sprint-prototype-plan/SKILL.md to produce the role plan, Five-Act interview script, trial-run checklist, and participant confirmation tracker.

Step 7: Test and Score (Friday)

Use the tool-design-sprint-test-and-score skill from skills/tool-design-sprint-test-and-score/SKILL.md to run the 5 customer interviews, score the sprint questions, capture hot takes, and produce the Decider's build / iterate / pivot / stop call.

Throughout, use the tool-note-and-vote skill from skills/tool-note-and-vote/SKILL.md to run structured group decisions at each decision moment.

Output

Produce each artifact in sequence. The Decider's call (Step 7) is the final output, grounded in the five customer interviews against the prototype.

Reference the Design Sprint workflow at _workflows/design-sprint.md for additional guidance.

Context from user: $ARGUMENTS

Bundled with this artifact

2 files

Reference files that ship alongside this artifact. Agents pull these in only when the task needs them.

More on the bench

SKILL0

Pptx

Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.

product-management+1
0
SKILL0

Knowledge Management

Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.

customer-success+2
0
SKILL0

Customer Research

Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.

customer-success+1
0