tool-design-sprint-readiness

Name: tool-design-sprint-readiness
Author: product-on-purpose

486stars64forks

How to install tool-design-sprint-readiness?

product-on-purpose/pm-skills/tool-design-sprint-readiness

$npx -y skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness

Installs into the current project.

Summary

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 activi

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2
3	# Design Sprint Readiness
4
5	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.
6
7	Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../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.
8
9	## When to Use
10
11	- A team is considering starting a Design Sprint and needs a fast diagnosis before committing five days plus customer recruiting effort.
12	- 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).
13	- An existing sprint commitment is on the calendar and the team wants to validate that prerequisites (Decider, customers, prototype medium) are in place.
14	- Re-running a Design Sprint after an inconclusive first sprint: use to confirm the new challenge framing and customer access are ready.
15
16	## When NOT to Use
17
18	- The team has already decided to run the sprint and just needs the brief. Use `tool-design-sprint-brief` instead.
19	- The team has no clear challenge and is still in discovery. Run problem framing or a Foundation Sprint first; a Design Sprint depends on a sprint-worthy challenge.
20	- Low-stakes tweaks where five days of team time would be disproportionate. Use a lighter experiment design instead.
21	- No customer access for Friday testing and no realistic recruiting plan. A Design Sprint that cannot test on Friday is just a four-day workshop with no learning event.
22	- No Decider available and one cannot be appointed. Design Sprint requires fast decisions Wednesday and pre-test Thursday; without authority the sprint produces options without commitment.
23
24	## What This Skill Produces
25
26	A single bundled artifact with six sections:
27
28	1. Readiness verdict: Go / Conditional Go / Wait
29	2. Diagnosis: what is in place, what is missing, what is uncertain
30	3. Recommended preconditions (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint
31	4. Recommended attendee list (when verdict is Go or Conditional Go): the 4-7 people who should be in the room, with role expectations
32	5. Customer recruiting plan (when verdict is Go or Conditional Go): target profile, source, count, incentive, recruiter owner, recruiting deadline (typically 7-10 days before Friday)
33	6. Pre-sprint activities (when verdict is Go): the prep work to complete in the days before Monday
34
35	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for a worked example using the Brainshelf book-catalog thread.
36
37	## Inference Inputs
38
39	The skill runs an inference pass over these inputs to produce the verdict:
40
41	\| Input \| What the skill does with it \|
42	\|---\|---\|
43	\| Challenge description \| Determines whether the challenge is sprint-worthy (specific enough to prototype in 4 days; big enough to justify 5 team-days) \|
44	\| Existing hypothesis (from Foundation Sprint or elsewhere) \| Confirms there is a testable bet, not exploratory discovery. Highest-risk assumption from the FS scorecard becomes a candidate sprint question \|
45	\| Customer access status \| Critical. Without realistic Friday customer access, the sprint cannot test \|
46	\| Decider name and full-week avai

People who liked this also viewed

6 picks

Type

tool-design-sprint-readiness

486stars64forks

View on GitHub

How to install tool-design-sprint-readiness?

product-on-purpose/pm-skills/tool-design-sprint-readiness

$npx -y skills add product-on-purpose/pm-skills --skill tool-design-sprint-readiness

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- PM-Skills \| https://github.com/product-on-purpose/pm-skills \| Apache 2.0 -->
2
3	# Design Sprint Readiness
4
5	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.
6
7	Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../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.
8
9	## When to Use
10
11	- A team is considering starting a Design Sprint and needs a fast diagnosis before committing five days plus customer recruiting effort.
12	- 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).
13	- An existing sprint commitment is on the calendar and the team wants to validate that prerequisites (Decider, customers, prototype medium) are in place.
14	- Re-running a Design Sprint after an inconclusive first sprint: use to confirm the new challenge framing and customer access are ready.
15
16	## When NOT to Use
17
18	- The team has already decided to run the sprint and just needs the brief. Use `tool-design-sprint-brief` instead.
19	- The team has no clear challenge and is still in discovery. Run problem framing or a Foundation Sprint first; a Design Sprint depends on a sprint-worthy challenge.
20	- Low-stakes tweaks where five days of team time would be disproportionate. Use a lighter experiment design instead.
21	- No customer access for Friday testing and no realistic recruiting plan. A Design Sprint that cannot test on Friday is just a four-day workshop with no learning event.
22	- No Decider available and one cannot be appointed. Design Sprint requires fast decisions Wednesday and pre-test Thursday; without authority the sprint produces options without commitment.
23
24	## What This Skill Produces
25
26	A single bundled artifact with six sections:
27
28	1. Readiness verdict: Go / Conditional Go / Wait
29	2. Diagnosis: what is in place, what is missing, what is uncertain
30	3. Recommended preconditions (when verdict is Wait or Conditional Go): the prerequisite work the team should do before the sprint
31	4. Recommended attendee list (when verdict is Go or Conditional Go): the 4-7 people who should be in the room, with role expectations
32	5. Customer recruiting plan (when verdict is Go or Conditional Go): target profile, source, count, incentive, recruiter owner, recruiting deadline (typically 7-10 days before Friday)
33	6. Pre-sprint activities (when verdict is Go): the prep work to complete in the days before Monday
34
35	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for a worked example using the Brainshelf book-catalog thread.
36
37	## Inference Inputs
38
39	The skill runs an inference pass over these inputs to produce the verdict:
40
41	\| Input \| What the skill does with it \|
42	\|---\|---\|
43	\| Challenge description \| Determines whether the challenge is sprint-worthy (specific enough to prototype in 4 days; big enough to justify 5 team-days) \|
44	\| Existing hypothesis (from Foundation Sprint or elsewhere) \| Confirms there is a testable bet, not exploratory discovery. Highest-risk assumption from the FS scorecard becomes a candidate sprint question \|
45	\| Customer access status \| Critical. Without realistic Friday customer access, the sprint cannot test \|
46	\| Decider name and full-week avai

People who liked this also viewed

6 picks

Type