tool-design-sprint-brief

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

486stars64forks

How to install tool-design-sprint-brief?

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

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

Installs into the current project.

Summary

Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint. Use after the readiness verdict is Go and before Monday begins. Prod

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 Brief
4
5	Produce the brief that aligns the team on challenge, sprint questions, participants, customer recruiting, prototype medium, interview format, logistics, and success criteria before Monday begins. A well-built brief prevents Monday morning from opening with re-litigation of "what are we testing this week?"; a missing or vague brief almost guarantees it.
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`.
8
9	## When to Use
10
11	- The readiness verdict from `tool-design-sprint-readiness` is Go (or Conditional Go with preconditions cleared).
12	- The sprint has dates blocked on calendars and you need the artifact that names what the sprint is for.
13	- The team has customer recruiting active and you need to commit a recruiting plan, honorarium budget, and Friday schedule before recruiting closes.
14	- A skeptical exec wants to know "what is the team doing for five days plus customer cost?" and you need an answer that fits on two pages.
15
16	## When NOT to Use
17
18	- The sprint has already started. The brief is a prep artifact, not an in-sprint deliverable. If Monday is happening, run `tool-design-sprint-map-and-target` instead.
19	- The readiness verdict is Wait. The brief cannot fix an unready team; close the preconditions first, then re-run readiness, then invoke this skill.
20	- The team wants a stakeholder strategy document. The brief is internal prep, not an external deliverable. If a stakeholder document is needed, that is a downstream artifact (the Friday scorecard or the next-step memo).
21	- Customer recruiting has not started. The brief locks the recruiting plan but cannot replace the recruiter. If no recruiter is named, go back to readiness Wait verdict.
22
23	## What This Skill Produces
24
25	A single bundled artifact with nine sections:
26
27	1. Challenge statement and why-now: one paragraph naming the testable challenge and the urgency that justifies a sprint this week vs. later.
28	2. Sprint questions: 2-4 specific questions the Friday testing answers. The highest-risk assumption from any prior Foundation Sprint becomes the lead question.
29	3. Decider attendance windows: the load-bearing moments (Mon AM, Wed AM, Fri PM at minimum); fully blocked if available.
30	4. Team roster with role assignments: who is in the room each day and what role each person plays through the week.
31	5. Customer recruiting plan: target profile, source, count, incentive, recruiter owner, recruiting deadline, Friday schedule.
32	6. Prototype medium decision: clickable, slideware, service role-play, paper, physical mock, or other; with rationale.
33	7. Interview format: live or remote; moderated or unmoderated; recording and consent posture; observer-room setup.
34	8. Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
35	9. Success criteria: observable outcomes that mark the sprint successful or not.
36
37	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog brief.
38
39	## Inference Inputs
40
41	\| Input \| What the skill does with it \|
42	\|---\|---\|
43	\| Readiness verdict and recommendations (from `tool-design-sprint-readiness`) \| Pulls the recommended attendees, customer recruiting plan, pre-sprint activities, and prototype medium proposal; flags any precondition that has not been closed \|
44	\| Challenge description \| Compresses into the Challenge Statement

People who liked this also viewed

6 picks

Type

tool-design-sprint-brief

486stars64forks

View on GitHub

How to install tool-design-sprint-brief?

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

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

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 Brief
4
5	Produce the brief that aligns the team on challenge, sprint questions, participants, customer recruiting, prototype medium, interview format, logistics, and success criteria before Monday begins. A well-built brief prevents Monday morning from opening with re-litigation of "what are we testing this week?"; a missing or vague brief almost guarantees it.
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`.
8
9	## When to Use
10
11	- The readiness verdict from `tool-design-sprint-readiness` is Go (or Conditional Go with preconditions cleared).
12	- The sprint has dates blocked on calendars and you need the artifact that names what the sprint is for.
13	- The team has customer recruiting active and you need to commit a recruiting plan, honorarium budget, and Friday schedule before recruiting closes.
14	- A skeptical exec wants to know "what is the team doing for five days plus customer cost?" and you need an answer that fits on two pages.
15
16	## When NOT to Use
17
18	- The sprint has already started. The brief is a prep artifact, not an in-sprint deliverable. If Monday is happening, run `tool-design-sprint-map-and-target` instead.
19	- The readiness verdict is Wait. The brief cannot fix an unready team; close the preconditions first, then re-run readiness, then invoke this skill.
20	- The team wants a stakeholder strategy document. The brief is internal prep, not an external deliverable. If a stakeholder document is needed, that is a downstream artifact (the Friday scorecard or the next-step memo).
21	- Customer recruiting has not started. The brief locks the recruiting plan but cannot replace the recruiter. If no recruiter is named, go back to readiness Wait verdict.
22
23	## What This Skill Produces
24
25	A single bundled artifact with nine sections:
26
27	1. Challenge statement and why-now: one paragraph naming the testable challenge and the urgency that justifies a sprint this week vs. later.
28	2. Sprint questions: 2-4 specific questions the Friday testing answers. The highest-risk assumption from any prior Foundation Sprint becomes the lead question.
29	3. Decider attendance windows: the load-bearing moments (Mon AM, Wed AM, Fri PM at minimum); fully blocked if available.
30	4. Team roster with role assignments: who is in the room each day and what role each person plays through the week.
31	5. Customer recruiting plan: target profile, source, count, incentive, recruiter owner, recruiting deadline, Friday schedule.
32	6. Prototype medium decision: clickable, slideware, service role-play, paper, physical mock, or other; with rationale.
33	7. Interview format: live or remote; moderated or unmoderated; recording and consent posture; observer-room setup.
34	8. Logistics plan: dates, hours, location, format (in-person, remote, hybrid), tools, daily rhythm.
35	9. Success criteria: observable outcomes that mark the sprint successful or not.
36
37	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog brief.
38
39	## Inference Inputs
40
41	\| Input \| What the skill does with it \|
42	\|---\|---\|
43	\| Readiness verdict and recommendations (from `tool-design-sprint-readiness`) \| Pulls the recommended attendees, customer recruiting plan, pre-sprint activities, and prototype medium proposal; flags any precondition that has not been closed \|
44	\| Challenge description \| Compresses into the Challenge Statement

People who liked this also viewed

6 picks

Type