storymap-skill

User story mapping (Jeff Patton style). Lean SKILL.md + on-demand references. Turns a goal, brief, or messy backlog into a sliced, prioritized delivery plan with per-persona stories that act as the blueprint for the team's test playbook. Auto-activates in Superpowers/gstack/GSD Plan stages, including Superpowers plan generation, gstack /office-hours, /autoplan, any /plan-*-review such as /plan-dev-design-review, and cases where a design doc has been generated and the plan is being adjusted. Consumes framework-owned design.md as the authoritative brief and augments it with story-map sections without clobbering the framework's content. Generates UX/UI designer + architect role hints and chains to flow-advisor skills when available. Step 0.5 reconciles prior progress against tracker + code state (with opt-in tracker-status-update.sh write-back). Runs as one re-entrant loop that diffs against existing artifacts/tracker/code and updates in place; re-runs detect capacity/dependency/OKR/scope limit breaches. Always produces or updates design.md + storymap.md + storymap.csv (the flat items+status manifest); generates storymap.mmd + backlog.md + backlog.csv only when no issue tracker is defined. When a tracker is defined it reuses the tracker's existing taxonomy (epics/components/fix-versions/labels/fields), persists the mapping, and the opt-in write-back sets each item's burn-down fields (story-points/sprint/status) so the tracker's native burn-down works. Before the interview, it simulates each persona to surface cross-persona handoffs, interactions, and conflicts. Mines existing context (README, code, tests, ADRs, Jira/ADO/GitHub/Linear via MCP, .gsd/, prior design.md) before asking the user.