tool-design-sprint-prototype-plan

Generates the Thursday planning artifact for a Design Sprint prototype build day.

640|81|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-prototype-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tool-design-sprint-prototype-plan
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-prototype-plan
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill tool-design-sprint-prototype-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Thursday of a Design Sprint fails when teams start building without assigned roles, an agreed fidelity bar, or a drafted interview script, wasting hours on ad-hoc coordination. This Skill produces the complete Thursday-morning planning artifact so parallel prototype build work can start immediately.

Core Features & Use Cases

  • Prototype Role Plan: Assigns the five canonical Sprint roles (Maker, Stitcher, Writer, Asset Collector, Interviewer) across the team, including doubling-up rules for small teams.
  • Prototype Brief & Five-Act Interview Script: Locks the fidelity bar and scope exclusions, then drafts the canonical Welcome, Context, Intro, Tasks, and Debrief interview script with team-customized task wording.
  • Trial-Run Checklist & Participant Tracker: Defines the Thursday-afternoon gate criteria the prototype must pass and re-confirms all five Friday interview slots with buffer activation rules.
  • Use Case: On Thursday morning after Wednesday's storyboard is signed off, a facilitator uses this Skill to produce the role plan, brief, interview script, trial-run checklist, and participant tracker, then obtains Decider sign-off before the team disperses into parallel Figma build work.

Quick Start

Use the design sprint prototype plan skill to generate Thursday's planning artifact from Wednesday's signed-off storyboard and sprint questions.

Frequently Asked Questions about tool-design-sprint-prototype-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan Thursday of a Design Sprint?

Run this skill Thursday morning after Wednesday's storyboard is signed off. It produces a role plan assigning Maker, Stitcher, Writer, Asset Collector, and Interviewer, a prototype brief with a fidelity bar, a Five-Act interview script, a trial-run checklist, and a participant confirmation tracker, all within a 90-minute timebox.

What are the five roles in a Design Sprint prototype day?

The five canonical roles from the Sprint book are Maker (builds prototype surfaces), Stitcher (connects them into a flow), Writer (writes copy), Asset Collector (sources images and sample data), and Interviewer (drafts and runs the Five-Act script). On a 4-person team, Maker and Stitcher typically merge while Interviewer stays dedicated.

What is the Five-Act interview structure in a Design Sprint?

The Five-Act interview consists of Welcome (5 min), Context (5-10 min), Intro (5 min), Tasks (20-30 min), and Debrief (5-10 min). The act sequence is fixed; only the Tasks act is heavily customized with open-ended tasks derived from the storyboard.

Does this skill build the prototype for Thursday?

No. The skill only produces the Thursday-morning planning artifact; the actual prototype build in Figma, Keynote, paper, or other media is craft work the team owns for the rest of Thursday. Using it to build the prototype is explicitly out of scope.

When should I not use the Design Sprint prototype plan skill?

Do not use it if Wednesday's storyboard is not locked, since the prototype has no spec without it. Also avoid it if the team plans to skip the Thursday trial run, or if Friday participant cancellations have shrunk the cohort below four, which requires pausing the sprint.

What happens if Friday interview participants cancel on Thursday?

The participant confirmation tracker re-confirms all five Friday slots Thursday morning. Cancellations trigger buffer-slot activation, and if the cohort shrinks below four participants, the sprint pauses to decide whether to postpone Friday or accept a reduced-evidence test.