Results for “user-story-mapping”

Use this when a feature or product needs a clear end-to-end user journey across entry, action, system response, and outcome. Trigger on requests to map the full experience before screens or components are finalized.

Run a customer journey mapping workshop with adaptive questions to map stages, actions, emotions, pain points, and opportunities for a persona and scenario.

Maps user flows and journey maps with decision points, error states, and optimization suggestions

Manage user journey mapper operations. Auto-activating skill for Visual Content. Triggers on: user journey mapper, user journey mapper Part of the Visual Content skill category. Use when working with user journey mapper functionality. Trigger with phrases like "user journey mapper", "user mapper", "user".

Create a holistic experience map showing the full ecosystem of user touchpoints, channels, and relationships across the customer journey.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Generates user stories with clear acceptance criteria from product requirements or feature descriptions. Use when breaking down features for sprint planning, writing tickets, or communicating requirements to engineering.

Use only for developer-facing products; map users, buyers, champions, contributors, and operational stakeholders

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.

Maps the end-to-end customer experience from awareness to advocacy — touchpoints, emotions, friction points, and improvement opportunities per stage. Use when identifying drop-off points, improving onboarding, or understanding the full user lifecycle. Triggers on: customer journey, user journey, journey map, touchpoints, onboarding experience, funnel analysis, churn points, aha moment, drop-off, user lifecycle.

Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"

Create a customer journey map across stages, touchpoints, actions, emotions, and metrics to diagnose broken experiences and align teams on the full customer flow.

Craft compelling narratives using story frameworks. Use when the user says "help me with storytelling" or "I want to create a narrative through storytelling"

Extract coverage-checked, independently testable MoonSpec user stories from a technical or declarative design and write breakdown output under artifacts/story-breakdowns (gitignored). Use when the user asks to run or reproduce `/moonspec.breakdown`, split a broad design into one-story candidates, preserve source coverage, or build a coverage matrix before `/moonspec.specify`.

Create a six-frame storyboard that shows a user's journey from problem to solution, using a classic narrative arc to build empathy and align stakeholders.

Lead customer experience with journey mapping, voice of customer programs, service design, and experience metrics.

Analyzing session replays, extracting persona-based behavioral patterns, and storytelling UX issues. Reads the 'why' from real user operation logs. Works with Field/Echo for persona validation.

Design user flows and navigation structure following proven UX patterns

Analyzes dependencies between stories, code modules, tickets, or specs to compute an optimal implementation order with parallel batches, cycle detection, and critical path analysis.

Create process maps with steps, decisions, and handoffs. TRIGGERS - Use when user needs help with process-map related tasks.

Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes. Use when writing QA test cases, creating test plans, defining acceptance tests, or preparing for feature validation.

Design user flows and screen structure using StyleSeed UX patterns such as progressive disclosure, hub-and-spoke navigation, and information pyramids.

Break requirements into epics and user stories. Use when the user says "create the epics and stories list"