Tool Design Sprint Prototype Plan
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 Interview script (Welcome, Context, Intro, Tasks, Debrief), trial-run checklist, and Friday participant confirmation tracker. The actual prototype build is craft work outside the skill's AI invocation surface. Use Thursday morning after Wednesday's storyboard is signed off.
Install
/plugin marketplace add product-on-purpose/pm-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-prototype-plangit clone --depth 1 https://github.com/product-on-purpose/pm-skills.git /tmp/pm-skills
mkdir -p ~/.claude/skills
cp -r /tmp/pm-skills/skills/tool-design-sprint-prototype-plan ~/.claude/skills/tool-design-sprint-prototype-planPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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 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. 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`. ## When to Use - It is Thursday morning of the Design Sprint and Wednesday's storyboard is signed off. - The Friday participant tracker needs a Thursday-morning confirmation check; cancellations now trigger buffer activation. - The interview script needs to be drafted (or refined from a prior sprint's template) before the interviewer can mock-run it Thursday afternoon. - The team needs role assignments before parallel build work begins; ad-hoc assignment Thursday afternoon wastes 1-2 hours. ## When NOT to Use - Wednesday is not closed. Return to `tool-design-sprint-decide-and-storyboard`; without a locked storyboard, the prototype has no spec.
Details
- Skill name
tool-design-sprint-prototype-plan- Repository
- product-on-purpose/pm-skills
- Path
skills/tool-design-sprint-prototype-plan/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Tool Design Sprint Prototype Plan skill do?
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 Interview script (Welcome, Context, Intro, Tasks, Debrief), trial-run checklist, and Friday participant confirmation tracker. The actual prototype build is craft work outside the skill's AI invocation surface. Use Thursday morning after Wednesday's storyboard is signed off.
How do I install the Tool Design Sprint Prototype Plan skill?
Claude Code plugin: /plugin marketplace add product-on-purpose/pm-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Tool Design Sprint Prototype Plan popular?
It lives in product-on-purpose/pm-skills, which has 819 GitHub stars and 104 forks, and is included in 2 curated skill lists.
Related skills
<phase or Classification Skill Name>
819product-on-purpose/pm-skills
<single-line 20-100 word description; include trigger keywords and do not use folded YAML>
Define Hypothesis
819product-on-purpose/pm-skills
Defines a testable hypothesis with clear success metrics and a validation approach. Use when forming assumptions to test or aligning a team on what success looks like, before any experiment is designed. To design the A/B test or experiment that will validate the hypothesis, use measure-experiment-design.
Define Jtbd Canvas
819product-on-purpose/pm-skills
Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job. Use when deeply understanding customer motivations, designing for jobs, or reframing product positioning.
Utility Pm Skill Iterate
819product-on-purpose/pm-skills
Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.
Tool Design Sprint Decide and Storyboard
819product-on-purpose/pm-skills
Day 3 (Wednesday) move of a Design Sprint that runs the art museum layout, heat map, speed critique, straw poll, Decider supervote, rumble-vs-all-in-one decision, and the storyboard that drives Thursday's prototype build. The most decision-heavy day of the sprint. Use Wednesday morning and afternoon after Tuesday's sketches are collected and attribution-stripped. Produces the canonical 5-15 step storyboard that becomes the build spec.
Grill with Docs
559KunoLu/640-skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.