story

# Story Breakdown Transform requirements into INVEST-compliant user stories with testable acceptance criteria. **Announce:** "Using story breakdown to create implementable stories." ## The Iron Law ``` NO STORY WITHOUT ACCEPTANCE CRITERIA ``` Every story must have testable acceptance criteria before implementation. **No exceptions:** - Don't start work without criteria - Don't assume "obvious" criteria - Don't defer criteria to "later" - Later never comes ## INVEST Criteria Every story MUST pass: | Criterion | Question | Failure Symptom | |-----------|----------|-----------------| | **I**ndependent | Can this ship without other stories? | "We need to do X first" | | **N**egotiable | Can scope be discussed? | "It has to be exactly this" | | **V**aluable | Does user/business care? | "It's technical debt" | | **E**stimable | Can team size it? | "No idea how long" | | **S**mall | Fits in one iteration? | "It's a 2-week story" | | **T**estable | Can we verify done? | "We'll know when we see it" | **Failing any criterion = story needs work.** ## Epic Template ```markdown # Epic: [Name] ## Problem Statement [What problem does this solve? Who has this problem?] ## Success Metrics - [Measurable outcome 1] - [Measurable outcome 2] ## Scope ### In Scope - [Feature/capability] ### Out of Scope - [Explicitly excluded] ## Stories 1. [Story 1 title] 2. [Story 2 title] ## Dependencies - [External dependencies] ## Risks - [Risk]: [Mitigation] ``` ## Story Template ```mark...