Story Mapping Skill Guidance

Use When

arranging an existing backlog into user activities, a walking skeleton, and release slices; use backlog-prioritization for economic ordering after the map exists.
Use this procedure when the required source artefacts are available and Story map and release-slice record is the next lifecycle deliverable.

Use backlog-prioritization when that neighbouring route owns the decision or deliverable.
Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.

Artefact	Source or provider	Required?	Behaviour when missing
Approved stories, personas, user journeys, dependencies, and release constraints	Product backlog and product owner	Yes	Stop the affected step, name the missing source, and return only a qualified gap record.