New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Tool Design Sprint Map And Target

by product-on-purpose in product-on-purpose/pm-skills

Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert…

Apache-2.0Auto-check passedMedia & Creative

Install Tool Design Sprint Map And Target

skills CLI
$ npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-map-and-target -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install product-on-purpose/pm-skills tool-design-sprint-map-and-target --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/product-on-purpose/pm-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tool-design-sprint-map-and-target .claude/skills/tool-design-sprint-map-and-target && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tool-design-sprint-map-and-target
GitHub stars
716
Token cost
~2.2k tokens
SKILL.md length
1,040 words
Files
4 (incl. references)
Skills in repo
68
Repo updated
First seen
Licence
Apache-2.0

At a glance

Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert…

  • Works in 6 steps: Long-term goal: one sentence naming… → Sprint questions: 3-7 questions… → Customer or system map: 5-15 step flow… → …
  • Tasks that involve Comics and storyboards
  • SKILL.md covers When to Use, When NOT to Use, What This Skill Produces and Inference Inputs, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tool Design Sprint Map And Target is an agent skill from product-on-purpose/pm-skills. Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment. Use Day 1 morning and afternoon after the sprint brief is locked. Sets the design target for Tuesday's sketches and Wednesday's storyboard.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `HISTORY.md`, `references/EXAMPLE.md` and `references/TEMPLATE.md`).

It sits in Media & Creative, covering Comics and storyboards. The repository describes itself as: 68 plug-and-play, best-practice product management skills for AI agents: 30 Triple Diamond phase + 11 foundation + 12 utility + 15 tool (Foundation Sprint + Design Sprint). Plus… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Comics and storyboards

Example prompts

  • “s sketches and Wednesday”
  • “/tool-design-sprint-map-and-target”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Long-term goal: one sentence naming success in 1-5 years. Aspirational; cannot be hit in this sprint, but should be visible from the…
  2. Sprint questions: 3-7 questions converting team fears into testable risks. Phrased as "Can we... ?" or "Will... ?" or "How... ?"; NOT…
  3. Customer or system map: 5-15 step flow from key player(s) at the left to outcome (long-term goal) at the right. Includes major actors…
  4. Expert interview notes: synthesized observations from 2-4 cameo experts interviewed Monday afternoon. Surfaced as HMW candidates for the…
  5. HMW cluster board: 30-100+ How Might We notes from the team, clustered into 4-8 themes; voted with tool-note-and-vote heat-map mechanic to…
  6. Target moment: the single point on the map (or a tight cluster of points) the Decider picks as the prototyping target. Wednesday's…

What it can do on your machine

Read from SKILL.md and the folder at commit 1cef1a9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • gv.com
    • character.vc
    • designsprintkit.withgoogle.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tool Design Sprint Map And Target loads about 2.2k tokens when it runs, and up to ~6.1k if it reads all its reference files. Until then it costs about 115 tokens; SKILL.md has 1,040 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~115
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from product-on-purpose/pm-skills at commit 1cef1a9, republished under its Apache-2.0 licence (© product-on-purpose). 1,040 words, ~2,239 tokens.

Download SKILL.mdSave it as .claude/skills/tool-design-sprint-map-and-target/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
tool-design-sprint-map-and-target
description
Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment. Use Day 1 morning and afternoon after the sprint brief is locked. Sets the design target for Tuesday's sketches and Wednesday's storyboard.
license
Apache-2.0
metadata.classification
tool
metadata.version
1.0.0
metadata.updated
2026-07-04
metadata.tool
design-sprint
metadata.move
map-and-target
metadata.category
discovery
metadata.frameworks
design-sprint, sprint, character-note-and-vote
metadata.timebox_minutes
105
metadata.roles
facilitator, decider, pm, design, engineering, researcher, customer-expert
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Design Sprint Map and Target (Monday)

Produce Monday's bundled artifact: the long-term goal that names success in 1-5 years; 3-7 sprint questions converting team fears into testable risks; a 5-15 step customer or system map from key player to outcome; expert interview notes from cameo experts run in parallel; HMW (How Might We) clusters synthesized from the team; and the Decider's chosen target moment. Monday's output becomes Tuesday's design target.

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 1 of the Design Sprint and the brief is locked (via tool-design-sprint-brief).
  • The team is together (in-person, remote, or hybrid) for the full Monday workshop.
  • Expert interviews are scheduled for Monday afternoon (cameo role; 15-30 minutes each).
  • The team needs to converge from "five days of work ahead" to "this specific target moment is what we're prototyping."

When NOT to Use

  • The brief is not locked. Return to tool-design-sprint-brief; without sprint questions, this skill has nothing to converge toward.
  • The challenge is so broad that "long-term goal" would be longer than 5 years. Return to problem framing.
  • The team is missing the Decider. The target-moment selection at the end of Monday is the Decider's call; without that call the team disperses Tuesday with no agreed direction.
  • The team has already pre-decided the target moment. Monday's value is in the convergence; if it's been pre-decided, Monday becomes ratification theater.

What This Skill Produces

A single bundled artifact with six sections:

  1. Long-term goal: one sentence naming success in 1-5 years. Aspirational; cannot be hit in this sprint, but should be visible from the target moment.
  2. Sprint questions: 3-7 questions converting team fears into testable risks. Phrased as "Can we... ?" or "Will... ?" or "How... ?"; NOT phrased as solutions.
  3. Customer or system map: 5-15 step flow from key player(s) at the left to outcome (long-term goal) at the right. Includes major actors, decision points, and current alternatives.
  4. Expert interview notes: synthesized observations from 2-4 cameo experts interviewed Monday afternoon. Surfaced as HMW candidates for the cluster board.
  5. HMW cluster board: 30-100+ How Might We notes from the team, clustered into 4-8 themes; voted with tool-note-and-vote heat-map mechanic to surface top clusters.
  6. Target moment: the single point on the map (or a tight cluster of points) the Decider picks as the prototyping target. Wednesday's storyboard begins from here.

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

Inference Inputs

InputWhat the skill does with it
Sprint brief (from tool-design-sprint-brief)Pulls the locked sprint questions as seed for refinement; pulls the challenge statement as the long-term goal seed; pulls the team roster for role assignments in note-and-vote
Existing researchUsed to draft the customer or system map; researcher walks the team through key findings during the map step
AnalyticsQuantitative grounding for the map's decision-point branch points and abandonment moments
Customer examplesConcrete stories used to validate the map's key player and surface map-step gaps
Expert interview transcripts (run during Monday)Synthesized into HMW candidates by the moderator (typically PM or researcher) during the afternoon

Monday Time Structure

The full Monday 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:30: Welcome + brief recap + introductions (does not produce artifact content)
  • 09:30-10:30: Long-term goal (one sentence) + draft sprint questions (3-7)
  • 10:30-12:30: Customer or system map draft (continuous-flow whiteboard work; team builds together)
  • 12:30-13:30: Lunch + first expert interview slot (cameo)
  • 13:30-15:30: Remaining expert interviews (3 slots; 25 min each); team captures HMWs continuously during interviews
  • 15:30-16:30: HMW cluster board synthesis; team adds final HMWs; Facilitator clusters; team heat-map votes via tool-note-and-vote
  • 16:30-17:00: Decider picks target moment; signs off; team disperses for Tuesday sketches

This skill's 105-minute timebox covers the facilitated synthesis sections (long-term goal + sprint questions + map draft + HMW clustering + target selection). Expert interviews and silent map-extension work happen in parallel and are not counted in the timebox.

Show full SKILL.md (386 more words)Show less

Common Pitfalls

  • Long-term goal too short. "Ship Brainshelf MVP by Q3" is a roadmap goal, not a long-term goal. The long-term goal is 1-5 years out and aspirational ("Become the default way 25+/year readers remember and recall books").
  • Sprint questions phrased as solutions. "Build the camera-capture flow" is a solution; "Can we get sub-3-second capture without abandonment?" is a sprint question. The team must convert fears into questions, not predetermined answers.
  • Map too detailed. 5-15 steps, not 50. The map is for Decider orientation, not engineering documentation. If the map balloons, the Facilitator forces compression.
  • Skipping HMW because "we already know the opportunities." HMW's value is divergent surfacing followed by convergent voting. Pre-deciding the opportunities skips both halves.
  • Decider absent at target-moment selection. The whole point of Monday is the Decider's target choice. If the Decider must leave early, target selection must happen before they leave, even if HMW clustering compresses.
  • Expert interviews skipped or run by the wrong person. Experts bring outside context the team can't generate internally. Skipping them produces an inward-looking Monday. Running them as group calls (instead of small cameo conversations) wastes expert time and produces less useful HMW input.

Cross-Skill Usage

Prerequisites: tool-design-sprint-brief. Map-and-Target consumes the locked sprint brief and refines the sprint questions during the morning. Without a brief, this skill has no convergence target.

This skill invokes tool-note-and-vote twice during the day: once for HMW cluster heat-map voting (anonymous dot-voting to surface top 4-8 clusters) and optionally once for target-moment supervote when the Decider wants team input before deciding. The Decider's call is final regardless of team vote distribution.

Next invocation in the sprint: tool-design-sprint-sketch Tuesday morning.

Canonical Sources

Decider Checkpoint

This skill ends with a Decider Checkpoint in references/TEMPLATE.md. The Decider's call at the end of Monday is target-moment selection: a single point (or tight cluster of points) on the customer or system map that becomes Tuesday's design target. Without that selection, Tuesday's sketches diverge with no shared direction. The Decider also confirms the long-term goal, the sprint questions, and the top HMW clusters; these become Wednesday's heat-map orientation.

© product-on-purpose, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/tool-design-sprint-map-and-target of product-on-purpose/pm-skills.

  • SKILL.md
  • HISTORY.md
  • references/EXAMPLE.md
  • references/TEMPLATE.md

Open the folder on GitHubat commit 1cef1a9

Compare with similar skills

Tool Design Sprint Map And Target next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tool Design Sprint Map And Target compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tool Design Sprint Map And Target this skillproduct-on-purpose/pm-skills716—~2.2kAutomated safety check: PassApache-2.0
Canghe Comicfreestylefly/canghe-skills4618 repos~3.2kAutomated safety check: PassNone
Tutti UI Systemtutti-os/tutti3.8k—~2.7kAutomated safety check: PassApache-2.0
3D Animation Short Generatortl2012tl/comfyUI-llama-TE2414 repos~3.7kAutomated safety check: PassNone
Text to PNG Card Casterlijigang/ljg-skills7.5k—~1.9kAutomated safety check: PassMIT
H3 Cinematic Directorjtydhr88/ComfyTV1.1k—~2.7kAutomated safety check: PassMIT

Similar skills

  • Canghe Comic

    freestylefly/canghe-skills

    Knowledge comic creator supporting multiple art styles and tones.

    461 GitHub starsUsed in 8 repos~3.2k tokens
    Media & CreativeAuto-check passed

  • Tutti UI System

    tutti-os/tutti

    A skill your agent uses when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business…

    3.8k GitHub stars~2.7k tokensUpdated 3 days ago
    Media & CreativeAuto-check passed

  • 3D Animation Short Generator

    tl2012tl/comfyUI-llama-TE

    Create complete stylized 3D animated shorts from a story idea through an ordered production workflow covering project brief, story outline, character and environment cards, standardized shot…

    241 GitHub starsUsed in 4 repos~3.7k tokens
    Media & CreativeAuto-check passed

  • Text to PNG Card Caster

    lijigang/ljg-skills

    Turns text, URLs or local files into tall PNG cards through HTML typography, with four modes: long reading card, full-text layout, comic and whiteboard.

    7.5k GitHub stars~1.9k tokensUpdated 2 days ago
    Media & CreativeAuto-check passed

  • H3 Cinematic Director

    jtydhr88/ComfyTV

    Convert approved scripts, shot briefs, storyboards, keyframes, character sheets, scene assets, prop sheets, and sound briefs into director-level storyboards and production-ready MiniMax H3 prompts.

    1.1k GitHub stars~2.7k tokensUpdated 4 days ago
    Media & CreativeAuto-check passed

  • Scroll Promo Site Builder

    kangarooking/kangarooking-skills

    Create a scroll-controlled cinematic product website with rich motion (动效网站) from product materials, reference pages or videos, and brand assets.

    662 GitHub stars~2.6k tokensUpdated 1 mo ago
    Media & CreativeAuto-check passed

More from product-on-purpose/pm-skills

All 68 skills in this repo

  • Define Hypothesis

    product-on-purpose/pm-skills

    Defines a testable hypothesis with clear success metrics and a validation approach.

    716 GitHub stars~966 tokensUpdated 3 days ago
    Auto-check passed

  • Define Jtbd Canvas

    product-on-purpose/pm-skills

    Creates a Jobs to be Done canvas capturing the functional, emotional, and social dimensions of a customer job.

    716 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Define Opportunity Tree

    product-on-purpose/pm-skills

    Creates an opportunity solution tree connecting a desired outcome to customer opportunities and candidate solutions, preventing solution-first jumps in continuous discovery.

    716 GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Define Problem Statement

    product-on-purpose/pm-skills

    Creates a clear problem framing document with user impact, business context, and success criteria.

    716 GitHub stars~932 tokensUpdated 3 days ago
    Auto-check passed

  • Deliver Acceptance Criteria

    product-on-purpose/pm-skills

    Generates structured Given/When/Then acceptance criteria for a user story or feature slice, covering the happy path, key failure scenarios, and non-functional expectations in testable form.

    716 GitHub stars~1k tokensUpdated 3 days ago
    Auto-check passed

  • Deliver Launch Checklist

    product-on-purpose/pm-skills

    Creates a cross-functional pre-launch checklist covering engineering, design, marketing, support, legal, and operations readiness, with owners, dates, and go/no-go criteria so nothing is missed…

    716 GitHub stars~970 tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Tool Design Sprint Map And Target

What does Tool Design Sprint Map And Target do?

Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert…. Tool Design Sprint Map And Target is an agent skill from product-on-purpose/pm-skills. Day 1 (Monday) move of a Design Sprint that produces the bundled Monday artifact containing long-term goal, sprint questions (3-7 testable risks), customer or system map (5-15 step flow), expert interview notes, HMW (How Might We) cluster board, and the Decider's chosen target moment.

When should I use Tool Design Sprint Map And Target?

Tool Design Sprint Map And Target fits situations like: tasks that involve Comics and storyboards.

How do I install Tool Design Sprint Map And Target in Claude Code?

Run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-map-and-target -a claude-code`. Or copy the skill folder (skills/tool-design-sprint-map-and-target in product-on-purpose/pm-skills) into .claude/skills/tool-design-sprint-map-and-target in your project. Claude Code loads it when a task matches its description.

How do I install Tool Design Sprint Map And Target in Codex?

Run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-map-and-target -a codex`. Or copy the skill folder (skills/tool-design-sprint-map-and-target in product-on-purpose/pm-skills) into .agents/skills/tool-design-sprint-map-and-target in your project. Codex loads it when a task matches its description.

Can I use Tool Design Sprint Map And Target in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add product-on-purpose/pm-skills --skill tool-design-sprint-map-and-target -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tool-design-sprint-map-and-target, .gemini/skills/tool-design-sprint-map-and-target, .github/skills/tool-design-sprint-map-and-target and .opencode/skills/tool-design-sprint-map-and-target in your project.

What does Tool Design Sprint Map And Target need to run?

SKILL.md names no scripts, command-line tools or credentials: Tool Design Sprint Map And Target is instructions for the agent only.

Does Tool Design Sprint Map And Target access the network?

SKILL.md names 3 domains. As links in the text: gv.com, character.vc and designsprintkit.withgoogle.com. This is read from the text; nothing was executed.

Is Tool Design Sprint Map And Target safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Tool Design Sprint Map And Target use?

Tool Design Sprint Map And Target is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tool Design Sprint Map And Target use?

About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.8k tokens, read only when the agent opens those files.

What are the alternatives to Tool Design Sprint Map And Target?

Skills that share tags, products or a category with Tool Design Sprint Map And Target: Canghe Comic (freestylefly/canghe-skills, 461 stars), Tutti UI System (tutti-os/tutti, 3.8k stars), 3D Animation Short Generator (tl2012tl/comfyUI-llama-TE, 241 stars) and Text to PNG Card Caster (lijigang/ljg-skills, 7.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tool Design Sprint Map And Target?

product-on-purpose (a GitHub organization) maintains it in product-on-purpose/pm-skills, which has 716 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on October 8, 2026.

Source: product-on-purpose/pm-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.