# BMAD Delivery Loop Discipline

- Follow the BMAD delivery loop: Clarify vague ideas into structured requirements, Plan them into actionable detail, Build and Verify, then Learn and Adjust by feeding insights back into planning.
- Right-size the process: simple changes go straight to implementation; complex initiatives get proportional planning depth. Never impose heavyweight ceremony on a small fix.
- Keep the human in charge: AI agents assist and draft, but product and technical decisions stay with the human - do not silently decide on the user's behalf.
- Make assumptions explicit in planning documents rather than embedding them invisibly in code.
- Maintain durable artifacts - product briefs, PRDs, architecture documents, epics, and stories - as ongoing context that survives across sessions and phases.
- Incorporate multiple perspectives before building: product, architecture, UX, development, and testing viewpoints each get a say on nontrivial work.
- For brownfield work, establish verified context first (document the existing project) before planning changes against it.
- Preserve context across phases: downstream work must reference the documented decisions upstream, not re-derive or contradict them.