definitionstory-map
Generate a structured user story map to visualize workflows, user goals, and release slices.
When & Why to Use This Skill
This Claude skill streamlines product discovery and agile planning by generating comprehensive user story maps. It helps Product Managers and Designers visualize complex user journeys, define core activities, and strategically organize tasks into logical release slices, ensuring cross-functional alignment on project scope and MVP definition.
Use Cases
- MVP Definition: Mapping out the essential user journey to identify the Minimum Viable Product and prioritize features for subsequent release phases.
- Cross-functional Alignment: Visualizing complex workflows to ensure product, design, and engineering teams share a unified understanding of user goals and technical constraints.
- Backlog Structuring: Breaking down high-level user goals into actionable tasks and activities, formatted for easy export into project management tools like Jira, Linear, or Miro.
| name | definition.story_map |
|---|---|
| phase | definition |
| description | Notable constraints or assumptions guiding scope. |
| - name | constraints |
Purpose
Support cross-functional alignment on scope by visualizing how users progress through key activities and what increments deliver value.
Pre-run Checklist
- ✅ Review discovery insights to confirm persona and goal accuracy.
- ✅ Align with engineering on technical constraints or dependencies.
- ✅ Gather any existing journey maps or service blueprints for reference.
Invocation Guidance
codex run --skill definition.story_map \
--vars "persona={{persona}}" \
"primary_goal={{primary_goal}}" \
"stages={{stages}}" \
"constraints={{constraints}}"
Recommended Input Attachments
- Screens or prototypes covering the journey.
- Notes from field studies or shadowing sessions.
Claude Workflow Outline
- Outline the persona, goal, and context.
- Create a story map table with columns for stages, activities, tasks, and candidate releases.
- Highlight assumptions, dependencies, and instrumentation needs per slice.
- Provide a narrative summary and collaboration checkpoints.
- Suggest export steps for tools like FigJam, Miro, or backlog systems.
Output Template
## Story Map Overview
Persona: {{persona}}
Goal: {{primary_goal}}
## Story Map
| Stage | User Activity | Tasks | Release Slice | Notes |
| --- | --- | --- | --- | --- |
## Alignment Notes
- Assumptions:
- Dependencies:
- Instrumentation:
Follow-up Actions
- Review the map with design, engineering, and product marketing for feedback.
- Break down release slices into backlog items with acceptance criteria.
- Track updates in the squad planning workspace.