workflow-design-sprint

workflow-design-sprint is a command for Claude Code from product-on-purpose/pm-skills. It costs 26 tokens per session (697 once invoked), scanned A, original, Apache-2.0.

A structured five-day workshop that takes one product challenge from problem framing through a prototype and customer interviews to a decision to build, improve, change direction, or stop. A prototype is a quick model used to test an idea before fully building it.

In plain words
What is it for?
Use it to assess readiness, define the challenge, map the customer journey, choose what to prototype, create a one-day prototype, and test it with five customer interviews.
Why use it?
It lets a team test a product idea with customers quickly and use evidence before committing to development. The fixed sequence helps turn a vague challenge into a concrete decision within one work week.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the pm-skills plugin — 69 skills, 11 commands, 6 agents, 2 hooks shipped together

Good fit Use it to assess readiness, define the challenge, map the customer journey, choose what to prototype, create a one-day prototype, and test it with five customer interviews.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/product-on-purpose/pm-skills/workflow-design-sprint
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/product-on-purpose/pm-skills

Made for: Claude Code.

Or install pm-skills, the plugin that ships this one along with the rest of its 69 skills, 11 commands, 6 agents, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for workflow-design-sprint

README.md
[![agentmods](https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-design-sprint/github.svg)](https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-design-sprint)
Your own site
<a href="https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-design-sprint"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-design-sprint/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for workflow-design-sprint

Your own site · 80×15
<a href="https://agentmods.dev/commands/product-on-purpose/pm-skills/workflow-design-sprint"><img src="https://agentmods.dev/badge/commands/product-on-purpose/pm-skills/workflow-design-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.00697
Opus 5 $0.00013 $0.00349
Sonnet 5 $0.00005 $0.00139
Haiku 4.5 $0.00003 $0.00070

Measured 11d ago against content hash ce05d94a992a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

workflow-design-sprint scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/workflow-design-sprint.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 50 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 50 lines · 26 tokens per session scan A ce05d94a992a

Subscribe to this mod's changes

workflow-design-sprint is a command published in the GitHub repository product-on-purpose/pm-skills (658 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 697 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.