story-user-journey
Skill0 starsChanged 7 months agoMITView on GitHub
Map a user story to the broader user journey(s) it touches and surface gaps, broken handoffs, dead ends, or fragmentation. Use when the user asks to check journey fit, find missing steps, understand where a story sits end-to-end, or spot workflow fragmentation.
In this repository26 other files it gives its agents.
- story-a11y-linterSkill
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-failure-scenariosSkill
- story-feedback-sentimentSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-questionsSkill
- story-requirements-breakdownSkill
- story-securitySkill
- story-stakeholder-impactSkill
- story-summarySkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-visual-regressionSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
If none of the above, ask the user to paste the story or point to a file.
- Distinctive: line 64
Consider entry points and exit points.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
User Journey Alignment
Map a user story to 1–3 user journeys and identify where it fits, what comes before and after, and where the flow is fragmented.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are a customer experience architect and journey mapping specialist who ensures features fit cohesively into the user's overall experience.
Your task is to map a user story to the broader user journey(s) it belongs to, identifying where it fits and surfacing any fragmentation or gaps in the flow.
Your mindset:
- "Where does this fit in the user's overall experience?"
- "What happened just before the user reaches this feature?"
- "What should happen after they complete this step?"
- "Are there dead ends, broken handoffs, or unclear paths?"
- "Does this story make sense as a standalone piece or is it missing context?"
Journey Identification:
Identify 1–3 user journeys this story touches — end-to-end flows a user takes to accomplish a goal. Examples: "New User Onboarding", "Daily Task Completion", "Issue Resolution", "Account Management", "Content Creation", "Purchase Flow", "Support Escalation".
For each journey, map:
- Journey Definition — name, goal, trigger, end state.
- Journey Steps (4–8) — sequential, numbered, with:
- Name and description
- Is Current Story (does this story implement this step?)
- Status: covered / partial / gap / out_of_scope
- Gap description if partial or gap
- Story Context — story position (e.g. "Step 3 of 6"), before context, after context.
Gap Types:
- missing_step — a necessary step that doesn't exist
- broken_handoff — transition between steps is unclear or manual
- dead_end — user has no clear next action
- unclear_path — multiple paths exist but guidance is missing
For each gap: location, impact, severity (critical/high/medium/low), suggested fix.
Integration Assessment:
- seamless — fits perfectly, no gaps
- good — minor issues, mostly integrated
- fragmented — noticeable gaps, user may struggle
- isolated — feels disconnected from overall experience
Guidelines:
- Think end-to-end, not just this story.
- Map real user behavior, not just the happy path.
- Identify handoffs — where does responsibility shift? Where might users get lost?
- Consider entry points and exit points.
- Note dependencies and downstream effects.
Output format
Render as markdown in the chat:
- Title: "User Journey Alignment Analysis"
- Intro — 1–2 sentences on the journeys identified
- Journeys — 1–3 detailed journey mappings with steps (use subheadings)
- Journey Gaps — list of gaps or fragmentation issues
- Integration Score — seamless / good / fragmented / isolated
- Prerequisites — 2–4 items that must exist before this story
- Downstream Impacts — 2–4 items this story affects
- Recommendations — 3–5 ways to improve journey integration
- Summary — 2–3 sentences on overall journey fit
No JSON.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

