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.
SkillScore82Maintained
Automatic
◆Product Management pack
Last verified 8/19/2026
What it changes
Passed 17 of 21 test cases with the skill, and 12 of 21 without it.
Without skill59%
With skill82%
Checks it passed that the model alone missed
Halt the workshop until the sprint brief is locked
Transition to individual sketch exercises on Tuesday
Execute heat-map dot voting using note-and-vote mechanics
and 3 more in the full report
6 fixed12 passed either way3 still failing1 broke
Pass-rate lift
+23 pp
Tokens
+105%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/19/2026v118 of 22 cases passed with skill · 21 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 6
Prompt
Monday afternoon concludes with the Decider selecting the target moment on the map for a fitness tracking application. What activity immediately follows this on Tuesday morning?
What was checked, without and with the skill
Checked
Without skill
With skill
Transition to individual sketch exercises on Tuesday
Missed
Passed
case-20 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md86 lines3 files
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:
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.
Sprint questions: 3-7 questions converting team fears into testable risks. Phrased as "Can we... ?" or "Will... ?" or "How... ?"; NOT phrased as solutions.
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.
Expert interview notes: synthesized observations from 2-4 cameo experts interviewed Monday afternoon. Surfaced as HMW candidates for the cluster board.
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.
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
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
Day 5 (Friday) sprint-closing move of a Design Sprint that produces the bundled Friday artifact covering per-customer interview observations, best quotes, scorecard grid (sprint questions by customers), observed patterns, hot takes from each team member, and the Decider summary (build, iterate, pivot, or stop, plus highest-confidence learning, most important revision, and next artifact). Use Friday after Thursday's prototype passes trial run and during/after the 5 customer interviews. The sprint