Menu
Build a persona-grounded user journey map for a product flow
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Interactive 8-module learning path for the shipped skills, role-adaptive
Make a product decision with full context from the vault and available sources
Daily planning - morning (fill journal, plan focus) or evening (close-out, prep tomorrow)
Process raw meeting notes into structured meeting note with in-repo tasks
Customize this workspace to your role, company, and tools - quick (3 min) or deep (10 min)
Submit feedback to the template repo as a GitHub issue (bug, feature request, or confusion)
| name | user-journey |
| description | Build a persona-grounded user journey map for a product flow |
| argument-hint | [flow or task the user is trying to complete] |
You help map a user journey for a specific task or flow. The output is a markdown journey artifact that names the persona, walks through stages, and highlights friction, emotion, and opportunities.
The user provides via $ARGUMENTS:
Read research/personas/ to see what personas exist.
If one persona clearly matches: confirm with the user - "I'll ground this journey in [[persona]]. OK?"
If multiple could match or none exists: ask the user which persona to use via AskUserQuestion, offering personas from research/personas/ plus an "Other - I'll describe it" option.
If no personas exist yet: prompt the user to run /personalize --deep or describe the persona in a short paragraph. Build the journey with an inline persona description at the top.
Clarify in ONE AskUserQuestion round (skip any that are already answered):
Produce a table-and-prose journey map with these columns:
| Stage | What the user does | What the user thinks | What the user feels | Friction / opportunity |
|---|
Keep stages at the right level of granularity - for most journeys, 5-8 stages is the sweet spot. Fewer misses detail; more turns into a task list.
For each stage:
Use specific, first-person voice ("I paste my API key and...") over generic ("The user enters credentials...").
A "moment of truth" is a stage where the user's experience makes or breaks their trust in the product. Below the table, call out the 2-3 most critical:
### Moments of truth
1. **[Stage name]**: Why it's critical, what good looks like, what bad looks like.
2. ...
In the last section, list 3-5 concrete things to improve the journey. For each:
These feed into /opportunity-solution-tree or a follow-up epic.
research/journeys/. Create if it doesn't exist.YYYY-MM-DD - [Persona] - [Flow].md. Example: 2026-04-20 - Dana (Backend Dev) - First API Integration.md.tags: Journey, persona: [[persona file]], created: YYYY-MM-DD.## Notes.## Breakdown > Scope section.✅ Journey mapped: [[YYYY-MM-DD - Persona - Flow]]
✅ Linked in today's journal
[if epic] ✅ Linked in [[Epic]]
Persona: [[persona]]
Stages: [N]
🎯 Moments of truth:
1. [Stage name]
2. [Stage name]
💡 Top opportunity: [One-line summary]
Next step: run `/opportunity-solution-tree` to explore solutions for the top opportunity.