Workflow Map V6

BMad Method

Context engineering and planning for AI-powered software development

Artifact Flow → (arrows show which documents feed into the next workflow)
product-brief.md → PRD.md → architecture.md → Stories story file → dev → code-review tech-spec.md → quick-dev
1
Optional
Analysis
Explore the problem space and validate ideas.
brainstorm Opt

Brainstorm project ideas

M
Mary
brainstorming-report.md
research Opt

Validate assumptions

M
Mary
Research findings
create-product-brief

Capture strategic vision

M
Mary
product-brief.md →
product-brief.md
→
2
Planning
Define requirements and user experience.
create-prd

Define requirements (FRs/NFRs)

J
John
PRD.md →
Has UI?
create-ux-design If Yes

Design user experience

S
Sally
ux-spec.md →
PRD + UX
→
3
Solutioning
Design architecture and break into stories.
create-architecture

Make technical decisions explicit

W
Winston
architecture.md →
create-epics-and-stories

Break into implementable work

J
John
Epic files →
check-implementation-readiness

Gate check before implementation

J
John
PASS/CONCERNS/FAIL
arch + epics
→
4
Implementation
Build it, one story at a time.
sprint-planning

Initialize tracking

B
Bob
sprint-status.yaml →
create-story

Prepare story for implementation

B
Bob
story-[slug].md →
dev-story

Implement the story

A
Amelia
code →
code-review

Validate implementation

A
Amelia
Approved
correct-course Ad-Hoc

Handle mid-sprint changes

J
John
Updated plan
retrospective Per Epic

Review lessons learned

B
Bob
Lessons
⚡

Quick Flow (Parallel Track)

For small, well-understood changes — skip phases 1-3

B
Barry
quick-spec
Define an ad-hoc change
tech-spec.md
→
B
Barry
quick-dev
Implement from spec
Working code + tests
📚

Context Management

Each document becomes context for the next phase. PRD → Architecture, Architecture → Dev, Story → Implementation. Without this structure, agents make inconsistent decisions.

Brownfield: Use document-project to create project-context.md before Phase 4. (Mary / Paige)

Context loaded per workflow:

create-story epics, PRD, arch, UX
dev-story story file
code-review arch, story
quick-dev tech-spec
Phase 1: Analysis
Phase 2: Planning
Phase 3: Solutioning
Phase 4: Implementation
→ = Artifact flows to next phase
M
Mary
J
John
S
Sally
W
Winston
B
Bob
A
Amelia
B
Barry