ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
91f6c41be1509025f0c520adab856788ae7a4d0a
BMAD-METHOD/docs/_basement/explanation/four-phases.md
Alex Verkhovsky 91f6c41be1 docs: radical reduction of documentation scope for v6 beta (#1406) 
* docs: radical reduction of documentation scope for v6 beta

Archive and basement unreviewed content to ship a focused, minimal doc set.

Changes:
- Archive stale how-to workflow guides (will rewrite for v6)
- Archive outdated explanation and reference content
- Move unreviewed content to basement for later review
- Reorganize TEA docs into dedicated /tea/ section
- Add workflow-map visual reference page
- Simplify getting-started tutorial and sidebar navigation
- Add explanation pages: brainstorming, adversarial-review, party-mode,
  quick-flow, advanced-elicitation
- Fix base URL handling for subdirectory deployments (GitHub Pages forks)

The goal is a minimal, accurate doc set for beta rather than
comprehensive but potentially misleading content.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* refactor: restructure BMM and agents documentation by consolidating and flattening index files.

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-25 14:00:26 -06:00

2.8 KiB
Raw Blame History

title, description
title description
The Four Phases of BMad Method Understanding the four phases of the BMad Method

BMad Method uses a four-phase approach that adapts to project complexity while ensuring consistent quality.

Phase Overview

Phase Name Purpose Required?
Phase 1 Analysis Exploration and discovery Optional
Phase 2 Planning Requirements definition Required
Phase 3 Solutioning Technical design Track-dependent
Phase 4 Implementation Building the software Required

Phase 1: Analysis (Optional)

Exploration and discovery workflows that help validate ideas and understand markets before planning.

Workflows:

  • brainstorm-project - Solution exploration
  • research - Market/technical/competitive research
  • product-brief - Strategic vision capture

When to use:

  • Starting new projects
  • Exploring opportunities
  • Validating market fit

When to skip:

  • Clear requirements
  • Well-defined features
  • Continuing existing work

Phase 2: Planning (Required)

Requirements definition using the scale-adaptive system to match planning depth to project complexity.

Workflows:

  • prd - Product Requirements Document (BMad Method/Enterprise)
  • tech-spec - Technical specification (Quick Flow)
  • create-ux-design - Optional UX specification

Key principle: Define what to build and why. Leave how to Phase 3.

Phase 3: Solutioning (Track-Dependent)

Technical architecture and design decisions that prevent agent conflicts during implementation.

Workflows:

  • architecture - System design with ADRs
  • create-epics-and-stories - Work breakdown (after architecture)
  • implementation-readiness - Gate check

Required for:

  • BMad Method (complex projects)
  • Enterprise Method

Skip for:

  • Quick Flow (simple changes)

Key principle: Make technical decisions explicit so all agents implement consistently.

Phase 4: Implementation (Required)

Iterative sprint-based development with story-centric workflow.

Workflows:

  • sprint-planning - Initialize tracking
  • create-story - Prepare stories
  • dev-story - Implement with tests
  • code-review - Quality assurance
  • retrospective - Continuous improvement

:::tip[Key Principle] One story at a time — complete each story's full lifecycle before starting the next. :::

Phase Flow by Track

Quick Flow

Phase 2 (tech-spec) → Phase 4 (implement)

Skip Phases 1 and 3 for simple changes.

BMad Method

Phase 1 (optional) → Phase 2 (PRD) → Phase 3 (architecture) → Phase 4 (implement)

Full methodology for complex projects.

Enterprise

Phase 1 → Phase 2 (PRD) → Phase 3 (architecture + extended) → Phase 4 (implement)

Same as BMad Method with optional extended workflows.