# Tool Design Sprint Readiness

Pre-sprint diagnostic that determines whether a team should run a Design Sprint now...

- Repository: https://github.com/product-on-purpose/pm-skills (780 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness -g -a claude-code -y`
Codex: `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness -g -a codex -y`
Cursor: `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness -g -a cursor -y`
Gemini CLI: `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add product-on-purpose/pm-skills`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

# 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`](../../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.

## When NOT to Use

The rest: https://github.com/product-on-purpose/pm-skills/blob/HEAD/skills/tool-design-sprint-readiness/SKILL.md