---
name: bmad-story-discipline
description: "BMAD story discipline: context-rich stories done one at a time. Use when writing or implementing a user story."
---

# BMAD Story Discipline

- Break planned requirements into epics and stories before implementation; a story is the unit of agent work.
- Author each story as a dedicated file carrying all the context the implementing agent will need - acceptance criteria, relevant architecture decisions, and constraints - so implementation does not depend on chat history.
- Implement one story at a time, driven by its story file; verify against its acceptance criteria before moving to the next.
- Use specialized agent roles for specialized work - analyst, product manager, architect, UX designer, developer, tech writer - rather than one undifferentiated assistant doing everything.
- Track sprint status against the epics and stories list; surface risks and course-correct explicitly when scope or reality shifts mid-sprint.
- Run a retrospective after each epic to extract lessons and feed them into the next planning cycle.
- Validate implementation readiness before development starts: PRD, UX, architecture, and epics must be complete and consistent with each other.