Tool Design Sprint Map and Target
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.
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-map-and-targetgit 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-map-and-target ~/.claude/skills/tool-design-sprint-map-and-targetPersonal 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 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: [`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 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.
Details
- Skill name
tool-design-sprint-map-and-target- Repository
- product-on-purpose/pm-skills
- Path
skills/tool-design-sprint-map-and-target/SKILL.md- License
- Apache-2.0
- Repo updated
- 17 November 2026
FAQ
What does the Tool Design Sprint Map and Target skill 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 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.
How do I install the Tool Design Sprint Map and Target 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 Map and Target 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.
Tool Design Sprint Readiness
819product-on-purpose/pm-skills
Pre-sprint diagnostic that determines whether a team should run a Design Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, customer recruiting plan, and pre-sprint activities. Use when a team is considering starting a Design Sprint and wants a fast yes/no diagnosis before committing five days of team time and customer recruiting cost.
Tool Design Sprint Brief
819product-on-purpose/pm-skills
Pre-sprint brief that locks challenge, sprint questions, team and role assignments, customer recruiting plan, prototype medium, interview format, logistics, and success criteria before Monday of a Design Sprint. Use after the readiness verdict is Go and before Monday begins. Produces a two-page artifact the team and Decider sign off on as the contract for the next five days.
Tool Foundation Sprint Basics
819product-on-purpose/pm-skills
Day 1 morning move of a Foundation Sprint. Forces explicit team choices on target customer, important problem, team advantage, and competitors and alternatives. Produces a single coherent strategic frame that becomes the input to Day 1 afternoon Differentiation. Use after the sprint brief is signed and Day 1 morning is scheduled. Bundled artifact, not four separate decisions.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.