Epic to User Stories

Translates high-level ideas into detailed Epic-level Product Requirements Documents (PRDs) that serve as the single source of truth for engineering teams.

Guide product managers through breaking down epics into user stories using the Humanizing Work methodology with 9 splitting patterns.

Generate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, with descriptions, design links, and acceptance criteria.

Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.

Translate a vague request or GitHub issue into a concrete, testable spec using five structured elements (problem, scope, acceptance criteria, edge cases, success criterion) before writing any code. Prevents scope creep, PR churn, and mid-implementation pivots.

Chains /mvp and /backend-spec to analyze an app from video, screenshots, or description, then generate implementation stories from the analysis.

Write and refine user stories using INVEST criteria, the 'As a X, I want Y, so that Z' format, Gherkin acceptance criteria, definition of ready, anti-patterns, and a review checklist.

Breaks a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices, then publishes them to the project issue tracker.

Turns the current conversation context and codebase understanding into a PRD and publishes it to the project issue tracker with a triage label.

Breaks a product requirements document into independently-grabbable GitHub issues using vertical slices, with user approval before creation.