What problem does it solve? Product teams often write user flows that miss error paths, permissions, backend mappings, or accessibility requirements, forcing developers to guess during implementation. This Skill provides a complete template that ensures every user flow connects business goals, UX screens, system states, and acceptance criteria. ## Core Features & Use Cases - Structured Flow Documentation: Captures flow metadata, user context, screen-by-screen tables, main paths, alternative paths, and error recovery paths. - Cross-Functional Coverage: Includes sections for permissions matrices, UI-to-backend data mapping, notifications, analytics metrics, accessibility, and responsive behavior. - Acceptance Gates: Defines a checklist a flow must pass before handoff, plus a standardized output format for the Technical Product Owner Agent. - Use Case: A product owner documenting a "submit startup profile for review" flow uses the template to define each screen, validation rule, error recovery, and developer task so the AI Developer Agent can implement it without ambiguity. ## Quick Start Ask the agent to create a user flow for a specific feature using the tpo-user-flow-template, providing the flow name, user role, and goal.
