tool-design-sprint-map-and-target

<!-- 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`](../../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 t...