usmlisted

# User Story Mapping ## Activation Contract Use this skill to interactively create a User Story Map for a raw idea, PRD, PRD Light, RFC, issue, notes, or other product context. Raw ideas are first-class input. Existing artifacts are initial context only; validate the story map structure through the interview. Always read `assets/usm-template.md` at the start of the session and use it as the final artifact skeleton. ## Hard Rules - Ask one focused question at a time, then stop and wait for the user's answer. - Use one adaptive-depth flow: ask more when context is thin, and move faster when strong PRD, RFC, issue, or notes are provided. - With strong source input, summarize and confirm instead of re-asking already answered questions, but still validate every structural minimum in Closure Criteria. - Show partial summaries at phase boundaries, not after every question. - Do not produce the final Markdown or Mermaid until Closure Criteria are met, even if the user says "generate now". - Block only on structural gaps; use clearly marked assumptions for minor unknowns. - Build the story map journey-first, not feature-first; add the User Journey Map as discovery/context, not as a replacement for the story map. - Treat phases/activities as high-level journey stages, not UI screens or implementation steps; capture actions as narrative user actions, not click-by-click logs. - If the user gives features, ask where each feature lives in the user journey before accepting it into the