authoring-user-flows

Author user-flows documents mapping entry points, branches, error states, and screens from an approved PRD.

1|1|Updated May 24, 2026
One-click install
npx skills add https://github.com/bm629/agent-skills --skill authoring-user-flows-bm629
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authoring-user-flows
Source: https://github.com/bm629/agent-skills/tree/main/skills/authoring-user-flows
Command: npx skills add https://github.com/bm629/agent-skills --skill authoring-user-flows-bm629

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a user-flows document from scratch often produces happy-path-only diagrams with dead ends, missing error states, and screens that downstream wireframing cannot enumerate. This Skill provides the derivation method and production-grade quality bar for authoring a complete, walkable user-flows document grounded in an approved PRD. ## Core Features & Use Cases - Goal-driven flow derivation: Maps every PRD goal/persona pairing to a flow grounded in established interaction patterns, with no orphans and no reinvented solved flows. - Systematic edge and resilience coverage: Enumerates decision branches, empty/loading/error/success states, undo/confirm guards, resume behavior, and flow-level accessibility so no path dead-ends. - Synced dual notation and amend support: Renders each flow as a Mermaid flowchart plus numbered narrative kept in sync, and amends existing docs as scoped, versioned deltas instead of regenerating. - Use Case: Given an approved PRD for a checkout feature, produce a user-flows document with entry-point taxonomy, happy path, every branch and recovery path, a screens index, and a changelog — ready for the reviewing-user-flows gate and downstream wireframing. ## Quick Start Use authoring-user-flows to map the goals and personas in my approved PRD into a complete user-flows document with diagrams, error paths, and a screens index.

Frequently Asked Questions about authoring-user-flows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a user-flows document from a PRD?

Derive one flow per PRD goal/persona pairing, map the happy path first, then enumerate every decision branch, edge case, and error recovery path. Render each flow as a Mermaid flowchart plus a numbered narrative, and finish with a screens index for wireframing.

What is the difference between a user flow and a user journey map?

A user flow is the interaction and navigation graph: entry points, steps, branches, and states. A user journey covers emotion, channels, and touchpoints over time. This Skill produces flows only and treats journey content as out of scope.

How do I update an existing user-flows document without rewriting it?

Scope the change to the affected flows and trace the ripple through cross-flow hand-offs and the screens index, then edit in place. Bump the document version by change class (MAJOR/MINOR/PATCH) and add a changelog entry rather than regenerating untouched flows.

Does this Skill design screen layouts or wireframes?

No. It defines the navigation graph and names every screen and state a flow traverses, but screen layout, pixels, and per-screen accessibility like contrast and target size belong to the downstream wireframing and design-system work.

What accessibility checks apply at the flow level?

Every path must be keyboard-completable with no traps, focus must move meaningfully on step or route changes per WCAG 2.2 SC 2.4.3, errors must be announced to assistive technology, and no required step may depend solely on mouse or gesture input.