⚡ Workflow Map V6

# BMad Method

Context engineering for AI-powered development

→ arrows show artifact flow between workflows
1
Analysis
Optional
brainstorm opt
M
Mary
brainstorming-report.md
research opt
M
Mary
findings
product-brief or ↓
M
Mary
product-brief.md →
prfaq or ↑
M
Mary
prfaq.md →
→
2
Planning
create-prd
J
John
PRD.md →
Has UI?
create-ux-design if yes
S
Sally
ux-spec.md →
→
3
Solutioning
create-architecture
W
Winston
architecture.md →
create-epics-and-stories
J
John
epics.md →
check-implementation-readiness
J
John
gate check
→
4
Implementation
sprint-planning
A
Amelia
sprint-status.yaml →
create-story
A
Amelia
story-[slug].md →
dev-story
A
Amelia
code →
code-review
A
Amelia
approve
correct-course ad-hoc
J
John
updated plan
retrospective per epic
A
Amelia
lessons
investigate opt
T
Tracy
investigation.md
code-archaeology opt
T
Tracy
archaeology.md
⚡

## Quick Flow (Parallel Track)

For small changes or known bugs. Skip phases 1-3, or investigate first then implement.
T
Tracy
`investigate`
evidence → case file → fix direction
→
A
Amelia
`quick-dev`
intent → tech-spec → working code
📚 Context Flow

Each document becomes context for the next phase.

`create-story` loads epics, PRD, architecture, UX `dev-story` loads story file `code-review` loads architecture, story `investigate` produces case file consumed by quick-dev or dev-story `quick-dev` clarify, plan, implement, review
Analysis
Planning
Solutioning
Implementation
Quick Flow