Tool Design Sprint Readiness
Pre-sprint diagnostic that determines whether a team should run a Design Sprint now...
Install
npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness -g -a claude-code -y- Repository
- product-on-purpose/pm-skills780
- Category
- Design
- Updated
- 5d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,575 tokens
- Runs scripts
- No, instructions only
What it does
Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, customer recruiting plan, and pre-sprint activities. Use when a team is considering starting a Design Sprint and wants a fast yes/no diagnosis before committing five days of team time and customer recruiting cost.
Design Sprint Readiness
Assess whether a Design Sprint fits the team's current situation. Design Sprint failure modes are expensive: five consecutive days of a 4-7 person team, plus customer recruiting cost (typically 5 strangers paid honoraria), plus the prototype build. A 30-45 minute readiness diagnostic catches the failure modes before that commitment is made.
Family contract: site/src/content/docs/reference/skill-families/design-sprint-skills-contract.md. This skill is a member of design-sprint-skills and conforms to the family frontmatter and Decider Checkpoint requirements.
When to Use
- A team is considering starting a Design Sprint and needs a fast diagnosis before committing five days plus customer recruiting effort.
- A team has just completed a Foundation Sprint and is deciding whether the next test should be a Design Sprint, a smaller experiment, or direct build. The Founding Hypothesis is consumed as optional input context (no separate bridge skill artifact is required).
- An existing sprint commitment is on the calendar and the team wants to validate that prerequisites (Decider, customers, prototype medium) are in place.
- Re-running a Design Sprint after an inconclusive first sprint: use to confirm the new challenge framing and customer access are ready.
