Help us improve
Share bugs, ideas, or general feedback.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-skills:tool-design-sprint-map-and-targetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
Plans and facilitates design sprints from challenge framing through prototype testing, with 5-day structure, variations, checklists, and best practices.
Produces a two-page design sprint brief that locks challenge, sprint questions, team roles, customer recruiting, prototype medium, interview format, logistics, and success criteria before Monday. Use after readiness verdict is Go.
Plan and execute a focused 1-week discovery sprint with clear learning objectives.
Share bugs, ideas, or general feedback.
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.
tool-design-sprint-brief).tool-design-sprint-brief; without sprint questions, this skill has nothing to converge toward.A single bundled artifact with six sections:
tool-note-and-vote heat-map mechanic to surface top clusters.See references/TEMPLATE.md for the canonical structure and references/EXAMPLE.md for the Brainshelf book-catalog Monday artifact.
| Input | What 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 research | Used to draft the customer or system map; researcher walks the team through key findings during the map step |
| Analytics | Quantitative grounding for the map's decision-point branch points and abandonment moments |
| Customer examples | Concrete 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 |
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:
tool-note-and-voteThis 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.
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.
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.