Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mattgierhart/PRD-driven-context-engineering --skill prd-v04-user-journey-mappinggit clone --depth 1 https://github.com/mattgierhart/PRD-driven-context-engineeringWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v04-user-journey-mapping)<a href="https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v04-user-journey-mapping"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v04-user-journey-mapping/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mattgierhart/prd-driven-context-engineering/prd-v04-user-journey-mapping"><img src="https://agentmods.dev/badge/skills/mattgierhart/prd-driven-context-engineering/prd-v04-user-journey-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00145 | $0.02417 |
| Opus 5 | $0.00072 | $0.01208 |
| Sonnet 5 | $0.00029 | $0.00483 |
| Haiku 4.5 | $0.00015 | $0.00242 |
Grade A, and why
prd-v04-user-journey-mapping scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Journey Mapping
Position in workflow: v0.4 Persona Definition → v0.4 User Journey Mapping → v0.4 Screen Flow Definition
User journeys transform features into paths. A journey answers: "How does [persona] go from [trigger] to [value moment] using [features]?"
Consumes
This skill requires prior work from v0.3-v0.4:
- PER-* persona entries (from v0.4 Persona Definition) — Behavioral profiles that journeys are built around; each journey belongs to a specific persona
- FEA-* feature entries (from v0.3 Features Value Planning) — Feature list that becomes journey steps; validates that journeys use only MVP-scoped features
- KPI-* outcome definitions (from v0.3 Outcome Definition) — Success metrics that journeys drive; Core journeys must tie to Tier 1/2 KPIs
- MVP-SCOPE artifact (from v0.3 Features Value Planning) — Explicit feature boundary; journeys must use only features in MVP-SCOPE, no backlog features
- BR-* business rules (from v0.3 Commercial Model) — Constraints that affect journey design (pricing tiers affect onboarding paths, moat rules affect targeting journeys, etc.)
This skill assumes v0.4 Persona Definition is complete.
Produces
This skill creates/updates:
- UJ-* entries (user journeys, confidence 2-3/5) — Paths from trigger through steps to value moment, tied to PER-/FEA-/KPI- with pain point identification
- Journey sequencing artifact — Dependency map showing which journeys gate which (Onboarding gates Core; Core gates Power User)
All UJ- entries should include:
confidence: 2-3/5(based on design validation and feature implementation certainty)- Evidence source citations (PER-ID, FEA-ID, KPI-ID references)
- Forward target: "Would move to 4/5 if validated in beta with actual persona users"
Example UJ- entry with confidence:
UJ-001: First Report Generation
Persona: PER-001 (Overwhelmed Ops Manager)
Type: Core
Trigger: User completes onboarding and sees empty dashboard
Goal: Generate first automated report to see time-saving value
Confidence: 2/5 (source: design-validation + feature-status-in-development; KPI-002 links to conversion)
Steps:
1. Click "Create Report" → FEA-003 (one-click reports) [In MVP-SCOPE]
2. Select data source → FEA-001 (auto-sync) [In MVP-SCOPE]
3. Choose report template → FEA-008 (templates) [In MVP-SCOPE]
4. Preview report → FEA-003 [In MVP-SCOPE]
5. Export/share report → FEA-009 (export) [In MVP-SCOPE]
Pain Points:
- Step 2: User may not have connected data source yet (dependency on UJ-002)
- Step 3: Template overload if too many choices (design concern; recommend 3-5 templates max)
Moment of Value: Seeing the completed report with their actual data
KPI Link: KPI-002 (activation rate — user completes first valuable action)
Success Metric: Time from "Create Report" click to export ≤ 5 minutes
Dependencies: BR-015 (data format rules), UJ-002 (data source connection must precede)
Next Target: "Would move to 4/5 if 5+ beta users complete this journey in ≤5 minutes and report value"
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 233 lines · 145 tokens per session scan A d1d0697ac77c
prd-v04-user-journey-mapping is a skill published in the GitHub repository mattgierhart/PRD-driven-context-engineering (182 stars, last pushed 11d ago), licensed MIT. It adds 145 tokens to every session and 2,417 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
loft
Loft the shape before cutting steel — answer a design question that prose cannot settle by building a throwaway artifact: a pure logic module in a clickable shell, or structurally different UI variants behind one route. The captain reacts to the artifact; the answer folds into the decision; the artifact never docks.…
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.
latex-posters
Use when creating or revising LaTeX research posters with beamerposter, tikzposter, or baposter, including poster layout, typography, color, print sizing, figure placement, QR codes, compilation, and print-ready PDF checks.
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a…
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.