tool-design-sprint-prototype-plan

Name: tool-design-sprint-prototype-plan
Author: product-on-purpose

486stars64forks

How to install tool-design-sprint-prototype-plan?

product-on-purpose/pm-skills/tool-design-sprint-prototype-plan

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

Installs into the current project.

Summary

Day 4 (Thursday) move of a Design Sprint that produces the planning artifact for the day. Output covers the prototype role plan (Maker, Stitcher, Writer, Asset Collector, Interviewer), prototype brief (what to build, fidelity bar, time allocation per role), canonical Five-Act Int

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 Prototype Plan (Thursday morning)
4
5	Thursday is the prototype build day. This skill produces the morning planning artifact that makes the build run; it does NOT build the prototype itself. The skill assigns roles, locks the fidelity bar, drafts the Five-Act interview script, defines the trial-run gate, and confirms Friday participants. The actual building (Figma frames, slideware decks, role-play scripts, paper assemblies) is craft work the team owns through the rest of Thursday.
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	- It is Thursday morning of the Design Sprint and Wednesday's storyboard is signed off.
12	- The Friday participant tracker needs a Thursday-morning confirmation check; cancellations now trigger buffer activation.
13	- The interview script needs to be drafted (or refined from a prior sprint's template) before the interviewer can mock-run it Thursday afternoon.
14	- The team needs role assignments before parallel build work begins; ad-hoc assignment Thursday afternoon wastes 1-2 hours.
15
16	## When NOT to Use
17
18	- Wednesday is not closed. Return to `tool-design-sprint-decide-and-storyboard`; without a locked storyboard, the prototype has no spec.
19	- The team is trying to use this skill to build the prototype. The prototype is craft work (per Ratified Decision 1 in the DS integration plan). This skill plans Thursday; the build happens in Figma, Keynote, paper, or whatever the medium is.
20	- The team has decided to skip Friday's trial run. Trial run is the gate that catches "prototype is unreachable" or "interview script confuses customer" before live interviews start. Skipping it converts Friday into a debugging session.
21	- Friday participant cancellations have triggered cohort-shrinks-to-fewer-than-4. Pause the sprint and decide whether to postpone Friday or accept a reduced-evidence test.
22
23	## What This Skill Produces
24
25	A single bundled artifact with five sections:
26
27	1. Prototype role plan: assigns 5 canonical roles (Maker, Stitcher, Writer, Asset Collector, Interviewer) across the team. Roles can double up on small teams; cannot triple up except for Asset Collector.
28	2. Prototype brief: one-page spec covering what to build (storyboard panels in scope), fidelity bar (what "real enough" means for the medium), time allocation per role, and what's explicitly NOT being built.
29	3. Interview script (Five-Act): canonical Five-Act structure (Welcome, Context, Intro, Tasks, Debrief) with team-supplied task wording derived from the storyboard. The act sequence is fixed; only Tasks is heavily customized.
30	4. Trial-run checklist: the gates the prototype must pass Thursday afternoon (canonically 16:00-17:00) before Friday begins. Each gate is a yes/no item the interviewer or Maker confirms.
31	5. Participant confirmation tracker: Thursday morning re-confirmation of all 5 Friday slots; cancellations trigger buffer-slot activation; failures cascade to a cohort-decision moment.
32
33	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Thursday morning artifact.
34
35	## Five Canonical Roles
36
37	Sprint book Chapter 16 defines these 5 roles. The skill assigns them; the humans fill them.
38
39	\| Role \| What they do \| Typical owner \|
40	\|---\|---\|---\|
41	\| Maker \| Builds the prototype surface (Figma frames, Keynote slides, role-play props). Owns visual and

product-on-purposePublisher · 67 listings

Preview

product-on-purpose/pm-skills

# Design Sprint Prototype Plan (Thursday morning)

Thursday is the prototype build day. This skill produces the morning planning artifact that makes the build run; it does NOT build the prototype itself. The ski

Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This

Repoproduct-on-purpose/pm-skills

LicenseApache-2.0

TypeSkills

CategoryDesign

UpdatedJul 2026

Repo stars486

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type

tool-design-sprint-prototype-plan

486stars64forks

View on GitHub

How to install tool-design-sprint-prototype-plan?

product-on-purpose/pm-skills/tool-design-sprint-prototype-plan

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

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 Prototype Plan (Thursday morning)
4
5	Thursday is the prototype build day. This skill produces the morning planning artifact that makes the build run; it does NOT build the prototype itself. The skill assigns roles, locks the fidelity bar, drafts the Five-Act interview script, defines the trial-run gate, and confirms Friday participants. The actual building (Figma frames, slideware decks, role-play scripts, paper assemblies) is craft work the team owns through the rest of Thursday.
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	- It is Thursday morning of the Design Sprint and Wednesday's storyboard is signed off.
12	- The Friday participant tracker needs a Thursday-morning confirmation check; cancellations now trigger buffer activation.
13	- The interview script needs to be drafted (or refined from a prior sprint's template) before the interviewer can mock-run it Thursday afternoon.
14	- The team needs role assignments before parallel build work begins; ad-hoc assignment Thursday afternoon wastes 1-2 hours.
15
16	## When NOT to Use
17
18	- Wednesday is not closed. Return to `tool-design-sprint-decide-and-storyboard`; without a locked storyboard, the prototype has no spec.
19	- The team is trying to use this skill to build the prototype. The prototype is craft work (per Ratified Decision 1 in the DS integration plan). This skill plans Thursday; the build happens in Figma, Keynote, paper, or whatever the medium is.
20	- The team has decided to skip Friday's trial run. Trial run is the gate that catches "prototype is unreachable" or "interview script confuses customer" before live interviews start. Skipping it converts Friday into a debugging session.
21	- Friday participant cancellations have triggered cohort-shrinks-to-fewer-than-4. Pause the sprint and decide whether to postpone Friday or accept a reduced-evidence test.
22
23	## What This Skill Produces
24
25	A single bundled artifact with five sections:
26
27	1. Prototype role plan: assigns 5 canonical roles (Maker, Stitcher, Writer, Asset Collector, Interviewer) across the team. Roles can double up on small teams; cannot triple up except for Asset Collector.
28	2. Prototype brief: one-page spec covering what to build (storyboard panels in scope), fidelity bar (what "real enough" means for the medium), time allocation per role, and what's explicitly NOT being built.
29	3. Interview script (Five-Act): canonical Five-Act structure (Welcome, Context, Intro, Tasks, Debrief) with team-supplied task wording derived from the storyboard. The act sequence is fixed; only Tasks is heavily customized.
30	4. Trial-run checklist: the gates the prototype must pass Thursday afternoon (canonically 16:00-17:00) before Friday begins. Each gate is a yes/no item the interviewer or Maker confirms.
31	5. Participant confirmation tracker: Thursday morning re-confirmation of all 5 Friday slots; cancellations trigger buffer-slot activation; failures cascade to a cohort-decision moment.
32
33	See `references/TEMPLATE.md` for the canonical structure and `references/EXAMPLE.md` for the Brainshelf book-catalog Thursday morning artifact.
34
35	## Five Canonical Roles
36
37	Sprint book Chapter 16 defines these 5 roles. The skill assigns them; the humans fill them.
38
39	\| Role \| What they do \| Typical owner \|
40	\|---\|---\|---\|
41	\| Maker \| Builds the prototype surface (Figma frames, Keynote slides, role-play props). Owns visual and

product-on-purposePublisher · 67 listings

Preview

product-on-purpose/pm-skills

# Design Sprint Prototype Plan (Thursday morning)

Thursday is the prototype build day. This skill produces the morning planning artifact that makes the build run; it does NOT build the prototype itself. The ski

Family contract: [`docs/reference/skill-families/design-sprint-skills-contract.md`](../../docs/reference/skill-families/design-sprint-skills-contract.md). This

Repoproduct-on-purpose/pm-skills

LicenseApache-2.0

TypeSkills

CategoryDesign

UpdatedJul 2026

Repo stars486

First seenJul 22, 2026

People who liked this also viewed

6 picks

Type