to-story-maplisted

# To Story Map Facilitate a Jeff Patton story mapping session in which the user watches the map grow on a **live whiteboard**, put the finished map in front of two adversaries, then cut one issue per release slice. The map is a strategic artifact: it shows *how* users reach their goal, which is what tells you what to build. It changes as the team learns. The three slice issues are the map's record. Anything the session decides that a later reader needs — the map itself, what the review changed, what stayed an assumption — rides in them, because they are what `/to-user-stories` and `/prototype` read and what a resumed session reconstructs from. ## Repo wiring Two pointers, both written by `/setup-playbook-skills`. A missing one: tell the user to run that skill and hold. - **`docs/agents/issue-tracker.md`** — reached from the `### Issue tracker` sub-block of `## Agent skills` in `AGENTS.md` or `CLAUDE.md`. Its operation table defines every tracker verb this skill names in **bold** — **publish**, **list**, **link A blocked by B** and the rest — and is the authority on both the command to run and the fallback when a tracker cannot express an edge. Read it at the write gate. - **`docs/agents/domain.md`** — the rules for reading this repo's `CONTEXT.md` glossary and its ADRs. Followed at Preflight. ## Input **Works best with:** the system or workflow to map. **Also useful:** primary users/personas, workflow steps already known, what the map must decide (MVP scope, release p