What problem does it solve?
It turns an approved PRD or structured flow notes into a shareable, flow-level user journey preview so teams can spot missing pages, unreachable states, and unclear transitions before implementation.
Core Features & Use Cases
- Generates modal-per-page journey HTML: produces a single self-contained file where each page is a clickable box that opens a per-page modal.
- Builds from multiple inputs: parses user pages and transitions from a PRD, a YAML journey file, or a conversational 5-question flow capture.
- Writes diffable source-of-truth YAML: stores the canonical journey graph as
<projects/<name>/journeys/<feature-slug>.yaml and regenerates HTML from it via --update.
- Validates the journey graph: checks reachability, references consistency, and enforces caps (max 12 pages, max 30 transitions) to keep previews readable.
Quick Start
Run the journey skill for your feature by providing a feature slug, then review the generated HTML preview to confirm the flow matches your PRD.