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
2f98f9130a79330683c507c326b372ada991b93e
BMAD-METHOD/docs/explanation/architecture/four-phases.md
forcetrainer 12d3492e0c Add link auditor, reorganize documentation, and README update (#1277) 
* feat: add link auditor tools and fix broken docs links

- Add audit-doc-links.js to scan docs for broken links with auto-resolution
- Add fix-doc-links.js to apply suggested fixes (dry-run by default)
- Remove stale "Back to Core Concepts" breadcrumb links
- Update BMad acronym to "Breakthrough Method of Agile AI Driven Development"
- Update README links to docs.bmad-method.org
- Simplify upgrade callout in getting-started tutorial

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

* docs: reorganize docs structure and archive v4 tutorial

- Remove unused section index files (tutorials, how-to, explanation, reference)
- Move getting-started-bmadv4.md to _archive
- Update quick-start-bmgd.md to remove archived file reference
- Update upgrade-to-v6.md
- Update astro.config.mjs for new structure

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

* fix: ignore underscore directories in link checker

Update check-doc-links.js to skip _archive, _planning, and other
underscore-prefixed directories when validating links.

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

* docs: add v4 users section to README

Add links to v4 documentation archive and upgrade guide for users
migrating from previous versions.

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

* feat: convert docs to site-relative links and add validation tools

- Convert all relative links (./  ../) to site-relative paths (/path/)
- Strip .md extensions and use trailing slashes for Astro/Starlight
- Add fix-doc-links.js to convert relative links to site-relative
- Add validate-doc-links.js to check links point to existing files
- Remove old audit-doc-links.js and check-doc-links.js
- Update build-docs.js to use new validation script
- Add npm scripts: docs:fix-links, docs:validate-links
- Update style guide with validation steps

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

* docs: standardize acronym to BMad across documentation

Replace incorrect "BMAD" with correct "BMad" in text and frontmatter
while preserving "BMAD-METHOD" in GitHub URLs.

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

* docs: fix BMad acronym and remove draft README

- Correct acronym to "Breakthrough Method of Agile AI Driven Development"
- Remove unused README-draft.md

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

* docs: standardize BMad acronym in README

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

* docs: standardize FAQ format across all FAQ pages

- Add TOC with jump links under "## Questions"
- Use ### headers for questions (no Q: prefix)
- Direct answers without **A:** prefix
- Remove horizontal rules and "Related Documentation" sections
- End each FAQ with issue/Discord CTA
- Update style guide with new FAQ guidelines
- Delete redundant faq/index.md (sidebar handles navigation)

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

* fix: use repo-relative links with .md for GitHub compatibility

Convert all documentation links to repo-relative format (/docs/path/file.md)
so they work when browsing on GitHub. The rehype plugin strips /docs/ prefix
and converts .md to trailing slash at build time for Astro/Starlight.

- Update rehype-markdown-links.js to strip /docs/ prefix from absolute paths
- Update fix-doc-links.js to generate /docs/ prefixed paths with .md extension
- Convert 217 links across 64 files to new format

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

* fix: handle /docs/ prefix in link validator

Update resolveLink to strip /docs/ prefix from repo-relative links
before checking if files exist.

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

* docs: restore FAQ index page

Re-add the FAQ index page that was accidentally deleted, with
updated repo-relative link format.

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

---------

Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Alex Verkhovsky <alexey.verkhovsky@gmail.com>
2026-01-10 02:55:33 +08:00

3.1 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

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.

Related