User Story Breakdown Engine

Prompt

Break down the following feature or epic into well-formed user stories with acceptance criteria.

Feature/Epic: [DESCRIBE THE FEATURE OR PASTE THE EPIC]
Product context: [BRIEF DESCRIPTION OF THE PRODUCT]
User personas involved: [LIST RELEVANT USER TYPES]
Definition of done for this team: [YOUR TEAM'S CRITERIA]
Estimation method: [STORY POINTS / T-SHIRT SIZES / HOURS]

For each user story:

1. **User Story** — "As a [USER TYPE], I want [ACTION] so that [BENEFIT]."

2. **Acceptance Criteria** — Given/When/Then format. Be exhaustive. Cover:
   - Happy path
   - Error states
   - Edge cases
   - Permissions/role variations

3. **Story Points Estimate** — With reasoning.

4. **Dependencies** — Other stories or systems this story depends on.

5. **Notes for Engineering** — Technical considerations the developer should know.

Also provide:
- **Story Map** — Visual hierarchy showing epics → stories → tasks
- **Sprint Recommendation** — Which stories should be grouped into the same sprint and why
- **Stories That Need More Discovery** — Flag any stories with too many unknowns to estimate confidently
- **Splitting Guidance** — If any story is over [THRESHOLD] points, suggest how to split it