BMAD for AI Departments¶
Document ID: PRO-BMAD-001
Status: Active
Owner: Maya (COO)
Last Edited: Maya, 2026-02-23
Review Due: 2026-05-23
Purpose¶
BMAD (Business Method of Agile AI Driven Development) adapted for COOWN AI departments. Ensures consistent project execution, quality gates, and anti-inflammation controls.
BMAD Modules for AI Departments¶
| Module | Full Name | Purpose | BMAD Equivalent |
|---|---|---|---|
| BMI | BMAD Maya Infrastructure | Project lifecycle, checkpoint enforcement | Core |
| BMN | BMAD Maya Narrative | Story definition, acceptance criteria | BMM/CIS |
| BMA | BMAD Maya Audit | Verification, quality gates | TEA |
Checkpoint System¶
BACKLOG → READY → IN PROGRESS → REVIEW → DONE
↑___________|← approval required
Checkpoint Rules: 1. No self-approved stories — Maya reviews all completions 2. No stories without acceptance criteria 3. No "done" without QA verification (Tom) 4. File creation requires explicit Maya pre-approval 5. Blockers escalate to Simon within 4 hours
Anti-Inflammation Rules (Mandatory)¶
Before creating ANY file, agent MUST check:
- [ ] Does this content fit in an existing canonical file?
- [ ] Does this duplicate information elsewhere?
- [ ] Can this be a section instead of a standalone file?
- [ ] Does this violate the scope boundary of any canonical file?
If ANY answer is "yes" → STOP. Ask Maya before proceeding.
Roles¶
| Role | Agent | Responsibility |
|---|---|---|
| Product Manager | Maya | Story definition, acceptance criteria, file creation approval |
| Architect | Maya | Structure decisions, canonical locations |
| Implementer | Paul, Devin | Execute stories, never create files without approval |
| QA | Tom | Verify against criteria, block if not met |
| Sponsor | Simon | Approve charter, escalate blockers |
Story Lifecycle¶
1. BACKLOG¶
- Story defined
- Acceptance criteria written
- Estimate assigned
- Maya approval required to move to READY
2. READY¶
- All prerequisites complete
- Agent assigned
- Maya moves to IN PROGRESS
3. IN PROGRESS¶
- Agent executes
- Regular updates to Plane
- Blockers escalated immediately
4. REVIEW¶
- Agent marks complete
- Tom runs QA verification
- Maya reviews against acceptance criteria
5. DONE¶
- All criteria met
- QA passed
- Artifacts delivered
- Maya updates Plane + MEMORY.md
Violation Consequences¶
| Violation | Consequence |
|---|---|
| File created without approval | Story rejected, rework required |
| Duplicate content introduced | Remove duplication, update canonical |
| Skipped QA checkpoint | Return to IN PROGRESS |
| Scope boundary violation | Archive file, consolidate to canonical |
Related Documentation¶
- Project Charter Template
- Story Template
- IMS Alignment Charter — Example implementation