mattgierhart/PRD-driven-context-engineering / .claude/skills/prd-v04-user-journey-mapping
prd-v04-user-journey-mapping
VerifiedMap user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.3 KB |
| assets/uj.md | markdown | 1.2 KB |
| references/examples.md | markdown | 4.0 KB |
| references/sequencing.md | markdown | 3.2 KB |
references/sequencing.md
View on GitHub# Journey Sequencing Guide
## The Dependency Chain
Journeys have dependencies. Map them to understand build order.
### Basic Pattern
```
UJ-000: Onboarding
│
├──→ UJ-001: Core Journey A (primary value)
│ │
│ └──→ UJ-002: Core Journey B (depends on A)
│
└──→ UJ-010: Recovery (available anytime after onboarding)
│
└──→ UJ-003: Power User (expansion)
```
### Sequencing Rules
1. **Onboarding gates everything**
- No journey should assume onboarding is skipped
- Onboarding sets up data/state for all other journeys
2. **Core journeys drive KPIs**
- Sequence core journeys by which KPI- they affect
- Activation KPI journey comes before retention KPI journey
3. **Recovery journeys are always-available**
- They should work from any state
- Don't sequence them as "after" something
4. **Power User journeys unlock after core completion**
- Don't offer expansion before primary value delivered
### Example Sequence for SaaS Product
```
Phase 1: Getting Started
├── UJ-000: Account Creation (onboarding)
└── UJ-001: First Value Moment (core - activation KPI)
Phase 2: Depth
├── UJ-002: Data Integration (core - depth KPI)
└── UJ-003: Customization (core - engagement KPI)
Phase 3: Expansion
├── UJ-004: Team Invite (power user - expansion KPI)
└── UJ-005: Advanced Features (power user - upsell KPI)
Always Available:
├── UJ-010: Password Reset (recovery)
├── UJ-011: Billing Issue (recovery)
└── UJ-012: Support Contact (recovery)
```
### Visualizing Dependencies
For complex products, draw the dependency graph:
```
┌─────────────────────────────────────┐
│ UJ-000: Onboarding │
└─────────────┬───────────────────────┘
│
┌─────────────┴───────────────┐
▼ ▼
┌─────────────────┐ ┌─────────────────┐
│ UJ-001: First │ │ UJ-002: Connect │
│ Report │ │ Data Source │
└────────┬────────┘ └────────┬────────┘
│ │
└──────────┬─────────────────┘
▼
┌─────────────────┐
│ UJ-003: Share │
│ with Team │
└─────────────────┘
```
### Build Order Implications
Journey dependencies inform EPIC sequencing in v0.7:
| Journey | Depends On | Build Order |
|---------|------------|-------------|
| UJ-000 | None | EPIC-01 |
| UJ-001 | UJ-000 | EPIC-02 |
| UJ-002 | UJ-000 | EPIC-02 (parallel with UJ-001) |
| UJ-003 | UJ-001, UJ-002 | EPIC-03 |
This ensures we build foundations before dependent features.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |