Workflow Map V6

BMad Method

Context engineering and planning for AI-powered software development

1
Optional

Analysis

Explore the problem space and validate ideas before committing to planning.
brainstorm Optional

Brainstorm project ideas with guided facilitation

M
Mary
Business Analyst
brainstorming-report.md
research Optional

Validate market, technical, or domain assumptions

M
Mary
Business Analyst
Research findings
create-product-brief

Capture strategic vision and product scope

M
Mary
Business Analyst
product-brief.md
2

Planning

Define what to build, requirements, and user experience.
create-prd

Define functional and non-functional requirements

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

Design user experience when UX matters

S
Sally
UX Designer
ux-spec.md
3

Solutioning

Decide how to build it and break work into stories.
create-architecture

Make technical decisions explicit with ADRs

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

Break requirements into implementable work

J
John
Product Manager
Epic files with stories
check-implementation-readiness

Gate check before implementation begins

J
John
Product Manager
PASS/CONCERNS/FAIL
4

Implementation

Build it, one story at a time.
sprint-planning

Initialize tracking (once per project)

B
Bob
Scrum Master
sprint-status.yaml
create-story

Prepare next story for implementation

B
Bob
Scrum Master
story-[slug].md
dev-story

Implement the story with code and tests

A
Amelia
Developer
Working code + tests
code-review

Validate implementation quality

A
Amelia
Developer
Approved / Changes
correct-course Ad-Hoc

Handle significant mid-sprint changes

J
John
Product Manager
Updated plan
retrospective Per Epic

Review lessons learned after epic completion

B
Bob
Scrum Master
Lessons learned
⚡

Quick Flow

Parallel track for small, well-understood changes — skip phases 1-3

B
Barry
Quick Flow Dev
quick-spec
Define an ad-hoc change
→ tech-spec.md
B
Barry
Quick Flow Dev
quick-dev
Implement from spec or direct instructions
→ Working code + tests
📚

Context Management

Each document becomes context for the next phase. The PRD tells the architect what constraints matter. The architecture tells the dev agent which patterns to follow. Story files give focused, complete context for implementation. Without this structure, agents make inconsistent decisions.

Brownfield Projects: Use document-project to create project-context.md before Phase 4. Run it when structure, architecture, or rules change.
Mary Paige (Business Analyst / Technical Writer)

Additional context loaded per workflow:

create-story → epics, PRD, architecture, UX
dev-story → story file
code-review → architecture, story file
quick-spec → planning docs (if exist)
quick-dev → tech-spec
Phase 1: Analysis
Phase 2: Planning
Phase 3: Solutioning
Phase 4: Implementation
Quick Flow (Parallel)
M
Mary
J
John
S
Sally
W
Winston
B
Bob
A
Amelia
B
Barry
P
Paige