project-story-mapping

To create a user story map for Agile discovery, orchestrate a mapping session to visualize user journeys, identify backbone activities, and slice releases. This Skill coordinates the workflow and generates a structured story-map.md file for stakeholder alignment.

A walking skeleton in MVP release planning is a minimal slice of the user journey that demonstrates end-to-end functionality. This Skill helps delineate it within your story map to inform structured release slicing and project scope.

To slice user stories into MVP releases, map the user journey and identify backbone activities before delineating release slices. This Skill orchestrates that workflow and outputs a structured story-map.md to align stakeholder understanding.

Yes, you need existing project docs to start user story mapping. This Skill reads project context from your documentation to generate a structured story-map.md with frontmatter, ensuring the mapped user journeys align with current stakeholder understanding.

You should use user story mapping instead of a flat backlog during Agile discovery scenarios where visualizing user journeys is critical. It helps identify backbone activities and walking skeletons to scope MVPs, whereas flat backlogs lack spatial journey context.

The story-map.md output integrates into the SDDF pipeline through generated frontmatter. This Skill produces frontmatter-ready outputs alongside the structured story map, allowing seamless delegation to specialized agents for downstream planning.