Tool Design Sprint Decide And Storyboard logo

Tool Design Sprint Decide And Storyboard

Organization
product-on-purpose
tool-design-sprint-decide-and-storyboard

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.

Overview

Publisherproduct-on-purpose
Repositorypm-skills
Skill nametool-design-sprint-decide-and-storyboard
Stars
717
Forks
92
Bundled files
3
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by product-on-purpose on GitHub. Read the source before you install it.

Installation

Install the Tool Design Sprint Decide And Storyboard AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-decide-and-storyboard
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git 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-decide-and-storyboard .claude/skills/tool-design-sprint-decide-and-storyboard
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Tool Design Sprint Decide And Storyboard in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Tool Design Sprint Decide And Storyboard on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Tool Design Sprint Decide And Storyboard is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Design Sprint Decide and Storyboard (Wednesday)

Wednesday is the most decision-heavy day of the Design Sprint. The skill runs the art museum layout (sketches posted anonymously on the wall), heat map (silent dot-vote stickers on promising parts), speed critique (3 minutes per sketch summarizing what the team sees), straw poll (each team member's top choice), and the Decider's supervote (the call that triggers the storyboard). Then the team decides whether to rumble (storyboard two sketches as competing prototypes) or all-in-one (storyboard one). The day ends with a 5-15 step storyboard that drives Thursday's build.

Family contract: docs/reference/skill-families/design-sprint-skills-contract.md. This skill is a member of design-sprint-skills.

When to Use

  • It is Day 3 of the Design Sprint and Tuesday's sketches are collected, attribution-stripped, and uploaded to the shared workspace.
  • The Decider is present for the full morning (heat map plus critique plus straw poll plus supervote happen 09:00-12:30 canonically).
  • The team has accepted that the supervote is the Decider's call, not a consensus average.
  • Thursday's prototype build needs a storyboard by Wednesday end-of-day or the build cannot start clean Thursday morning.

When NOT to Use

  • Tuesday is not closed. Return to tool-design-sprint-sketch; without independent sketches, the heat-map is meaningless.
  • Sketcher attribution leaked into Wednesday morning. The Facilitator must re-strip before the heat-map begins; voting on sketchers contaminates the day.
  • The Decider is absent. Wednesday's supervote cannot be delegated; without the Decider, the day produces a recommendation, not a decision.
  • The team is treating the supervote as advisory. The supervote is the call. Re-litigating it Thursday morning is sprint failure.

What This Skill Produces

A single bundled artifact with seven sections:

  1. Art museum layout: how sketches are arranged for viewing (typically wall or shared Figma board); attribution stripped; sketches labeled A / B / C / D / etc. in randomized order.
  2. Heat map: silent dot-vote stickers (typically 3 small dots per voter) placed on the most compelling PARTS of any sketch; voters can stack dots on the same element.
  3. Speed critique notes: 3-minute structured walkthrough per sketch by the Facilitator (or rotated team member) summarizing what the team sees; the sketcher does NOT explain their own sketch; concerns are captured as "what would worry me" notes.
  4. Straw poll results: each team member places one larger sticker (typically 1 large dot per voter) on the sketch they would pick if it were their call. Non-binding; informs the Decider.
  5. Supervote: the Decider places their supervote sticker (typically 3 large dots or a distinctively-colored sticker). The supervote is the decision. The Decider can place multiple supervotes on different sketches if running a rumble.
  6. Rumble vs all-in-one decision: the Decider chooses to storyboard one sketch (all-in-one; default) or two sketches as competing prototypes (rumble; chosen when the supervotes split clearly across two distinct approaches).
  7. Storyboard: 5-15 step storyboard derived from the supervoted sketch(es); each panel shows what the customer sees and what they do; specific enough that Thursday's build can begin without re-debating the design.

See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for the Brainshelf book-catalog Wednesday artifact.

Wednesday Time Structure

The full Wednesday workshop is approximately 7 hours (09:00-12:30 + 13:30-17:00). The skill's bundled artifact emerges across the day:

  • 09:00-09:15: Welcome + Tuesday recap + Wednesday agenda
  • 09:15-09:30: Art museum setup; Facilitator confirms sketches are attribution-stripped and labeled A/B/C/D
  • 09:30-09:45: Heat map (silent; 15 minutes; team places dot stickers on compelling parts)
  • 09:45-10:45: Speed critique (3 min per sketch; sketchers silent during their own sketch's critique)
  • 10:45-11:00: Break
  • 11:00-11:15: Straw poll (silent; each person places 1 large dot on their pick)
  • 11:15-11:30: Decider's supervote and rumble vs all-in-one call
  • 11:30-12:30: Storyboard framing (which panels matter most; which map steps to cover; storyboard scope)
  • 12:30-13:30: Lunch
  • 13:30-16:30: Storyboard build (Facilitator drives; team contributes panel content; storyboard reaches 5-15 panels)
  • 16:30-17:00: Day-end review; Thursday build kickoff prep (who builds, who supports, what tools, what gets prebuilt overnight)

This skill's 210-minute timebox covers the Facilitator-led portions (heat map setup, critique, straw poll, supervote, storyboard build).

Common Pitfalls

  • Consensus drift instead of Decider supervote. The most common failure: the team votes, the Facilitator averages, and the Decider rubber-stamps the average. The Decider's call is the Decider's call; the straw poll is input, not result.
  • Storyboard too vague. "User captures a book" is not a storyboard panel; "user opens camera surface, points at book held at arm's length, sees recognized cover appear in bottom card within 1.5 seconds, taps the card to commit" is. Vague storyboards force Thursday's builders to re-debate design.
  • Skipping critique to save time. Critique surfaces concerns the storyboard must address. Skipping it produces a storyboard that hits Thursday and immediately re-surfaces every concern that should have been addressed Wednesday.
  • Sketcher explaining their own sketch. During critique, the sketcher is silent. The point is to test whether the sketch communicates without the artist. If the team can't read the sketch, that's data, not a bug.
  • Rumble chosen when all-in-one was right (or vice versa). Rumble is appropriate when 2 distinct supervoted approaches are both worth testing AND the team has Thursday capacity to build 2 prototypes. Default is all-in-one. Rumble is exception, not norm.
  • Storyboard scope too broad. 5-15 panels, not 50. The storyboard covers the target moment (from Monday) plus 1-2 panels of setup and 1-2 panels of outcome; it does NOT cover the full product.

Cross-Skill Usage

Prerequisites: tool-design-sprint-sketch. Decide and Storyboard consumes Tuesday's sketches as input. Without independent sketches, this skill has no material to heat-map.

This skill invokes tool-note-and-vote twice during the morning: once for the heat-map (small-dot voting) and once for the straw poll (large-dot voting). The supervote itself is the Decider's call after seeing both vote distributions; it does NOT delegate to note-and-vote.

Next invocation in the sprint: tool-design-sprint-prototype-plan Thursday morning.

Canonical Sources

Decider Checkpoint

This skill ends with a Decider Checkpoint in references/TEMPLATE.md. The Decider's supervote earlier in the day is the substantive decision; the end-of-day checkpoint confirms the storyboard is build-ready (specific enough; covers the target moment plus setup plus outcome panels; no remaining hand-waving). Without sign-off, Thursday's build begins with ambiguity and Friday's test risks being a test of the wrong artifact.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Tool Design Sprint Decide And Storyboard AI skill do?

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.

Why use Tool Design Sprint Decide And Storyboard on TypingMind?

Because you install it once and use it with any model. Tool Design Sprint Decide And Storyboard is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Tool Design Sprint Decide And Storyboard in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/product-on-purpose/pm-skills/tree/main/skills/tool-design-sprint-decide-and-storyboard. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Tool Design Sprint Decide And Storyboard?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Tool Design Sprint Decide And Storyboard?

As many as you like. As long as a model supports skills, you can use Tool Design Sprint Decide And Storyboard with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Tool Design Sprint Decide And Storyboard AI skill free?

Yes. It is published on GitHub by product-on-purpose under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇