ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity

feat(docs): complete Phase 2 - split files and fix broken links 

Phase 2 of Diataxis migration:
- Split 16 large legacy files into 42+ focused documents
- Created FAQ section with 7 topic-specific files
- Created brownfield how-to guides (3 files)
- Created workflow how-to guides (15+ files)
- Created architecture explanation files (3 files)
- Created TEA/testing explanation files
- Moved remaining legacy module files to proper Diataxis locations

Link fixes:
- Fixed ~50 broken internal links across documentation
- Updated relative paths for new file locations
- Created missing index files for installation, advanced tutorials
- Simplified TOC anchors to fix Docusaurus warnings

Cleanup:
- Removed legacy sidebar entries for deleted folders
- Deleted duplicate and empty placeholder files
- Moved workflow diagram assets to tutorials/images

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
forcetrainer 2026-01-03 14:33:25 -05:00 committed by Alex Verkhovsky
parent 9d7e7e67c6
commit 42cc21e4cb
91 changed files with 4835 additions and 3775 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

77
docs/bmad-core-concepts/installing/index.md
View File

@ -1,77 +0,0 @@
# Installation
Get BMAD up and running in your project.
## Upgrading?
If you're upgrading from v4, see the [Upgrade Guide](../../how-to/installation/upgrade-to-v6.md).
---
## Quick Install
```bash
npx bmad-method install
```
This interactive installer will:
1. Let you choose a location to install to
2. Let you choose which Agentic LLM Tools you would like to use (Such as Claude Code, Cursor, Windsurf, etc...)
3. Let you choose which official modules to install (BMad Method, Creative Intelligence suite, BMad Builder)
4. Let you choose any custom local modules, workflows or agents to install
5. Let you configure each module or quickly accept the default recommended settings for each selected model
## Requirements
- **Node.js** 20+ (for the installer)
- **Git** (recommended for version control)
- An **AI-powered Agent and/or IDE** or access to Claude/ChatGPT/Gemini
## Module Options
During installation, you'll choose which modules to install:
| Module | Description | Best For |
| -------- | -------------------- | ----------------------------------------------------- |
| **BMM** | BMAD Method Core | Software development projects |
| **BMGD** | Game Development | Game projects with specialized workflows |
| **CIS** | Creative Intel Suite | Creativity Unlocking Suite, not software dev specific |
| **BMB** | Builder | Creating custom agents and workflows |
You will also be asked if you would like to install custom content (agents, workflows or modules) you have created with the BMB, or shared from others in the community.
## Post-Installation
After installation, your project will have:
```
your-project/
├── _bmad/ # BMAD configuration and agents
│ ├── bmm/ # Method module (if installed)
│ ├── bmgd/ # Game dev module (if installed)
│ ├── core/ # Always installed, includes party mode, advanced elicitation, and other core generic utils
│ ├── {others}/ # etc...
├── _bmad-output/ # BMAD default output folder - configurable during install
├── .claude/ # IDE-specific setup (varies by IDE)
└── ... your code # maybe nothing else yet if a fresh new folder
```
## Next Steps
1. **Read the [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md)** to build your first feature
2. **Explore [Workflows](../../modules/bmm-bmad-method/index#-workflow-guides)** to understand the methodology
3. **Learn about [Agents](../../explanation/core-concepts/what-are-agents.md)** to understand BMAD's core building blocks
## Troubleshooting
### Common Issues
**"Command not found: npx"**
: Install Node.js 20+ from [nodejs.org](https://nodejs.org)
**"Permission denied"**
: Run with appropriate permissions or check your npm configuration
For more help, join our [Discord](https://discord.gg/bmad).

127
docs/explanation/architecture/four-phases.md Normal file
View File

@ -0,0 +1,127 @@
---
sidebar_label: Four Phases
description: Understanding the four phases of the BMad Method
---
# The Four Phases of 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
- [Why Solutioning Matters](./why-solutioning-matters.md)
- [Preventing Agent Conflicts](./preventing-agent-conflicts.md)
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md)

139
docs/explanation/architecture/preventing-agent-conflicts.md Normal file
View File

@ -0,0 +1,139 @@
---
sidebar_label: Preventing Agent Conflicts
description: How architecture prevents conflicts when multiple agents implement a system
---
# Preventing Agent Conflicts
When multiple AI agents implement different parts of a system, they can make conflicting technical decisions. Architecture documentation prevents this by establishing shared standards.
---
## Common Conflict Types
### API Style Conflicts
Without architecture:
- Agent A uses REST with `/users/{id}`
- Agent B uses GraphQL mutations
- Result: Inconsistent API patterns, confused consumers
With architecture:
- ADR specifies: "Use GraphQL for all client-server communication"
- All agents follow the same pattern
### Database Design Conflicts
Without architecture:
- Agent A uses snake_case column names
- Agent B uses camelCase column names
- Result: Inconsistent schema, confusing queries
With architecture:
- Standards document specifies naming conventions
- All agents follow the same patterns
### State Management Conflicts
Without architecture:
- Agent A uses Redux for global state
- Agent B uses React Context
- Result: Multiple state management approaches, complexity
With architecture:
- ADR specifies state management approach
- All agents implement consistently
---
## How Architecture Prevents Conflicts
### 1. Explicit Decisions via ADRs
Every significant technology choice is documented with:
- Context (why this decision matters)
- Options considered (what alternatives exist)
- Decision (what we chose)
- Rationale (why we chose it)
- Consequences (trade-offs accepted)
### 2. FR/NFR-Specific Guidance
Architecture maps each functional requirement to technical approach:
- FR-001: User Management → GraphQL mutations
- FR-002: Mobile App → Optimized queries
### 3. Standards and Conventions
Explicit documentation of:
- Directory structure
- Naming conventions
- Code organization
- Testing patterns
---
## Architecture as Shared Context
Think of architecture as the shared context that all agents read before implementing:
```
PRD: "What to build"
↓
Architecture: "How to build it"
↓
Agent A reads architecture → implements Epic 1
Agent B reads architecture → implements Epic 2
Agent C reads architecture → implements Epic 3
↓
Result: Consistent implementation
```
---
## Key ADR Topics
Common decisions that prevent conflicts:
| Topic | Example Decision |
|-------|-----------------|
| API Style | GraphQL vs REST vs gRPC |
| Database | PostgreSQL vs MongoDB |
| Auth | JWT vs Sessions |
| State Management | Redux vs Context vs Zustand |
| Styling | CSS Modules vs Tailwind vs Styled Components |
| Testing | Jest + Playwright vs Vitest + Cypress |
---
## Anti-Patterns
### ❌ Implicit Decisions
"We'll figure out the API style as we go"
→ Leads to inconsistency
### ❌ Over-Documentation
Every minor choice documented
→ Analysis paralysis, wasted time
### ❌ Stale Architecture
Document written once, never updated
→ Agents follow outdated patterns
### ✅ Correct Approach
- Document decisions that cross epic boundaries
- Focus on conflict-prone areas
- Update architecture as you learn
- Use `correct-course` for significant changes
---
## Related
- [Why Solutioning Matters](./why-solutioning-matters.md)
- [Four Phases](./four-phases.md)
- [Create Architecture](../../how-to/workflows/create-architecture.md)

92
docs/explanation/architecture/why-solutioning-matters.md Normal file
View File

@ -0,0 +1,92 @@
---
sidebar_label: Why Solutioning Matters
description: Understanding why the solutioning phase is critical for multi-epic projects
---
# Why Solutioning Matters
Phase 3 (Solutioning) translates **what** to build (from Planning) into **how** to build it (technical design). This phase prevents agent conflicts in multi-epic projects by documenting architectural decisions before implementation begins.
---
## The Problem Without Solutioning
```
Agent 1 implements Epic 1 using REST API
Agent 2 implements Epic 2 using GraphQL
Result: Inconsistent API design, integration nightmare
```
When multiple agents implement different parts of a system without shared architectural guidance, they make independent technical decisions that may conflict.
---
## The Solution With Solutioning
```
architecture workflow decides: "Use GraphQL for all APIs"
All agents follow architecture decisions
Result: Consistent implementation, no conflicts
```
By documenting technical decisions explicitly, all agents implement consistently and integration becomes straightforward.
---
## Solutioning vs Planning
| Aspect | Planning (Phase 2) | Solutioning (Phase 3) |
| -------- | ----------------------- | --------------------------------- |
| Question | What and Why? | How? Then What units of work? |
| Output | FRs/NFRs (Requirements) | Architecture + Epics/Stories |
| Agent | PM | Architect → PM |
| Audience | Stakeholders | Developers |
| Document | PRD (FRs/NFRs) | Architecture + Epic Files |
| Level | Business logic | Technical design + Work breakdown |
---
## Key Principle
**Make technical decisions explicit and documented** so all agents implement consistently.
This prevents:
- API style conflicts (REST vs GraphQL)
- Database design inconsistencies
- State management disagreements
- Naming convention mismatches
- Security approach variations
---
## When Solutioning is Required
| Track | Solutioning Required? |
|-------|----------------------|
| Quick Flow | No - skip entirely |
| BMad Method Simple | Optional |
| BMad Method Complex | Yes |
| Enterprise | Yes |
**Rule of thumb:** If you have multiple epics that could be implemented by different agents, you need solutioning.
---
## The Cost of Skipping
Skipping solutioning on complex projects leads to:
- **Integration issues** discovered mid-sprint
- **Rework** due to conflicting implementations
- **Longer development time** overall
- **Technical debt** from inconsistent patterns
Catching alignment issues in solutioning is 10× faster than discovering them during implementation.
---
## Related
- [Four Phases](./four-phases.md) - Overview of all phases
- [Preventing Agent Conflicts](./preventing-agent-conflicts.md) - Detailed conflict prevention
- [Create Architecture](../../how-to/workflows/create-architecture.md) - How to do it

16
docs/explanation/bmad-builder/custom-content-types.md
View File

@ -14,21 +14,17 @@ This flexibility transforms the platform beyond its current capabilities, enabli
## Categories
- [Custom Content](#custom-content)
- [Categories](#categories)
- [Custom Stand Alone Modules](#custom-stand-alone-modules)
- [Custom Add On Modules](#custom-add-on-modules)
- [Custom Global Modules](#custom-global-modules)
- [Custom Agents](#custom-agents)
- [BMad Tiny Agents](#bmad-tiny-agents)
- [Simple and Expert Agents](#simple-and-expert-agents)
- [Custom Workflows](#custom-workflows)
- [Custom Stand Alone Modules](#custom-stand-alone-modules)
- [Custom Add On Modules](#custom-add-on-modules)
- [Custom Global Modules](#custom-global-modules)
- [Custom Agents](#custom-agents)
- [Custom Workflows](#custom-workflows)
## Custom Stand Alone Modules
Custom modules range from simple collections of related agents, workflows, and tools designed to work independently, to complex, expansive systems like the BMad Method or even larger applications.
Custom modules are [installable](./custom-content-installation.md) using the standard BMAD method and support advanced features:
Custom modules are [installable](../../how-to/installation/install-custom-modules.md) using the standard BMAD method and support advanced features:
- Optional user information collection during installation/updates
- Versioning and upgrade paths

67
docs/explanation/bmad-builder/index.md Normal file
View File

@ -0,0 +1,67 @@
---
sidebar_label: BMad Builder
description: Create custom agents, workflows, and modules for BMAD
---
# BMad Builder (BMB)
Create custom agents, workflows, and modules for BMAD.
---
## Quick Start
- **[Agent Creation Guide](../../tutorials/advanced/create-custom-agent.md)** - Step-by-step guide to building your first agent
---
## Agent Architecture
Comprehensive guides for each agent type:
- **Simple Agent Architecture** - Self-contained, optimized, personality-driven
- **Expert Agent Architecture** - Memory, sidecar files, domain restrictions
- **Module Agent Architecture** - Workflow integration, professional tools
---
## Key Concepts
### YAML to XML Compilation
Agents are authored in YAML with Handlebars templating. The compiler auto-injects:
1. **Frontmatter** - Name and description from metadata
2. **Activation Block** - Steps, menu handlers, rules
3. **Menu Enhancement** - `*help` and `*exit` commands added automatically
4. **Trigger Prefixing** - Your triggers auto-prefixed with `*`
---
## Reference Examples
Production-ready examples available in the BMB reference folder:
### Simple Agents
- **commit-poet** - Commit message artisan with style customization
### Expert Agents
- **journal-keeper** - Personal journal companion with memory and pattern recognition
### Module Agents
- **security-engineer** - BMM security specialist with threat modeling
- **trend-analyst** - CIS trend intelligence expert
---
## Installation Guide
For installing standalone simple and expert agents, see:
- [Install Custom Modules](../../how-to/installation/install-custom-modules.md)
---
## Related
- [Custom Content Types](./custom-content-types.md) - Understanding content types
- [Create Custom Agent](../../tutorials/advanced/create-custom-agent.md) - Tutorial

2
docs/modules/bmm-bmad-method/index.md → docs/explanation/bmm/index.md
View File

@ -18,7 +18,7 @@ Complete guides for the BMad Method Module (BMM) - AI-powered agile development
### 📊 Visual Overview
**[Complete Workflow Diagram](./images/workflow-method-greenfield.svg)** - Visual flowchart showing all phases, agents (color-coded), and decision points for the BMad Method standard greenfield track.
**[Complete Workflow Diagram](../../tutorials/getting-started/images/workflow-method-greenfield.svg)** - Visual flowchart showing all phases, agents (color-coded), and decision points for the BMad Method standard greenfield track.
## 📖 Core Concepts

205
docs/explanation/core-concepts/agent-roles.md Normal file
View File

@ -0,0 +1,205 @@
---
sidebar_label: Agent Roles
description: Understanding the different agent roles in BMad Method
---
# Agent Roles in BMad Method
BMad Method uses specialized AI agents, each with a distinct role, expertise, and personality. Understanding these roles helps you know which agent to use for each task.
---
## Core Agents Overview
| Agent | Role | Primary Phase |
|-------|------|---------------|
| **Analyst** | Research and discovery | Phase 1 (Analysis) |
| **PM** | Requirements and planning | Phase 2 (Planning) |
| **Architect** | Technical design | Phase 3 (Solutioning) |
| **SM** | Sprint orchestration | Phase 4 (Implementation) |
| **DEV** | Code implementation | Phase 4 (Implementation) |
| **TEA** | Test architecture | Phases 3-4 (Cross-phase) |
| **UX Designer** | User experience | Phase 2-3 |
| **Quick Flow Solo Dev** | Fast solo development | All phases (Quick Flow) |
---
## Phase 1: Analysis
### Analyst (Mary)
Business analysis and research specialist.
**Responsibilities:**
- Brainstorming and ideation
- Market, domain, and competitive research
- Product brief creation
- Brownfield project documentation
**Key Workflows:**
- `*brainstorm-project`
- `*research`
- `*product-brief`
- `*document-project`
**When to use:** Starting new projects, exploring ideas, validating market fit, documenting existing codebases.
---
## Phase 2: Planning
### PM (John)
Product requirements and planning expert.
**Responsibilities:**
- Creating Product Requirements Documents
- Defining functional and non-functional requirements
- Breaking requirements into epics and stories
- Validating implementation readiness
**Key Workflows:**
- `*create-prd`
- `*create-epics-and-stories`
- `*implementation-readiness`
**When to use:** Defining what to build, creating PRDs, organizing work into stories.
### UX Designer (Sally)
User experience and UI design specialist.
**Responsibilities:**
- UX specification creation
- User journey mapping
- Wireframe and mockup design
- Design system documentation
**Key Workflows:**
- `*create-ux-design`
- `*validate-design`
**When to use:** When UX is a primary differentiator, complex user workflows, design system creation.
---
## Phase 3: Solutioning
### Architect (Winston)
System architecture and technical design expert.
**Responsibilities:**
- System architecture design
- Architecture Decision Records (ADRs)
- Technical standards definition
- Implementation readiness validation
**Key Workflows:**
- `*create-architecture`
- `*implementation-readiness`
**When to use:** Multi-epic projects, cross-cutting technical decisions, preventing agent conflicts.
---
## Phase 4: Implementation
### SM (Bob)
Sprint planning and story preparation orchestrator.
**Responsibilities:**
- Sprint planning and tracking
- Story preparation for development
- Course correction handling
- Epic retrospectives
**Key Workflows:**
- `*sprint-planning`
- `*create-story`
- `*correct-course`
- `*epic-retrospective`
**When to use:** Organizing work, preparing stories, tracking progress.
### DEV (Amelia)
Story implementation and code review specialist.
**Responsibilities:**
- Story implementation with tests
- Code review
- Following architecture patterns
- Quality assurance
**Key Workflows:**
- `*dev-story`
- `*code-review`
**When to use:** Writing code, implementing stories, reviewing quality.
---
## Cross-Phase Agents
### TEA (Murat)
Test architecture and quality strategy expert.
**Responsibilities:**
- Test framework setup
- Test design and planning
- ATDD and automation
- Quality gate decisions
**Key Workflows:**
- `*framework`, `*ci`
- `*test-design`, `*atdd`, `*automate`
- `*test-review`, `*trace`, `*nfr-assess`
**When to use:** Setting up testing, creating test plans, quality gates.
---
## Quick Flow
### Quick Flow Solo Dev (Barry)
Fast solo development without handoffs.
**Responsibilities:**
- Technical specification
- End-to-end implementation
- Code review
**Key Workflows:**
- `*create-tech-spec`
- `*quick-dev`
- `*code-review`
**When to use:** Bug fixes, small features, rapid prototyping.
---
## Choosing the Right Agent
| Task | Agent |
|------|-------|
| Brainstorming ideas | Analyst |
| Market research | Analyst |
| Creating PRD | PM |
| Designing UX | UX Designer |
| System architecture | Architect |
| Preparing stories | SM |
| Writing code | DEV |
| Setting up tests | TEA |
| Quick bug fix | Quick Flow Solo Dev |
---
## Related
- [What Are Agents](./what-are-agents.md) - Foundational concepts
- [Agent Reference](../../reference/agents/index.md) - Complete command reference
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md)

22
docs/explanation/core-concepts/index.md
View File

@ -6,32 +6,32 @@ Understanding the fundamental building blocks of the BMAD Method.
| Concept | Description | Guide |
|---------|-------------|-------|
| **Agents** | AI assistants with personas, capabilities, and menus | [Agents Guide](./agents.md) |
| **Workflows** | Structured processes for achieving specific outcomes | [Workflows Guide](./workflows.md) |
| **Modules** | Packaged collections of agents and workflows | [Modules Guide](./modules.md) |
| **Agents** | AI assistants with personas, capabilities, and menus | [Agents Guide](./what-are-agents.md) |
| **Workflows** | Structured processes for achieving specific outcomes | [Workflows Guide](./what-are-workflows.md) |
| **Modules** | Packaged collections of agents and workflows | [Modules Guide](./what-are-modules.md) |
## Getting Started
### New to BMAD?
Start here to understand what BMAD is and how it works:
1. **[Agents Guide](./agents.md)** - Learn about Simple and Expert agents
2. **[Workflows Guide](./workflows.md)** - Understand how workflows orchestrate tasks
3. **[Modules Guide](./modules.md)** - See how modules organize functionality
1. **[Agents Guide](./what-are-agents.md)** - Learn about Simple and Expert agents
2. **[Workflows Guide](./what-are-workflows.md)** - Understand how workflows orchestrate tasks
3. **[Modules Guide](./what-are-modules.md)** - See how modules organize functionality
### Installing BMAD
- **[Installation Guide](./installing/)** - Set up BMAD in your project
- **[Upgrading from v4](./installing/upgrading.md)** - Migrate from earlier versions
- **[Installation Guide](../../how-to/installation/index.md)** - Set up BMAD in your project
- **[Upgrading from v4](../../how-to/installation/upgrade-to-v6.md)** - Migrate from earlier versions
### Configuration
- **[BMAD Customization](./bmad-customization/)** - Personalize agents and workflows
- **[BMAD Customization](../../how-to/customization/index.md)** - Personalize agents and workflows
### Advanced
- **[Web Bundles](./web-bundles/)** - Use BMAD in Gemini Gems and Custom GPTs
- **[Web Bundles](../features/web-bundles.md)** - Use BMAD in Gemini Gems and Custom GPTs
---
**Next:** Read the [Agents Guide](./agents.md) to understand the core building block of BMAD.
**Next:** Read the [Agents Guide](./what-are-agents.md) to understand the core building block of BMAD.

6
docs/explanation/core-concepts/what-are-agents.md
View File

@ -82,12 +82,12 @@ All agents share these building blocks:
## Creating Custom Agents
BMAD provides the **BMAD Builder (BMB)** module for creating your own agents. See the [Agent Creation Guide](../modules/bmb-bmad-builder/agent-creation-guide.md) for step-by-step instructions.
BMAD provides the **BMAD Builder (BMB)** module for creating your own agents. See the [Agent Creation Guide](../../tutorials/advanced/create-custom-agent.md) for step-by-step instructions.
## Customizing Existing Agents
You can modify any agent's behavior without editing core files. See [BMAD Customization](./bmad-customization/) for details. It is critical to never modify an installed agents .md file directly and follow the customization process, this way future updates to the agent or module its part of will continue to be updated and recompiled with the installer tool, and your customizations will still be retained.
You can modify any agent's behavior without editing core files. See [BMAD Customization](../../how-to/customization/index.md) for details. It is critical to never modify an installed agents .md file directly and follow the customization process, this way future updates to the agent or module its part of will continue to be updated and recompiled with the installer tool, and your customizations will still be retained.
---
**Next:** Learn about [Workflows](./workflows.md) to see how agents accomplish complex tasks.
**Next:** Learn about [Workflows](./what-are-workflows.md) to see how agents accomplish complex tasks.

4
docs/explanation/core-concepts/what-are-modules.md
View File

@ -69,8 +69,8 @@ Custom modules are installed the same way as official modules.
During BMAD installation, you choose which modules to install. You can also add or remove modules later by re-running the installer.
See [Installation Guide](./installing/) for details.
See [Installation Guide](../../how-to/installation/index.md) for details.
---
**Next:** Read the [Installation Guide](./installing/) to set up BMAD with the modules you need.
**Next:** Read the [Installation Guide](../../how-to/installation/index.md) to set up BMAD with the modules you need.

0
docs/modules/core/index.md → docs/explanation/core/index.md
View File

77
docs/modules/cis-creative-intelligence-suite/index.md → docs/explanation/creative-intelligence/index.md
View File

@ -1,20 +1,20 @@
# CIS - Creative Intelligence Suite
---
sidebar_label: Creative Intelligence
description: AI-powered creative facilitation with the Creative Intelligence Suite
---
# Creative Intelligence Suite (CIS)
AI-powered creative facilitation transforming strategic thinking through expert coaching across five specialized domains.
## Table of Contents
- [Core Capabilities](#core-capabilities)
- [Specialized Agents](#specialized-agents)
- [Interactive Workflows](#interactive-workflows)
- [Quick Start](#quick-start)
- [Key Differentiators](#key-differentiators)
- [Configuration](#configuration)
---
## Core Capabilities
CIS provides structured creative methodologies through distinctive agent personas who act as master facilitators, drawing out insights through strategic questioning rather than generating solutions directly.
---
## Specialized Agents
- **Carson** - Brainstorming Specialist (energetic facilitator)
@ -23,52 +23,49 @@ CIS provides structured creative methodologies through distinctive agent persona
- **Victor** - Innovation Oracle (bold strategic precision)
- **Sophia** - Master Storyteller (whimsical narrator)
## Interactive Workflows
---
[View all workflows →](../workflows/README.md)
## Interactive Workflows
**5 Workflows** with **150+ Creative Techniques:**
### Brainstorming
36 techniques across 7 categories for ideation
36 techniques across 7 categories for ideation:
- Divergent/convergent thinking
- Lateral connections
- Forced associations
### Design Thinking
Complete 5-phase human-centered process
Complete 5-phase human-centered process:
- Empathize → Define → Ideate → Prototype → Test
- User journey mapping
- Rapid iteration
### Problem Solving
Systematic root cause analysis
Systematic root cause analysis:
- 5 Whys, Fishbone diagrams
- Solution generation
- Impact assessment
### Innovation Strategy
Business model disruption
Business model disruption:
- Blue Ocean Strategy
- Jobs-to-be-Done
- Disruptive innovation patterns
### Storytelling
25 narrative frameworks
25 narrative frameworks:
- Hero's Journey
- Story circles
- Compelling pitch structures
---
## Quick Start
### Direct Workflow
@ -91,6 +88,8 @@ agent cis/brainstorming-coach
> *brainstorm
```
---
## Key Differentiators
- **Facilitation Over Generation** - Guides discovery through questions
@ -99,30 +98,7 @@ agent cis/brainstorming-coach
- **Persona-Driven** - Unique communication styles
- **Rich Method Libraries** - 150+ proven techniques
## Configuration
Edit `/_bmad/cis/config.yaml`:
```yaml
output_folder: ./creative-outputs
user_name: Your Name
communication_language: english
```
## Module Structure
```
cis/
├── agents/ # 5 specialized facilitators
├── workflows/ # 5 interactive processes
│ ├── brainstorming/
│ ├── design-thinking/
│ ├── innovation-strategy/
│ ├── problem-solving/
│ └── storytelling/
├── tasks/ # Supporting operations
└── teams/ # Agent collaborations
```
---
## Integration Points
@ -132,6 +108,8 @@ CIS workflows integrate with:
- **BMB** - Creative module design
- **Custom Modules** - Shared creative resource
---
## Best Practices
1. **Set clear objectives** before starting sessions
@ -140,10 +118,9 @@ CIS workflows integrate with:
4. **Take breaks** when energy flags
5. **Document insights** as they emerge
## Related Documentation
- **[BMM Documentation](../bmm/index.md)** - Core BMad Method documentation
---
Part of BMad Method v6.0 - Transform creative potential through expert AI facilitation.
## Related
- [Facilitation Over Generation](../philosophy/facilitation-over-generation.md) - Core philosophy
- [Brainstorming Techniques](../features/brainstorming-techniques.md) - Technique reference

6
docs/explanation/features/party-mode.md
View File

@ -105,9 +105,9 @@ _(Multiple perspectives reveal the right answer)_
## Related Documentation
- [Agents Guide](./agents-guide.md) - Complete agent reference
- [Quick Start Guide](./quick-start.md) - Getting started with BMM
- [FAQ](./faq.md) - Common questions
- [Agents Reference](../../reference/agents/index.md) - Complete agent reference
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Getting started with BMM
- [Setup Party Mode](../../how-to/workflows/setup-party-mode.md) - How to use it
---

170
docs/explanation/features/quick-flow.md Normal file
View File

@ -0,0 +1,170 @@
---
sidebar_label: Quick Flow
description: Understanding Quick Spec Flow for rapid development in BMad Method
---
# Quick Spec Flow
Quick Spec Flow is a streamlined alternative to the full BMad Method for Quick Flow track projects. Instead of going through Product Brief → PRD → Architecture, you go straight to a context-aware technical specification and start coding.
**Perfect for:** Bug fixes, small features, rapid prototyping, and quick enhancements
**Time to implementation:** Minutes, not hours
---
## When to Use Quick Flow
### ✅ Use Quick Flow when:
- Single bug fix or small enhancement
- Small feature with clear scope (typically 1-15 stories)
- Rapid prototyping or experimentation
- Adding to existing brownfield codebase
- You know exactly what you want to build
### ❌ Use BMad Method or Enterprise when:
- Building new products or major features
- Need stakeholder alignment
- Complex multi-team coordination
- Requires extensive planning and architecture
💡 **Not sure?** Run `workflow-init` to get a recommendation based on your project's needs!
---
## Quick Flow Overview
```mermaid
flowchart TD
START[Step 1: Run Tech-Spec Workflow]
DETECT[Detects project stack]
ANALYZE[Analyzes brownfield codebase]
TEST[Detects test frameworks]
CONFIRM[Confirms conventions]
GENERATE[Generates context-rich tech-spec]
STORIES[Creates ready-to-implement stories]
IMPL[Step 2: Implement with DEV Agent]
DONE[DONE!]
START --> DETECT
DETECT --> ANALYZE
ANALYZE --> TEST
TEST --> CONFIRM
CONFIRM --> GENERATE
GENERATE --> STORIES
STORIES --> IMPL
IMPL --> DONE
style START fill:#bfb,stroke:#333,stroke-width:2px
style IMPL fill:#bbf,stroke:#333,stroke-width:2px
style DONE fill:#f9f,stroke:#333,stroke-width:3px
```
---
## What Makes It Quick
- ✅ No Product Brief needed
- ✅ No PRD needed
- ✅ No Architecture doc needed
- ✅ Auto-detects your stack
- ✅ Auto-analyzes brownfield code
- ✅ Auto-validates quality
- ✅ Story context optional (tech-spec is comprehensive!)
---
## Smart Context Discovery
Quick Spec Flow automatically discovers and uses:
### Existing Documentation
- Product briefs (if they exist)
- Research documents
- `document-project` output (brownfield codebase map)
### Project Stack
- **Node.js:** package.json → frameworks, dependencies, scripts
- **Python:** requirements.txt, pyproject.toml → packages, tools
- **Ruby:** Gemfile → gems and versions
- **Java:** pom.xml, build.gradle → Maven/Gradle dependencies
- **Go:** go.mod → modules
- **Rust:** Cargo.toml → crates
### Brownfield Code Patterns
- Directory structure and organization
- Existing code patterns (class-based, functional, MVC)
- Naming conventions
- Test frameworks and patterns
- Code style configurations
### Convention Confirmation
Quick Spec Flow detects your conventions and **asks for confirmation**:
```
I've detected these conventions in your codebase:
Code Style:
- ESLint with Airbnb config
- Prettier with single quotes
Test Patterns:
- Jest test framework
- .test.js file naming
Should I follow these existing conventions? (yes/no)
```
**You decide:** Conform to existing patterns or establish new standards!
---
## Auto-Validation
Quick Spec Flow **automatically validates** everything:
- ✅ Context gathering completeness
- ✅ Definitiveness (no "use X or Y" statements)
- ✅ Brownfield integration quality
- ✅ Stack alignment
- ✅ Implementation readiness
---
## Comparison: Quick Flow vs Full BMM
| Aspect | Quick Flow Track | BMad Method/Enterprise Tracks |
| --------------------- | ---------------------------- | ---------------------------------- |
| **Setup** | None (standalone) | workflow-init recommended |
| **Planning Docs** | tech-spec.md only | Product Brief → PRD → Architecture |
| **Time to Code** | Minutes | Hours to days |
| **Best For** | Bug fixes, small features | New products, major features |
| **Context Discovery** | Automatic | Manual + guided |
| **Validation** | Auto-validates everything | Manual validation steps |
| **Brownfield** | Auto-analyzes and conforms | Manual documentation required |
---
## When to Graduate to BMad Method
Start with Quick Flow, but switch to BMad Method when:
- ❌ Project grows beyond initial scope
- ❌ Multiple teams need coordination
- ❌ Stakeholders need formal documentation
- ❌ Product vision is unclear
- ❌ Architectural decisions need deep analysis
- ❌ Compliance/regulatory requirements exist
💡 **Tip:** You can always run `workflow-init` later to transition from Quick Flow to BMad Method!
---
## Related
- [Create Tech Spec](../../how-to/workflows/create-tech-spec.md) - How to use Quick Flow
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Getting started
- [Four Phases](../architecture/four-phases.md) - Understanding the full methodology

219
docs/explanation/features/tea-overview.md Normal file
View File

@ -0,0 +1,219 @@
---
sidebar_label: TEA Overview
description: Understanding the Test Architect (TEA) agent and its role in BMad Method
---
# Test Architect (TEA) Overview
The Test Architect (TEA) is a specialized agent focused on quality strategy, test automation, and release gates in BMad Method projects.
## Overview
- **Persona:** Murat, Master Test Architect and Quality Advisor focused on risk-based testing, fixture architecture, ATDD, and CI/CD governance.
- **Mission:** Deliver actionable quality strategies, automation coverage, and gate decisions that scale with project complexity and compliance demands.
- **Use When:** BMad Method or Enterprise track projects, integration risk is non-trivial, brownfield regression risk exists, or compliance/NFR evidence is required. (Quick Flow projects typically don't require TEA)
---
## Choose Your TEA Engagement Model
BMad does not mandate TEA. There are five valid ways to use it (or skip it). Pick one intentionally.
1. **No TEA**
- Skip all TEA workflows. Use your existing team testing approach.
2. **TEA-only (Standalone)**
- Use TEA on a non-BMad project. Bring your own requirements, acceptance criteria, and environments.
- Typical sequence: `*test-design` (system or epic) -> `*atdd` and/or `*automate` -> optional `*test-review` -> `*trace` for coverage and gate decisions.
- Run `*framework` or `*ci` only if you want TEA to scaffold the harness or pipeline.
3. **Integrated: Greenfield - BMad Method (Simple/Standard Work)**
- Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
- Phase 4: per-epic `*test-design`, optional `*atdd`, then `*automate` and optional `*test-review`.
- Gate (Phase 2): `*trace`.
4. **Integrated: Brownfield - BMad Method or Enterprise (Simple or Complex)**
- Phase 2: baseline `*trace`.
- Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
- Phase 4: per-epic `*test-design` focused on regression and integration risks.
- Gate (Phase 2): `*trace`; `*nfr-assess` (if not done earlier).
- For brownfield BMad Method, follow the same flow with `*nfr-assess` optional.
5. **Integrated: Greenfield - Enterprise Method (Enterprise/Compliance Work)**
- Phase 2: `*nfr-assess`.
- Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
- Phase 4: per-epic `*test-design`, plus `*atdd`/`*automate`/`*test-review`.
- Gate (Phase 2): `*trace`; archive artifacts as needed.
If you are unsure, default to the integrated path for your track and adjust later.
---
## TEA Workflow Lifecycle
TEA integrates into the BMad development lifecycle during Solutioning (Phase 3) and Implementation (Phase 4):
```mermaid
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','secondaryColor':'#fff','tertiaryColor':'#fff','fontSize':'16px','fontFamily':'arial'}}}%%
graph TB
subgraph Phase2["<b>Phase 2: PLANNING</b>"]
PM["<b>PM: *prd (creates PRD with FRs/NFRs)</b>"]
PlanNote["<b>Business requirements phase</b>"]
NFR2["<b>TEA: *nfr-assess (optional, enterprise)</b>"]
PM -.-> NFR2
NFR2 -.-> PlanNote
PM -.-> PlanNote
end
subgraph Phase3["<b>Phase 3: SOLUTIONING</b>"]
Architecture["<b>Architect: *architecture</b>"]
EpicsStories["<b>PM/Architect: *create-epics-and-stories</b>"]
TestDesignSys["<b>TEA: *test-design (system-level)</b>"]
Framework["<b>TEA: *framework (optional if needed)</b>"]
CI["<b>TEA: *ci (optional if needed)</b>"]
GateCheck["<b>Architect: *implementation-readiness</b>"]
Architecture --> EpicsStories
Architecture --> TestDesignSys
TestDesignSys --> Framework
EpicsStories --> Framework
Framework --> CI
CI --> GateCheck
Phase3Note["<b>Epics created AFTER architecture,</b><br/><b>then system-level test design and test infrastructure setup</b>"]
EpicsStories -.-> Phase3Note
end
subgraph Phase4["<b>Phase 4: IMPLEMENTATION - Per Epic Cycle</b>"]
SprintPlan["<b>SM: *sprint-planning</b>"]
TestDesign["<b>TEA: *test-design (per epic)</b>"]
CreateStory["<b>SM: *create-story</b>"]
ATDD["<b>TEA: *atdd (optional, before dev)</b>"]
DevImpl["<b>DEV: implements story</b>"]
Automate["<b>TEA: *automate</b>"]
TestReview1["<b>TEA: *test-review (optional)</b>"]
Trace1["<b>TEA: *trace (refresh coverage)</b>"]
SprintPlan --> TestDesign
TestDesign --> CreateStory
CreateStory --> ATDD
ATDD --> DevImpl
DevImpl --> Automate
Automate --> TestReview1
TestReview1 --> Trace1
Trace1 -.->|next story| CreateStory
TestDesignNote["<b>Test design: 'How do I test THIS epic?'</b><br/>Creates test-design-epic-N.md per epic"]
TestDesign -.-> TestDesignNote
end
subgraph Gate["<b>EPIC/RELEASE GATE</b>"]
NFR["<b>TEA: *nfr-assess (if not done earlier)</b>"]
TestReview2["<b>TEA: *test-review (final audit, optional)</b>"]
TraceGate["<b>TEA: *trace - Phase 2: Gate</b>"]
GateDecision{"<b>Gate Decision</b>"}
NFR --> TestReview2
TestReview2 --> TraceGate
TraceGate --> GateDecision
GateDecision -->|PASS| Pass["<b>PASS ✅</b>"]
GateDecision -->|CONCERNS| Concerns["<b>CONCERNS ⚠️</b>"]
GateDecision -->|FAIL| Fail["<b>FAIL ❌</b>"]
GateDecision -->|WAIVED| Waived["<b>WAIVED ⏭️</b>"]
end
Phase2 --> Phase3
Phase3 --> Phase4
Phase4 --> Gate
style Phase2 fill:#bbdefb,stroke:#0d47a1,stroke-width:3px,color:#000
style Phase3 fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px,color:#000
style Phase4 fill:#e1bee7,stroke:#4a148c,stroke-width:3px,color:#000
style Gate fill:#ffe082,stroke:#f57c00,stroke-width:3px,color:#000
style Pass fill:#4caf50,stroke:#1b5e20,stroke-width:3px,color:#000
style Concerns fill:#ffc107,stroke:#f57f17,stroke-width:3px,color:#000
style Fail fill:#f44336,stroke:#b71c1c,stroke-width:3px,color:#000
style Waived fill:#9c27b0,stroke:#4a148c,stroke-width:3px,color:#000
```
**Phase Numbering Note:** BMad uses a 4-phase methodology with optional Phase 1 and documentation prerequisite:
- **Documentation** (Optional for brownfield): Prerequisite using `*document-project`
- **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`)
- **Phase 2** (Required): Planning (`*prd` creates PRD with FRs/NFRs)
- **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*test-design` (system-level) → `*create-epics-and-stories` → TEA: `*framework`, `*ci` → `*implementation-readiness`)
- **Phase 4** (Required): Implementation (`*sprint-planning` → per-epic: `*test-design` → per-story: dev workflows)
**TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` is **dual-mode**:
- **System-level (Phase 3):** Run immediately after architecture/ADR drafting to produce `test-design-system.md` (testability review, ADR → test mapping, Architecturally Significant Requirements (ASRs), environment needs). Feeds the implementation-readiness gate.
- **Epic-level (Phase 4):** Run per-epic to produce `test-design-epic-N.md` (risk, priorities, coverage plan).
Quick Flow track skips Phases 1 and 3.
BMad Method and Enterprise use all phases based on project needs.
When an ADR or architecture draft is produced, run `*test-design` in **system-level** mode before the implementation-readiness gate. This ensures the ADR has an attached testability review and ADR → test mapping. Keep the test-design updated if ADRs change.
---
## Why TEA is Different from Other BMM Agents
TEA is the only BMM agent that operates in **multiple phases** (Phase 3 and Phase 4) and has its own **knowledge base architecture**.
### Phase-Specific Agents (Standard Pattern)
Most BMM agents work in a single phase:
- **Phase 1 (Analysis)**: Analyst agent
- **Phase 2 (Planning)**: PM agent
- **Phase 3 (Solutioning)**: Architect agent
- **Phase 4 (Implementation)**: SM, DEV agents
### TEA: Multi-Phase Quality Agent (Unique Pattern)
TEA is **the only agent that operates in multiple phases**:
```
Phase 1 (Analysis) → [TEA not typically used]
↓
Phase 2 (Planning) → [PM defines requirements - TEA not active]
↓
Phase 3 (Solutioning) → TEA: *framework, *ci (test infrastructure AFTER architecture)
↓
Phase 4 (Implementation) → TEA: *test-design (per epic: "how do I test THIS feature?")
→ TEA: *atdd, *automate, *test-review, *trace (per story)
↓
Epic/Release Gate → TEA: *nfr-assess, *trace Phase 2 (release decision)
```
### TEA's 8 Workflows Across Phases
**Standard agents**: 1-3 workflows per phase
**TEA**: 8 workflows across Phase 3, Phase 4, and Release Gate
| Phase | TEA Workflows | Frequency | Purpose |
| ----------- | --------------------------------------------------------- | ---------------- | ---------------------------------------------- |
| **Phase 2** | (none) | - | Planning phase - PM defines requirements |
| **Phase 3** | \*framework, \*ci | Once per project | Setup test infrastructure AFTER architecture |
| **Phase 4** | \*test-design, \*atdd, \*automate, \*test-review, \*trace | Per epic/story | Test planning per epic, then per-story testing |
| **Release** | \*nfr-assess, \*trace (Phase 2: gate) | Per epic/release | Go/no-go decision |
**Note**: `*trace` is a two-phase workflow: Phase 1 (traceability) + Phase 2 (gate decision). This reduces cognitive load while maintaining natural workflow.
---
## TEA Command Catalog
| Command | Primary Outputs | Notes |
| -------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- |
| `*framework` | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs | Use when no production-ready harness exists |
| `*ci` | CI workflow, selective test scripts, secrets checklist | Platform-aware (GitHub Actions default) |
| `*test-design` | Combined risk assessment, mitigation plan, and coverage strategy | Risk scoring + optional exploratory mode |
| `*atdd` | Failing acceptance tests + implementation checklist | TDD red phase + optional recording mode |
| `*automate` | Prioritized specs, fixtures, README/script updates, DoD summary | Optional healing/recording, avoid duplicate coverage |
| `*test-review` | Test quality review report with 0-100 score, violations, fixes | Reviews tests against knowledge base patterns |
| `*nfr-assess` | NFR assessment report with actions | Focus on security/performance/reliability |
| `*trace` | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision |
---
## Related Documentation
- [Setup Test Framework](../../how-to/workflows/setup-test-framework.md) - How to set up testing infrastructure
- [Run Test Design](../../how-to/workflows/run-test-design.md) - Creating test plans

151
docs/explanation/game-dev/bmgd-vs-bmm.md Normal file
View File

@ -0,0 +1,151 @@
---
sidebar_label: BMGD vs BMM
description: Understanding the differences between BMGD and BMM
---
# BMGD vs BMM
BMGD (BMad Game Development) extends BMM (BMad Method) with game-specific capabilities. This page explains the key differences.
---
## Quick Comparison
| Aspect | BMM | BMGD |
| -------------- | ------------------------------------- | ------------------------------------------------------------------------ |
| **Focus** | General software | Game development |
| **Agents** | PM, Architect, Dev, SM, TEA, Solo Dev | Game Designer, Game Dev, Game Architect, Game SM, Game QA, Game Solo Dev |
| **Planning** | PRD, Tech Spec | Game Brief, GDD |
| **Types** | N/A | 24 game type templates |
| **Narrative** | N/A | Full narrative workflow |
| **Testing** | Web-focused | Engine-specific (Unity, Unreal, Godot) |
| **Production** | BMM workflows | BMM workflows with game overrides |
---
## Agent Differences
### BMM Agents
- PM (Product Manager)
- Architect
- DEV (Developer)
- SM (Scrum Master)
- TEA (Test Architect)
- Quick Flow Solo Dev
### BMGD Agents
- Game Designer
- Game Developer
- Game Architect
- Game Scrum Master
- Game QA
- Game Solo Dev
BMGD agents understand game-specific concepts like:
- Game mechanics and balance
- Player psychology
- Engine-specific patterns
- Playtesting and QA
---
## Planning Documents
### BMM Planning
- **Product Brief** → **PRD** → **Architecture**
- Focus: Software requirements, user stories, system design
### BMGD Planning
- **Game Brief** → **GDD** → **Architecture**
- Focus: Game vision, mechanics, narrative, player experience
The GDD (Game Design Document) includes:
- Core gameplay loop
- Mechanics and systems
- Progression and balance
- Art and audio direction
- Genre-specific sections
---
## Game Type Templates
BMGD includes 24 game type templates that auto-configure GDD sections:
- Action, Adventure, Puzzle
- RPG, Strategy, Simulation
- Sports, Racing, Fighting
- Horror, Platformer, Shooter
- And more...
Each template provides:
- Genre-specific GDD sections
- Relevant mechanics patterns
- Testing considerations
- Common pitfalls to avoid
---
## Narrative Support
BMGD includes full narrative workflow for story-driven games:
- **Narrative Design** workflow
- Story structure templates
- Character development
- World-building guidelines
- Dialogue systems
BMM has no equivalent for narrative design.
---
## Testing Differences
### BMM Testing (TEA)
- Web-focused (Playwright, Cypress)
- API testing
- E2E for web applications
### BMGD Testing (Game QA)
- Engine-specific frameworks (Unity, Unreal, Godot)
- Gameplay testing
- Performance profiling
- Playtest planning
- Balance validation
---
## Production Workflow
BMGD production workflows **inherit from BMM** and add game-specific:
- Checklists
- Templates
- Quality gates
- Engine-specific considerations
This means you get all of BMM's implementation structure plus game-specific enhancements.
---
## When to Use Each
### Use BMM when:
- Building web applications
- Creating APIs and services
- Developing mobile apps (non-game)
- Any general software project
### Use BMGD when:
- Building video games
- Creating interactive experiences
- Game prototyping
- Game jams
---
## Related
- [BMGD Overview](./index.md) - Getting started with BMGD
- [Game Types Guide](./game-types.md) - Understanding game templates
- [Quick Start BMGD](../../tutorials/getting-started/quick-start-bmgd.md) - Tutorial

6
docs/explanation/game-dev/game-types.md
View File

@ -498,6 +498,6 @@ When you select a game type, BMGD adds these GDD sections:
## Next Steps
- **[Quick Start Guide](./quick-start.md)** - Get started with BMGD
- **[Workflows Guide](./workflows-guide.md)** - GDD workflow details
- **[Glossary](./glossary.md)** - Game development terminology
- **[Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)** - Get started with BMGD
- **[Workflows Guide](../../reference/workflows/bmgd-workflows.md)** - GDD workflow details
- **[Glossary](../../reference/glossary/index.md)** - Game development terminology

86
docs/explanation/game-dev/index.md Normal file
View File

@ -0,0 +1,86 @@
---
sidebar_label: Game Development
description: AI-powered workflows for game design and development with BMGD
---
# BMGD - Game Development Module
Complete guides for the BMad Game Development Module (BMGD) - AI-powered workflows for game design and development that adapt to your project's needs.
---
## Getting Started
**New to BMGD?** Start here:
- **[Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)** - Get started building your first game
- Installation and setup
- Understanding the game development phases
- Running your first workflows
- Agent-based development flow
**Quick Path:** Install BMGD module → Game Brief → GDD → Architecture → Build
---
## Core Documentation
- **[Game Types Guide](./game-types.md)** - Selecting and using game type templates (24 supported types)
- **[BMGD vs BMM](./bmgd-vs-bmm.md)** - Understanding the differences
---
## Game Development Phases
BMGD follows four phases aligned with game development:
### Phase 1: Preproduction
- **Brainstorm Game** - Ideation with game-specific techniques
- **Game Brief** - Capture vision, market, and fundamentals
### Phase 2: Design
- **GDD (Game Design Document)** - Comprehensive game design
- **Narrative Design** - Story, characters, world (for story-driven games)
### Phase 3: Technical
- **Game Architecture** - Engine, systems, patterns, structure
### Phase 4: Production
- **Sprint Planning** - Epic and story management
- **Story Development** - Implementation workflow
- **Code Review** - Quality assurance
- **Testing** - Automated tests, playtesting, performance
- **Retrospective** - Continuous improvement
---
## Choose Your Path
### I need to...
**Start a new game project**
→ Start with [Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)
→ Run `brainstorm-game` for ideation
→ Create a Game Brief with `create-brief`
**Design my game**
→ Create a GDD with `create-gdd`
→ If story-heavy, add Narrative Design with `create-narrative`
**Plan the technical architecture**
→ Run `create-architecture` with the Game Architect
**Build my game**
→ Use Phase 4 production workflows
→ Follow the sprint-based development cycle
**Quickly test an idea**
→ Use [Quick-Flow](../../how-to/workflows/bmgd-quick-flow.md) for rapid prototyping
---
## Related
- [Game Types Guide](./game-types.md) - Understanding game type templates
- [BMGD vs BMM](./bmgd-vs-bmm.md) - Comparison with core method
- [Glossary](../../reference/glossary/index.md) - Terminology reference

122
docs/explanation/philosophy/facilitation-over-generation.md Normal file
View File

@ -0,0 +1,122 @@
---
sidebar_label: Facilitation Over Generation
description: Understanding CIS's facilitation-first approach to creative work
---
# Facilitation Over Generation
The Creative Intelligence Suite (CIS) takes a fundamentally different approach from typical AI tools. Instead of generating solutions directly, CIS agents act as master facilitators who guide you to discover insights yourself.
---
## The Problem with Generation
Traditional AI approaches to creative work:
```
User: "Give me marketing ideas"
AI: "Here are 10 marketing ideas..."
```
This approach:
- Produces generic, predictable outputs
- Removes human ownership of ideas
- Misses context and nuance
- Limits creative exploration
---
## The Facilitation Approach
CIS agents use strategic questioning:
```
User: "I need marketing ideas"
CIS: "What makes your customers choose you over alternatives?
What's the one thing they always mention?"
User: "They say our support is exceptional"
CIS: "Interesting! How might you make that exceptional
support visible before they become customers?"
```
This approach:
- Draws out insights already within you
- Maintains human ownership of ideas
- Captures context and nuance
- Enables deeper creative exploration
---
## Key Principles
### 1. Questions Over Answers
CIS agents ask strategic questions rather than providing direct answers. This:
- Activates your own creative thinking
- Uncovers assumptions
- Reveals blind spots
- Builds on your domain knowledge
### 2. Energy-Aware Sessions
CIS monitors engagement and adapts:
- Adjusts pace when energy flags
- Suggests breaks when needed
- Changes techniques to maintain momentum
- Recognizes productive vs. unproductive struggle
### 3. Process Trust
CIS uses proven methodologies:
- Design Thinking's 5 phases
- Structured brainstorming techniques
- Root cause analysis frameworks
- Innovation strategy patterns
You're not just having a conversation—you're following time-tested creative processes.
### 4. Persona-Driven Engagement
Each CIS agent has a distinct personality:
- **Carson** - Energetic, encouraging
- **Maya** - Jazz-like, improvisational
- **Dr. Quinn** - Analytical, methodical
- **Victor** - Bold, strategic
- **Sophia** - Narrative, imaginative
These personas create engaging experiences that maintain creative flow.
---
## When Generation is Appropriate
CIS does generate when appropriate:
- Synthesizing session outputs
- Documenting decisions
- Creating structured artifacts
- Providing technique examples
But the core creative work happens through facilitated discovery.
---
## Benefits
### For Individuals
- Deeper insights than pure generation
- Ownership of creative outputs
- Skill development in creative thinking
- More memorable and actionable ideas
### For Teams
- Shared creative experience
- Aligned understanding
- Documented rationale
- Stronger buy-in to outcomes
---
## Related
- [Creative Intelligence Suite](../creative-intelligence/index.md) - CIS overview
- [Brainstorming Techniques](../features/brainstorming-techniques.md) - Available techniques

92
docs/how-to/brownfield/add-feature-to-existing.md Normal file
View File

@ -0,0 +1,92 @@
---
sidebar_label: Add Feature
description: How to add new features to an existing brownfield project
---
# How to Add a Feature to an Existing Project
Add new functionality to your brownfield codebase while respecting existing patterns and architecture.
---
## When to Use This
- Adding a new feature to an existing codebase
- Major enhancements that need proper planning
- Features that touch multiple parts of the system
---
## Prerequisites
- BMad Method installed
- Existing project documentation (run `document-project` first if needed)
- Clear understanding of what you want to build
---
## Steps
### 1. Run workflow-init
```
Run workflow-init
```
The workflow should recognize you're in an existing project. If not, explicitly clarify that this is brownfield development.
### 2. Choose Your Approach
| Feature Scope | Recommended Approach |
|---------------|---------------------|
| Small (1-5 stories) | Quick Flow with tech-spec |
| Medium (5-15 stories) | BMad Method with PRD |
| Large (15+ stories) | Full BMad Method with architecture |
### 3. Create Planning Documents
**For Quick Flow:**
- Load PM agent
- Run tech-spec workflow
- The agent will analyze your existing codebase and create a context-aware spec
**For BMad Method:**
- Load PM agent
- Run PRD workflow
- Ensure the agent reads your existing documentation
- Review that integration points are clearly identified
### 4. Consider Architecture Impact
If your feature affects system architecture:
- Load Architect agent
- Run architecture workflow
- Ensure alignment with existing patterns
- Document any new ADRs (Architecture Decision Records)
### 5. Implement
Follow the standard Phase 4 implementation workflows:
1. `sprint-planning` - Organize your work
2. `create-story` - Prepare each story
3. `dev-story` - Implement with tests
4. `code-review` - Quality assurance
---
## Tips
- Always ensure agents read your existing documentation
- Pay attention to integration points with existing code
- Follow existing conventions unless deliberately changing them
- Document why you're adding new patterns (if any)
---
## Related
- [Brownfield Onboarding Tutorial](../../tutorials/advanced/brownfield-onboarding.md)
- [Document Existing Project](./document-existing-project.md)
- [Quick Fix in Brownfield](./quick-fix-in-brownfield.md)

85
docs/how-to/brownfield/document-existing-project.md Normal file
View File

@ -0,0 +1,85 @@
---
sidebar_label: Document Existing Project
description: How to document an existing brownfield codebase using BMad Method
---
# How to Document an Existing Project
Use the `document-project` workflow to scan your entire codebase and generate comprehensive documentation about its current state.
---
## When to Use This
- Starting work on an undocumented legacy project
- Documentation is outdated and needs refresh
- AI agents need context about existing code patterns
- Onboarding new team members
---
## Prerequisites
- BMad Method installed in your project
- Access to the codebase you want to document
---
## Steps
### 1. Load the Analyst Agent
Start a fresh chat and load the Analyst agent.
### 2. Run the document-project Workflow
Tell the agent:
```
Run the document-project workflow
```
### 3. Let the Agent Scan Your Codebase
The workflow will:
- Scan your codebase structure
- Identify architecture patterns
- Document the technology stack
- Create reference documentation
- Generate a PRD-like document from existing code
### 4. Review the Generated Documentation
The output will be saved to `project-documentation-{date}.md` in your output folder.
Review the documentation for:
- Accuracy of detected patterns
- Completeness of architecture description
- Any missing business rules or intent
---
## What You Get
- **Project overview** - High-level description of what the project does
- **Technology stack** - Detected frameworks, libraries, and tools
- **Architecture patterns** - Code organization and design patterns found
- **Business rules** - Logic extracted from the codebase
- **Integration points** - External APIs and services
---
## Tips
- Run this before any major brownfield work
- Keep the documentation updated as the project evolves
- Use it as input for future PRD creation
---
## Related
- [Brownfield Onboarding Tutorial](../../tutorials/advanced/brownfield-onboarding.md)
- [Add Feature to Existing Project](./add-feature-to-existing.md)

95
docs/how-to/brownfield/quick-fix-in-brownfield.md Normal file
View File

@ -0,0 +1,95 @@
---
sidebar_label: Quick Fixes
description: How to make quick fixes and ad-hoc changes in brownfield projects
---
# How to Make Quick Fixes in Brownfield Projects
Not everything requires the full BMad method or even Quick Flow. For bug fixes, refactorings, or small targeted changes, you can work directly with the agent.
---
## When to Use This
- Bug fixes
- Small refactorings
- Targeted code improvements
- Learning about your codebase
- One-off changes that don't need planning
---
## Steps
### 1. Load an Agent
For quick fixes, you can use:
- **DEV agent** - For implementation-focused work
- **Quick Flow Solo Dev** - For slightly larger changes that still need a tech-spec
### 2. Describe the Change
Simply tell the agent what you need:
```
Fix the login validation bug that allows empty passwords
```
or
```
Refactor the UserService to use async/await instead of callbacks
```
### 3. Let the Agent Work
The agent will:
- Analyze the relevant code
- Propose a solution
- Implement the change
- Run tests (if available)
### 4. Review and Commit
Review the changes made and commit when satisfied.
---
## Learning Your Codebase
This approach is also excellent for exploring unfamiliar code:
```
Explain how the authentication system works in this codebase
```
```
Show me where error handling happens in the API layer
```
LLMs are excellent at interpreting and analyzing code—whether it was AI-generated or not. Use the agent to:
- Learn about your project
- Understand how things are built
- Explore unfamiliar parts of the codebase
---
## When to Upgrade to Formal Planning
Consider using Quick Flow or full BMad Method when:
- The change affects multiple files or systems
- You're unsure about the scope
- The fix keeps growing in complexity
- You need documentation for the change
---
## Related
- [Brownfield Onboarding Tutorial](../../tutorials/advanced/brownfield-onboarding.md)
- [Add Feature to Existing Project](./add-feature-to-existing.md)
- [Quick Spec Flow](../../explanation/features/quick-flow.md)

4
docs/how-to/customization/customize-agents.md
View File

@ -203,8 +203,8 @@ memories:
## Next Steps
- **[Learn about Agents](../agents.md)** - Understand Simple vs Expert agents
- **[Learn about Agents](../../explanation/core-concepts/what-are-agents.md)** - Understand Simple vs Expert agents
- **[Agent Creation Guide](../../tutorials/advanced/create-custom-agent.md)** - Build completely custom agents
- **[BMM Complete Documentation](../../modules/bmm-bmad-method/index)** - Full BMad Method reference
- **[BMM Complete Documentation](../../explanation/bmm/index.md)** - Full BMad Method reference
[← Back to Customization](./index.md)

2
docs/how-to/customization/customize-workflows.md
View File

@ -20,7 +20,7 @@ Workflow customization will allow you to:
While workflow customization is in development, you can:
- **Create Custom Workflows** - Use the BMAD Builder to create entirely new workflows
- **Customize Agents** - Modify agent behavior using [Agent Customization](./agents.md)
- **Customize Agents** - Modify agent behavior using [Agent Customization](./customize-agents.md)
- **Provide Feedback** - Share your workflow customization needs with the community
---

6
docs/how-to/customization/index.md
View File

@ -6,8 +6,8 @@ Personalize agents and workflows to match your needs.
| Guide | Description |
|-------|-------------|
| **[Agent Customization](./agents.md)** | Modify agent behavior without editing core files |
| **[Workflow Customization](./workflows.md)** | Customize and optimize workflows |
| **[Agent Customization](./customize-agents.md)** | Modify agent behavior without editing core files |
| **[Workflow Customization](./customize-workflows.md)** | Customize and optimize workflows |
## Overview
@ -21,6 +21,6 @@ Replace or extend workflow steps to create tailored processes. (Coming soon)
---
**Next:** Read the [Agent Customization Guide](./agents.md) to start personalizing your agents.
**Next:** Read the [Agent Customization Guide](./customize-agents.md) to start personalizing your agents.
[← Back to Core Concepts](../index.md)

20
docs/how-to/customization/shard-large-documents.md
View File

@ -4,21 +4,11 @@ Comprehensive guide to BMad Method's document sharding system for managing large
## Table of Contents
- [Document Sharding Guide](#document-sharding-guide)
- [Table of Contents](#table-of-contents)
- [What is Document Sharding?](#what-is-document-sharding)
- [Architecture](#architecture)
- [When to Use Sharding](#when-to-use-sharding)
- [Ideal Candidates](#ideal-candidates)
- [How Sharding Works](#how-sharding-works)
- [Sharding Process](#sharding-process)
- [Workflow Discovery](#workflow-discovery)
- [Using the Shard-Doc Tool](#using-the-shard-doc-tool)
- [CLI Command](#cli-command)
- [Interactive Process](#interactive-process)
- [What Gets Created](#what-gets-created)
- [Workflow Support](#workflow-support)
- [Universal Support](#universal-support)
- [What is Document Sharding?](#what-is-document-sharding)
- [When to Use Sharding](#when-to-use-sharding)
- [How Sharding Works](#how-sharding-works)
- [Using the Shard-Doc Tool](#using-the-shard-doc-tool)
- [Workflow Support](#workflow-support)
## What is Document Sharding?

2
docs/how-to/customization/vendor-workflows.md
View File

@ -1,4 +1,4 @@
# Workflow Vendoring, Customization, and Inheritance (Official Support Consing Soon)
# Workflow Vendoring, Customization, and Inheritance (Official Support Coming Soon))
Vendoring and Inheritance of workflows are 2 ways of sharing or reutilizing workflows - but with some key distinctions and use cases.

16
docs/how-to/installation/index.md Normal file
View File

@ -0,0 +1,16 @@
---
sidebar_label: Installation
description: How to install and upgrade BMad Method
---
# Installation Guides
How-to guides for installing and configuring the BMad Method.
## Available Guides
| Guide | Description |
|-------|-------------|
| **[Install BMad](./install-bmad.md)** | Step-by-step installation instructions |
| **[Install Custom Modules](./install-custom-modules.md)** | Add custom agents, workflows, and modules |
| **[Upgrade to v6](./upgrade-to-v6.md)** | Migrate from BMad v4 to v6 |

141
docs/how-to/installation/install-bmad.md Normal file
View File

@ -0,0 +1,141 @@
---
sidebar_label: Install BMAD
description: Step-by-step guide to installing BMAD in your project
---
# How to Install BMAD
Complete guide to installing BMAD in your project.
---
## Prerequisites
- **Node.js** 20+ (required for the installer)
- **Git** (recommended)
- **AI-powered IDE** (Claude Code, Cursor, Windsurf, or similar)
---
## Steps
### 1. Run the Installer
```bash
npx bmad-method install
```
### 2. Choose Installation Location
The installer will ask where to install BMAD files. Options:
- Current directory (recommended for new projects)
- Subdirectory
- Custom path
### 3. Select Your AI Tools
Choose which AI tools you'll be using:
- Claude Code
- Cursor
- Windsurf
- Other
The installer configures BMAD for your selected tools.
### 4. Choose Modules
Select which modules to install:
| Module | Purpose |
|--------|---------|
| **BMM** | Core methodology for software development |
| **BMGD** | Game development workflows |
| **CIS** | Creative intelligence and facilitation |
| **BMB** | Building custom agents and workflows |
### 5. Add Custom Content (Optional)
If you have custom agents, workflows, or modules:
- Point to their location
- The installer will integrate them
### 6. Configure Settings
For each module, either:
- Accept recommended defaults (faster)
- Customize settings (more control)
---
## Verify Installation
After installation, verify by:
1. Checking the `_bmad/` directory exists
2. Loading an agent in your AI tool
3. Running `*menu` to see available commands
---
## Directory Structure
```
your-project/
├── _bmad/
│ ├── bmm/ # Method module
│ │ ├── agents/ # Agent files
│ │ ├── workflows/ # Workflow files
│ │ └── config.yaml # Module config
│ ├── core/ # Core utilities
│ └── ...
├── _bmad-output/ # Generated artifacts
└── .claude/ # IDE configuration
```
---
## Configuration
Edit `_bmad/[module]/config.yaml` to customize:
```yaml
output_folder: ./_bmad-output
user_name: Your Name
communication_language: english
```
---
## Troubleshooting
### "Command not found: npx"
Install Node.js 20+:
```bash
# macOS with Homebrew
brew install node
# Or download from nodejs.org
```
### "Permission denied"
Check npm permissions:
```bash
npm config set prefix ~/.npm-global
```
### Installer hangs
Try running with verbose output:
```bash
npx bmad-method install --verbose
```
---
## Related
- [Installation Tutorial](../../tutorials/getting-started/installation.md) - Getting started
- [Upgrade to V6](./upgrade-to-v6.md) - Upgrading from previous versions
- [Install Custom Modules](./install-custom-modules.md) - Adding custom content

4
docs/how-to/installation/install-custom-modules.md
View File

@ -2,7 +2,7 @@
This guide explains how to create and install custom BMAD content including agents, workflows, and modules. Custom content extends BMAD's functionality with specialized tools and workflows that can be shared across projects or teams.
For detailed information about the different types of custom content available, see [Custom Content](modules/bmb-bmad-builder/custom-content.md).
For detailed information about the different types of custom content available, see [Custom Content Types](../../explanation/bmad-builder/custom-content-types.md).
You can find example custom modules in the `samples/sample-custom-modules/` folder of the repository. Download either of the sample folders to try them out.
@ -57,7 +57,7 @@ For standalone content that isn't part of a cohesive module collection, follow t
- Add the property `unitary: true` in the module.yaml
- The `unitary: true` property indicates this is a collection of potentially unrelated items that don't depend on each other
- Any content you add to this folder should still be nested under workflows and agents - but the key with stand alone content is they do not rely on each other.
- Agents do not reference other workflows even if stored in a unitary:true module. But unitary Agents can have their own workflows in their sidecar, or reference workflows as requirements from other modules - with a process known as workflow vendoring. Keep in mind, this will require that the workflow referenced from the other module would need to be available for the end user to install, so its recommended to only vendor workflows from the core module, or official bmm modules (See [Workflow Vendoring, Customization, and Inheritance](workflow-vendoring-customization-inheritance.md)).
- Agents do not reference other workflows even if stored in a unitary:true module. But unitary Agents can have their own workflows in their sidecar, or reference workflows as requirements from other modules - with a process known as workflow vendoring. Keep in mind, this will require that the workflow referenced from the other module would need to be available for the end user to install, so its recommended to only vendor workflows from the core module, or official bmm modules.
2. **Folder Structure**
Organize content in specific named folders:

2
docs/how-to/installation/upgrade-to-v6.md
View File

@ -120,7 +120,7 @@ persona:
- Always upbeat and adventurous
```
There is a lot more that is possible with agent customization, which is covered in detail in the [Agent Customization Guide](../bmad-customization/agents.md)
There is a lot more that is possible with agent customization, which is covered in detail in the [Agent Customization Guide](../customization/customize-agents.md)
CRITICAL NOTE: After you modify the customization file, you need to run the npx installer against your installed location, and choose the option to rebuild all agents, or just do a quick update again. This always builds agents fresh and applies customizations.

0
docs/modules/bmgd-bmad-game-dev/troubleshooting.md → docs/how-to/troubleshooting/bmgd-troubleshooting.md
View File

6
docs/how-to/workflows/bmgd-quick-flow.md
View File

@ -283,6 +283,6 @@ If quick-dev keeps expanding scope, stop and create proper stories.
## Next Steps
- **[Workflows Guide](./workflows-guide.md)** - Full workflow reference
- **[Agents Guide](./agents-guide.md)** - Agent capabilities
- **[Quick Start Guide](./quick-start.md)** - Getting started with BMGD
- **[Workflows Guide](../../reference/workflows/bmgd-workflows.md)** - Full workflow reference
- **[Agents Guide](../../reference/agents/bmgd-agents.md)** - Agent capabilities
- **[Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)** - Getting started with BMGD

131
docs/how-to/workflows/conduct-research.md Normal file
View File

@ -0,0 +1,131 @@
---
sidebar_label: Conduct Research
description: How to conduct market, technical, and competitive research using BMad Method
---
# How to Conduct Research
Use the `research` workflow to perform comprehensive multi-type research for validating ideas, understanding markets, and making informed decisions.
---
## When to Use This
- Need market viability validation
- Choosing frameworks or platforms
- Understanding competitive landscape
- Need user understanding
- Understanding domain or industry
- Need deeper AI-assisted research
---
## Prerequisites
- BMad Method installed
- Analyst agent available
---
## Steps
### 1. Load the Analyst Agent
Start a fresh chat and load the Analyst agent.
### 2. Run the Research Workflow
```
*research
```
### 3. Choose Research Type
Select the type of research you need:
| Type | Purpose | Use When |
| --------------- | ------------------------------------------------------ | ----------------------------------- |
| **market** | TAM/SAM/SOM, competitive analysis | Need market viability validation |
| **technical** | Technology evaluation, ADRs | Choosing frameworks/platforms |
| **competitive** | Deep competitor analysis | Understanding competitive landscape |
| **user** | Customer insights, personas, JTBD | Need user understanding |
| **domain** | Industry deep dives, trends | Understanding domain/industry |
| **deep_prompt** | Generate AI research prompts (ChatGPT, Claude, Gemini) | Need deeper AI-assisted research |
### 4. Provide Context
Give the agent details about what you're researching:
- "SaaS project management tool"
- "React vs Vue for our dashboard"
- "Fintech compliance requirements"
### 5. Set Research Depth
Choose your depth level:
- **Quick** - Fast overview
- **Standard** - Balanced depth
- **Comprehensive** - Deep analysis
---
## What You Get
### Market Research Example
```
TAM: $50B
SAM: $5B
SOM: $50M
Top Competitors:
- Asana
- Monday
- etc.
Positioning Recommendation: ...
```
### Technical Research Example
Technology evaluation with:
- Comparison matrix
- Trade-off analysis
- Recommendations with rationale
---
## Key Features
- Real-time web research
- Multiple analytical frameworks (Porter's Five Forces, SWOT, Technology Adoption Lifecycle)
- Platform-specific optimization for deep_prompt type
- Configurable research depth
---
## Next Steps
After research:
1. **Product Brief** - Capture strategic vision informed by research
2. **PRD** - Use findings as context for requirements
3. **Architecture** - Use technical research in ADRs
---
## Tips
- Use market research early for new products
- Technical research helps with architecture decisions
- Competitive research informs positioning
- Domain research is valuable for specialized industries
---
## Related
- [Run Brainstorming Session](./run-brainstorming-session.md) - Explore ideas before research
- [Create Product Brief](./create-product-brief.md) - Capture strategic vision
- [Create PRD](./create-prd.md) - Move to formal planning

148
docs/how-to/workflows/create-architecture.md Normal file
View File

@ -0,0 +1,148 @@
---
sidebar_label: Create Architecture
description: How to create system architecture using the BMad Method
---
# How to Create Architecture
Use the `architecture` workflow to make technical decisions explicit and prevent agent conflicts during implementation.
---
## When to Use This
- Multi-epic projects (BMad Method, Enterprise)
- Cross-cutting technical concerns
- Multiple agents implementing different parts
- Integration complexity exists
- Technology choices need alignment
---
## When to Skip This
- Quick Flow (simple changes)
- BMad Method Simple with straightforward tech stack
- Single epic with clear technical approach
---
## Prerequisites
- BMad Method installed
- Architect agent available
- PRD completed
---
## Steps
### 1. Load the Architect Agent
Start a fresh chat and load the Architect agent.
### 2. Run the Architecture Workflow
```
*create-architecture
```
### 3. Engage in Discovery
This is NOT a template filler. The architecture workflow:
1. **Discovers** technical needs through conversation
2. **Proposes** architectural options with trade-offs
3. **Documents** decisions that prevent agent conflicts
4. **Focuses** on decision points, not exhaustive documentation
### 4. Document Key Decisions
Work with the agent to create Architecture Decision Records (ADRs) for significant choices.
### 5. Review the Architecture
The agent produces a decision-focused architecture document.
---
## What You Get
An `architecture.md` document containing:
1. **Architecture Overview** - System context, principles, style
2. **System Architecture** - High-level diagram, component interactions
3. **Data Architecture** - Database design, state management, caching
4. **API Architecture** - API style (REST/GraphQL/gRPC), auth, versioning
5. **Frontend Architecture** - Framework, state management, components
6. **Integration Architecture** - Third-party integrations, messaging
7. **Security Architecture** - Auth/authorization, data protection
8. **Deployment Architecture** - CI/CD, environments, monitoring
9. **ADRs** - Key decisions with context, options, rationale
10. **FR/NFR-Specific Guidance** - Technical approach per requirement
11. **Standards and Conventions** - Directory structure, naming, testing
---
## ADR Format
```markdown
## ADR-001: Use GraphQL for All APIs
**Status:** Accepted | **Date:** 2025-11-02
**Context:** PRD requires flexible querying across multiple epics
**Decision:** Use GraphQL for all client-server communication
**Options Considered:**
1. REST - Familiar but requires multiple endpoints
2. GraphQL - Flexible querying, learning curve
3. gRPC - High performance, poor browser support
**Rationale:**
- PRD requires flexible data fetching (Epic 1, 3)
- Mobile app needs bandwidth optimization (Epic 2)
- Team has GraphQL experience
**Consequences:**
- Positive: Flexible querying, reduced versioning
- Negative: Caching complexity, N+1 query risk
- Mitigation: Use DataLoader for batching
```
---
## Example
E-commerce platform produces:
- Monolith + PostgreSQL + Redis + Next.js + GraphQL
- ADRs explaining each choice
- FR/NFR-specific implementation guidance
---
## Tips
- Focus on decisions that prevent agent conflicts
- Use ADRs for every significant technology choice
- Keep it practical - don't over-architect
- Architecture is living - update as you learn
---
## Next Steps
After architecture:
1. **Create Epics and Stories** - Work breakdown informed by architecture
2. **Implementation Readiness** - Gate check before Phase 4
---
## Related
- [Create PRD](./create-prd.md) - Requirements before architecture
- [Create Epics and Stories](./create-epics-and-stories.md) - Next step
- [Run Implementation Readiness](./run-implementation-readiness.md) - Gate check
- [Why Solutioning Matters](../../explanation/architecture/why-solutioning-matters.md)

137
docs/how-to/workflows/create-epics-and-stories.md Normal file
View File

@ -0,0 +1,137 @@
---
sidebar_label: Create Epics & Stories
description: How to break PRD requirements into epics and stories using BMad Method
---
# How to Create Epics and Stories
Use the `create-epics-and-stories` workflow to transform PRD requirements into bite-sized stories organized into deliverable epics.
---
## When to Use This
- After architecture workflow completes
- When PRD contains FRs/NFRs ready for implementation breakdown
- Before implementation-readiness gate check
---
## Prerequisites
- BMad Method installed
- PM agent available
- PRD completed
- Architecture completed
---
## Why After Architecture?
This workflow runs AFTER architecture because:
1. **Informed Story Sizing** - Architecture decisions affect story complexity
2. **Dependency Awareness** - Architecture reveals technical dependencies
3. **Technical Feasibility** - Stories can be properly scoped knowing the tech stack
4. **Consistency** - All stories align with documented architectural patterns
---
## Steps
### 1. Load the PM Agent
Start a fresh chat and load the PM agent.
### 2. Run the Workflow
```
*create-epics-and-stories
```
### 3. Provide Context
Point the agent to:
- Your PRD (FRs/NFRs)
- Your architecture document
- Optional: UX design artifacts
### 4. Review Epic Breakdown
The agent organizes requirements into logical epics with user stories.
### 5. Validate Story Quality
Ensure each story has:
- Clear acceptance criteria
- Appropriate priority
- Identified dependencies
- Technical notes from architecture
---
## What You Get
Epic files (one per epic) containing:
1. **Epic objective and scope**
2. **User stories with acceptance criteria**
3. **Story priorities** (P0/P1/P2/P3)
4. **Dependencies between stories**
5. **Technical notes** referencing architecture decisions
---
## Example
E-commerce PRD with FR-001 (User Registration), FR-002 (Product Catalog) produces:
- **Epic 1: User Management** (3 stories)
- Story 1.1: User registration form
- Story 1.2: Email verification
- Story 1.3: Login/logout
- **Epic 2: Product Display** (4 stories)
- Story 2.1: Product listing page
- Story 2.2: Product detail page
- Story 2.3: Search functionality
- Story 2.4: Category filtering
Each story references relevant ADRs from architecture.
---
## Story Priority Levels
| Priority | Meaning |
|----------|---------|
| **P0** | Critical - Must have for MVP |
| **P1** | High - Important for release |
| **P2** | Medium - Nice to have |
| **P3** | Low - Future consideration |
---
## Tips
- Keep stories small enough to complete in a session
- Ensure acceptance criteria are testable
- Document dependencies clearly
- Reference architecture decisions in technical notes
---
## Next Steps
After creating epics and stories:
1. **Implementation Readiness** - Validate alignment before Phase 4
2. **Sprint Planning** - Organize work for implementation
---
## Related
- [Create Architecture](./create-architecture.md) - Do this first
- [Run Implementation Readiness](./run-implementation-readiness.md) - Gate check
- [Run Sprint Planning](./run-sprint-planning.md) - Start implementation

131
docs/how-to/workflows/create-prd.md Normal file
View File

@ -0,0 +1,131 @@
---
sidebar_label: Create PRD
description: How to create a Product Requirements Document using the BMad Method
---
# How to Create a PRD
Use the `prd` workflow to create a strategic Product Requirements Document with Functional Requirements (FRs) and Non-Functional Requirements (NFRs).
---
## When to Use This
- Medium to large feature sets
- Multi-screen user experiences
- Complex business logic
- Multiple system integrations
- Phased delivery required
---
## Prerequisites
- BMad Method installed
- PM agent available
- Optional: Product brief from Phase 1
---
## Steps
### 1. Load the PM Agent
Start a fresh chat and load the PM agent.
### 2. Run the PRD Workflow
```
*create-prd
```
### 3. Provide Context
The workflow will:
- Load any existing product brief
- Ask about your project scope
- Gather requirements through conversation
### 4. Define Requirements
Work with the agent to define:
- Functional Requirements (FRs) - What the system should do
- Non-Functional Requirements (NFRs) - How well it should do it
### 5. Review the PRD
The agent produces a comprehensive PRD scaled to your project.
---
## What You Get
A `PRD.md` document containing:
- Executive summary
- Problem statement
- User personas
- Functional requirements (FRs)
- Non-functional requirements (NFRs)
- Success metrics
- Risks and assumptions
---
## Scale-Adaptive Structure
The PRD adapts to your project complexity:
| Scale | Pages | Focus |
|-------|-------|-------|
| **Light** | 10-15 | Focused FRs/NFRs, simplified analysis |
| **Standard** | 20-30 | Comprehensive FRs/NFRs, thorough analysis |
| **Comprehensive** | 30-50+ | Extensive FRs/NFRs, multi-phase, stakeholder analysis |
---
## V6 Improvement
In V6, the PRD focuses on **WHAT** to build (requirements). Epic and Stories are created **AFTER** architecture via the `create-epics-and-stories` workflow for better quality.
---
## Example
E-commerce checkout → PRD with:
- 15 FRs (user account, cart management, payment flow)
- 8 NFRs (performance, security, scalability)
---
## Best Practices
### 1. Do Product Brief First
Run product-brief from Phase 1 to kickstart the PRD for better results.
### 2. Focus on "What" Not "How"
Planning defines **what** to build and **why**. Leave **how** (technical design) to Phase 3 (Solutioning).
### 3. Document-Project First for Brownfield
Always run `document-project` before planning brownfield projects. AI agents need existing codebase context.
---
## Next Steps
After PRD:
1. **Create UX Design** (optional) - If UX is critical
2. **Create Architecture** - Technical design
3. **Create Epics and Stories** - After architecture
---
## Related
- [Create Product Brief](./create-product-brief.md) - Input for PRD
- [Create UX Design](./create-ux-design.md) - Optional UX workflow
- [Create Architecture](./create-architecture.md) - Next step after PRD

118
docs/how-to/workflows/create-product-brief.md Normal file
View File

@ -0,0 +1,118 @@
---
sidebar_label: Create Product Brief
description: How to create a product brief using the BMad Method
---
# How to Create a Product Brief
Use the `product-brief` workflow to define product vision and strategy through an interactive process.
---
## When to Use This
- Starting new product or major feature initiative
- Aligning stakeholders before detailed planning
- Transitioning from exploration to strategy
- Need executive-level product documentation
---
## Prerequisites
- BMad Method installed
- Analyst agent available
- Optional: Research documents from previous workflows
---
## Steps
### 1. Load the Analyst Agent
Start a fresh chat and load the Analyst agent.
### 2. Run the Product Brief Workflow
```
*product-brief
```
### 3. Answer the Interactive Questions
The workflow guides you through strategic product vision definition:
- What problem are you solving?
- Who are your target users?
- What makes this solution different?
- What's the MVP scope?
### 4. Review and Refine
The agent will draft sections and let you refine them interactively.
---
## What You Get
The `product-brief.md` document includes:
- **Executive summary** - High-level overview
- **Problem statement** - With evidence
- **Proposed solution** - And differentiators
- **Target users** - Segmented
- **MVP scope** - Ruthlessly defined
- **Financial impact** - And ROI
- **Strategic alignment** - With business goals
- **Risks and open questions** - Documented upfront
---
## Integration with Other Workflows
The product brief feeds directly into the PRD workflow:
| Analysis Output | Planning Input |
|-----------------|----------------|
| product-brief.md | **prd** workflow |
| market-research.md | **prd** context |
| technical-research.md | **architecture** (Phase 3) |
Planning workflows automatically load the product brief if it exists.
---
## Common Patterns
### Greenfield Software (Full Analysis)
```
1. brainstorm-project - explore approaches
2. research (market/technical/domain) - validate viability
3. product-brief - capture strategic vision
4. → Phase 2: prd
```
### Skip Analysis (Clear Requirements)
```
→ Phase 2: prd or tech-spec directly
```
---
## Tips
- Be specific about the problem you're solving
- Ruthlessly prioritize MVP scope
- Document assumptions and risks
- Use research findings as evidence
- This is recommended for greenfield projects
---
## Related
- [Run Brainstorming Session](./run-brainstorming-session.md) - Explore ideas first
- [Conduct Research](./conduct-research.md) - Validate ideas
- [Create PRD](./create-prd.md) - Next step after product brief

121
docs/how-to/workflows/create-story.md Normal file
View File

@ -0,0 +1,121 @@
---
sidebar_label: Create Story
description: How to create implementation-ready stories from epic backlog
---
# How to Create a Story
Use the `create-story` workflow to prepare the next story from the epic backlog for implementation.
---
## When to Use This
- Before implementing each story
- When moving to the next story in an epic
- After sprint-planning has been run
---
## Prerequisites
- BMad Method installed
- SM (Scrum Master) agent available
- Sprint-status.yaml created by sprint-planning
- Architecture and PRD available for context
---
## Steps
### 1. Load the SM Agent
Start a fresh chat and load the SM (Scrum Master) agent.
### 2. Run the Workflow
```
*create-story
```
### 3. Specify the Story
The agent will:
- Read the sprint-status.yaml
- Identify the next story to work on
- Or let you specify a particular story
### 4. Review the Story File
The agent creates a comprehensive story file ready for development.
---
## What You Get
A `story-[slug].md` file containing:
- Story objective and scope
- Acceptance criteria (specific, testable)
- Technical implementation notes
- References to architecture decisions
- Dependencies on other stories
- Definition of Done
---
## Story Content Sources
The create-story workflow pulls from:
- **PRD** - Requirements and acceptance criteria
- **Architecture** - Technical approach and ADRs
- **Epic file** - Story context and dependencies
- **Existing code** - Patterns to follow (brownfield)
---
## Example Output
```markdown
# Story 1.2: Email Verification
## Objective
Implement email verification flow for new user registrations.
## Acceptance Criteria
- [ ] User receives verification email within 30 seconds
- [ ] Email contains unique verification link
- [ ] Link expires after 24 hours
- [ ] User can request new verification email
## Technical Notes
- Use SendGrid API per ADR-003
- Store verification tokens in Redis per architecture
- Follow existing email template patterns in /templates
## Dependencies
- Story 1.1 (User Registration) - DONE ✅
## Definition of Done
- All acceptance criteria pass
- Tests written and passing
- Code review approved
```
---
## Tips
- Complete one story before creating the next
- Ensure dependencies are marked DONE before starting
- Review technical notes for architecture alignment
- Use the story file as context for dev-story
---
## Related
- [Run Sprint Planning](./run-sprint-planning.md) - Initialize tracking
- [Implement Story](./implement-story.md) - Next step
- [Run Code Review](./run-code-review.md) - After implementation

160
docs/how-to/workflows/create-tech-spec.md Normal file
View File

@ -0,0 +1,160 @@
---
sidebar_label: Create Tech Spec
description: How to create a technical specification using Quick Spec Flow
---
# How to Create a Tech Spec
Use the `tech-spec` workflow for Quick Flow projects to go directly from idea to implementation-ready specification.
---
## When to Use This
- Bug fixes and small enhancements
- Small features with clear scope (1-15 stories)
- Rapid prototyping
- Adding to existing brownfield codebase
- Quick Flow track projects
---
## Prerequisites
- BMad Method installed
- PM agent or Quick Flow Solo Dev agent available
- Project directory (can be empty for greenfield)
---
## Steps
### 1. Load the PM Agent
Start a fresh chat and load the PM agent (or Quick Flow Solo Dev agent).
### 2. Run the Tech Spec Workflow
```
*create-tech-spec
```
Or simply describe what you want to build:
```
I want to fix the login validation bug
```
### 3. Answer Discovery Questions
The workflow will ask:
- What problem are you solving?
- What's the scope of the change?
- Any specific constraints?
### 4. Review Detected Context
For brownfield projects, the agent will:
- Detect your project stack
- Analyze existing code patterns
- Detect test frameworks
- Ask: "Should I follow these existing conventions?"
### 5. Get Your Tech Spec
The agent generates a comprehensive tech-spec with ready-to-implement stories.
---
## What You Get
### tech-spec.md
- Problem statement and solution
- Detected framework versions and dependencies
- Brownfield code patterns (if applicable)
- Existing test patterns to follow
- Specific file paths to modify
- Complete implementation guidance
### Story Files
For single changes:
- `story-[slug].md` - Single user story ready for development
For small features:
- `epics.md` - Epic organization
- `story-[epic-slug]-1.md`, `story-[epic-slug]-2.md`, etc.
---
## Example: Bug Fix (Single Change)
**You:** "I want to fix the login validation bug that allows empty passwords"
**Agent:**
1. Asks clarifying questions about the issue
2. Detects your Node.js stack (Express 4.18.2, Jest for testing)
3. Analyzes existing UserService code patterns
4. Asks: "Should I follow your existing conventions?" → Yes
5. Generates tech-spec.md with specific file paths
6. Creates story-login-fix.md
**Total time:** 15-30 minutes (mostly implementation)
---
## Example: Small Feature (Multi-Story)
**You:** "I want to add OAuth social login (Google, GitHub)"
**Agent:**
1. Asks about feature scope
2. Detects your stack (Next.js 13.4, NextAuth.js already installed!)
3. Analyzes existing auth patterns
4. Confirms conventions
5. Generates:
- tech-spec.md (comprehensive implementation guide)
- epics.md (OAuth Integration epic)
- story-oauth-1.md (Backend OAuth setup)
- story-oauth-2.md (Frontend login buttons)
**Total time:** 1-3 hours (mostly implementation)
---
## Implementing After Tech Spec
```bash
# Single change:
# Load DEV agent and run dev-story
# Multi-story feature:
# Optional: Load SM agent and run sprint-planning
# Then: Load DEV agent and run dev-story for each story
```
---
## Tips
### Be Specific in Discovery
- ✅ "Fix email validation in UserService to allow plus-addressing"
- ❌ "Fix validation bug"
### Trust Convention Detection
If it detects your patterns correctly, say yes! It's faster than establishing new conventions.
### Keep Single Changes Atomic
If your "single change" needs 3+ files, it might be a multi-story feature. Let the workflow guide you.
---
## Related
- [Quick Flow](../../explanation/features/quick-flow.md) - Understanding Quick Spec Flow
- [Implement Story](./implement-story.md) - After tech spec
- [Create PRD](./create-prd.md) - For larger projects needing full BMad Method

118
docs/how-to/workflows/create-ux-design.md Normal file
View File

@ -0,0 +1,118 @@
---
sidebar_label: Create UX Design
description: How to create UX specifications using the BMad Method
---
# How to Create a UX Design
Use the `create-ux-design` workflow to create UX specifications for projects where user experience is a primary differentiator.
---
## When to Use This
- UX is primary competitive advantage
- Complex user workflows needing design thinking
- Innovative interaction patterns
- Design system creation
- Accessibility-critical experiences
---
## When to Skip This
- Simple CRUD interfaces
- Internal tools with standard patterns
- Changes to existing screens you're happy with
- Quick Flow projects
---
## Prerequisites
- BMad Method installed
- UX Designer agent available
- PRD completed
---
## Steps
### 1. Load the UX Designer Agent
Start a fresh chat and load the UX Designer agent.
### 2. Run the UX Design Workflow
```
*create-ux-design
```
### 3. Provide Context
Point the agent to your PRD and describe:
- Key user journeys
- UX priorities
- Any existing design patterns
### 4. Collaborate on Design
The workflow uses a collaborative approach:
1. **Visual exploration** - Generate multiple options
2. **Informed decisions** - Evaluate with user needs
3. **Collaborative design** - Refine iteratively
4. **Living documentation** - Evolves with project
### 5. Review the UX Spec
The agent produces comprehensive UX documentation.
---
## What You Get
The `ux-spec.md` document includes:
- User journeys
- Wireframes and mockups
- Interaction specifications
- Design system (components, patterns, tokens)
- Epic breakdown (UX stories)
---
## Example
Dashboard redesign produces:
- Card-based layout with split-pane toggle
- 5 card components
- 12 color tokens
- Responsive grid
- 3 epics (Layout, Visualization, Accessibility)
---
## Integration
The UX spec feeds into:
- PRD updates
- Epic and story creation
- Architecture decisions (Phase 3)
---
## Tips
- Focus on user problems, not solutions first
- Generate multiple options before deciding
- Consider accessibility from the start
- Document component reusability
---
## Related
- [Create PRD](./create-prd.md) - Create requirements first
- [Create Architecture](./create-architecture.md) - Technical design
- [Create Epics and Stories](./create-epics-and-stories.md) - Work breakdown

128
docs/how-to/workflows/implement-story.md Normal file
View File

@ -0,0 +1,128 @@
---
sidebar_label: Implement Story
description: How to implement a story using the dev-story workflow
---
# How to Implement a Story
Use the `dev-story` workflow to implement a story with tests following the architecture and conventions.
---
## When to Use This
- After create-story has prepared the story file
- When ready to write code for a story
- Story dependencies are marked DONE
---
## Prerequisites
- BMad Method installed
- DEV agent available
- Story file created by create-story
- Architecture and tech-spec available for context
---
## Steps
### 1. Load the DEV Agent
Start a fresh chat and load the DEV agent.
### 2. Run the Workflow
```
*dev-story
```
### 3. Provide Story Context
Point the agent to the story file created by create-story.
### 4. Implement with Guidance
The DEV agent:
- Reads the story file and acceptance criteria
- References architecture decisions
- Follows existing code patterns
- Implements with tests
### 5. Complete Implementation
Work with the agent until all acceptance criteria are met.
---
## What Happens
The dev-story workflow:
1. **Reads context** - Story file, architecture, existing patterns
2. **Plans implementation** - Identifies files to create/modify
3. **Writes code** - Following conventions and patterns
4. **Writes tests** - Unit, integration, or E2E as appropriate
5. **Validates** - Runs tests and checks acceptance criteria
---
## Key Principles
### One Story at a Time
Complete each story's full lifecycle before starting the next. This prevents context switching and ensures quality.
### Follow Architecture
The DEV agent references:
- ADRs for technology decisions
- Standards for naming and structure
- Existing patterns in the codebase
### Write Tests
Every story includes appropriate tests:
- Unit tests for business logic
- Integration tests for API endpoints
- E2E tests for critical flows
---
## After Implementation
1. **Update sprint-status.yaml** - Mark story as READY FOR REVIEW
2. **Run code-review** - Quality assurance
3. **Address feedback** - If code review finds issues
4. **Mark DONE** - After code review passes
---
## Tips
- Keep the story file open for reference
- Ask the agent to explain decisions
- Run tests frequently during implementation
- Don't skip tests for "simple" changes
---
## Troubleshooting
**Q: Story needs significant changes mid-implementation?**
A: Run `correct-course` to analyze impact and route appropriately.
**Q: Can I work on multiple stories in parallel?**
A: Not recommended. Complete one story's full lifecycle first.
**Q: What if implementation reveals the story is too large?**
A: Split the story and document the change.
---
## Related
- [Create Story](./create-story.md) - Prepare the story first
- [Run Code Review](./run-code-review.md) - After implementation
- [Run Sprint Planning](./run-sprint-planning.md) - Sprint organization

95
docs/how-to/workflows/run-brainstorming-session.md Normal file
View File

@ -0,0 +1,95 @@
---
sidebar_label: Run Brainstorming
description: How to run a brainstorming session using the BMad Method
---
# How to Run a Brainstorming Session
Use the `brainstorm-project` workflow to explore solution approaches through parallel ideation tracks.
---
## When to Use This
- Very vague or seed kernel of an idea that needs exploration
- Consider alternatives or enhancements to an idea
- See your idea from different angles and viewpoints
- No idea what you want to build, but want to find some inspiration
---
## Prerequisites
- BMad Method installed
- Analyst agent available
---
## Steps
### 1. Load the Analyst Agent
Start a fresh chat and load the Analyst agent.
### 2. Run the Brainstorm Workflow
```
*brainstorm-project
```
### 3. Describe Your Idea
Tell the agent about your project idea, even if it's vague:
- "I want to build something that helps developers manage their context"
- "I have a game idea about resource management"
- "I need a tool for my team but I'm not sure what exactly"
### 4. Explore the Tracks
The workflow generates solution approaches through parallel ideation tracks:
- **Architecture track** - Technical approaches and patterns
- **UX track** - User experience possibilities
- **Integration track** - How it connects with other systems
- **Value track** - Business value and differentiation
### 5. Evaluate Options
Review the generated options with rationale for each approach.
---
## What You Get
- Multiple solution approaches with trade-offs
- Different architectural options
- UX and integration considerations
- Clear rationale for each direction
---
## Next Steps
After brainstorming:
1. **Research** - Validate ideas with market/technical research
2. **Product Brief** - Capture strategic vision
3. **PRD** - Move to formal planning
---
## Tips
- Don't worry about having a fully formed idea
- Let the agent guide the exploration
- Consider multiple tracks before deciding
- Use outputs as input for product-brief workflow
---
## Related
- [Conduct Research](./conduct-research.md) - Validate your ideas
- [Create Product Brief](./create-product-brief.md) - Capture strategic vision
- [Create PRD](./create-prd.md) - Move to formal planning

142
docs/how-to/workflows/run-code-review.md Normal file
View File

@ -0,0 +1,142 @@
---
sidebar_label: Run Code Review
description: How to run code review for quality assurance
---
# How to Run Code Review
Use the `code-review` workflow to perform a thorough quality review of implemented code.
---
## When to Use This
- After dev-story completes implementation
- Before marking a story as DONE
- Every story goes through code review - no exceptions
---
## Prerequisites
- BMad Method installed
- DEV agent available
- Story implementation complete
- Tests written and passing
---
## Steps
### 1. Load the DEV Agent
Start a fresh chat (or continue from dev-story) and load the DEV agent.
### 2. Run the Workflow
```
*code-review
```
### 3. Provide Context
Point the agent to:
- The story file
- Files changed during implementation
- Test files
### 4. Review Findings
The agent performs a senior developer code review and reports findings.
### 5. Address Issues
If issues are found:
1. Fix issues using dev-story
2. Re-run tests
3. Run code-review again
---
## What Gets Reviewed
The code review checks:
### Code Quality
- Clean, readable code
- Appropriate abstractions
- No code smells
- Proper error handling
### Architecture Alignment
- Follows ADRs and architecture decisions
- Consistent with existing patterns
- Proper separation of concerns
### Testing
- Adequate test coverage
- Tests are meaningful (not just for coverage)
- Edge cases handled
- Tests follow project patterns
### Security
- No hardcoded secrets
- Input validation
- Authentication/authorization proper
- No common vulnerabilities
### Performance
- No obvious performance issues
- Appropriate data structures
- Efficient queries
---
## Review Outcomes
### ✅ Approved
- Code meets quality standards
- Tests pass
- **Action:** Mark story as DONE in sprint-status.yaml
### 🔧 Changes Requested
- Issues identified that need fixing
- **Action:** Fix issues in dev-story, then re-run code-review
---
## Quality Gates
Every story goes through code-review before being marked done. This ensures:
- Consistent code quality
- Architecture adherence
- Test coverage
- Security review
---
## Tips
- Don't skip code review for "simple" changes
- Address all findings, not just critical ones
- Use findings as learning opportunities
- Re-run review after fixes
---
## After Code Review
1. **If approved:** Update sprint-status.yaml to mark story DONE
2. **If changes requested:** Fix issues and re-run review
3. **Move to next story:** Run create-story for the next item
---
## Related
- [Implement Story](./implement-story.md) - Before code review
- [Create Story](./create-story.md) - Move to next story
- [Run Sprint Planning](./run-sprint-planning.md) - Sprint organization

163
docs/how-to/workflows/run-implementation-readiness.md Normal file
View File

@ -0,0 +1,163 @@
---
sidebar_label: Run Implementation Readiness
description: How to validate planning and solutioning before implementation
---
# How to Run Implementation Readiness
Use the `implementation-readiness` workflow to validate that planning and solutioning are complete and aligned before Phase 4 implementation.
---
## When to Use This
- **Always** before Phase 4 for BMad Method and Enterprise projects
- After create-epics-and-stories workflow completes
- Before sprint-planning workflow
- When stakeholders request readiness check
---
## When to Skip This
- Quick Flow (no solutioning phase)
- BMad Method Simple (no gate check required)
---
## Prerequisites
- BMad Method installed
- Architect agent available
- PRD, Architecture, and Epics completed
---
## Steps
### 1. Load the Architect Agent
Start a fresh chat and load the Architect agent.
### 2. Run the Workflow
```
*implementation-readiness
```
### 3. Let the Agent Validate
The workflow systematically checks:
- PRD completeness
- Architecture completeness
- Epic/Story completeness
- Alignment between all documents
### 4. Review the Gate Decision
The agent produces a gate decision with rationale.
---
## Gate Decision Outcomes
### ✅ PASS
- All critical criteria met
- Minor gaps acceptable with documented plan
- **Action:** Proceed to Phase 4
### ⚠️ CONCERNS
- Some criteria not met but not blockers
- Gaps identified with clear resolution path
- **Action:** Proceed with caution, address gaps in parallel
### ❌ FAIL
- Critical gaps or contradictions
- Architecture missing key decisions
- Epics conflict with PRD/architecture
- **Action:** BLOCK Phase 4, resolve issues first
---
## What Gets Checked
### PRD/GDD Completeness
- Problem statement clear and evidence-based
- Success metrics defined
- User personas identified
- Functional requirements (FRs) complete
- Non-functional requirements (NFRs) specified
- Risks and assumptions documented
### Architecture Completeness
- System architecture defined
- Data architecture specified
- API architecture decided
- Key ADRs documented
- Security architecture addressed
- FR/NFR-specific guidance provided
- Standards and conventions defined
### Epic/Story Completeness
- All PRD features mapped to stories
- Stories have acceptance criteria
- Stories prioritized (P0/P1/P2/P3)
- Dependencies identified
- Story sequencing logical
### Alignment Checks
- Architecture addresses all PRD FRs/NFRs
- Epics align with architecture decisions
- No contradictions between epics
- NFRs have technical approach
- Integration points clear
---
## What You Get
An `implementation-readiness.md` document containing:
1. **Executive Summary** (PASS/CONCERNS/FAIL)
2. **Completeness Assessment** (scores for PRD, Architecture, Epics)
3. **Alignment Assessment** (PRD↔Architecture, Architecture↔Epics)
4. **Quality Assessment** (story quality, dependencies, risks)
5. **Gaps and Recommendations** (critical/minor gaps, remediation)
6. **Gate Decision** with rationale
7. **Next Steps**
---
## Example
E-commerce platform → CONCERNS ⚠️
**Gaps identified:**
- Missing security architecture section
- Undefined payment gateway
**Recommendation:**
- Complete security section
- Add payment gateway ADR
**Action:** Proceed with caution, address before payment epic.
---
## Tips
- Run this before every Phase 4 start
- Take FAIL decisions seriously - fix issues first
- Use CONCERNS as a checklist for parallel work
- Document why you proceed despite concerns
---
## Related
- [Create Architecture](./create-architecture.md) - Architecture workflow
- [Create Epics and Stories](./create-epics-and-stories.md) - Work breakdown
- [Run Sprint Planning](./run-sprint-planning.md) - Start implementation

112
docs/how-to/workflows/run-sprint-planning.md Normal file
View File

@ -0,0 +1,112 @@
---
sidebar_label: Run Sprint Planning
description: How to initialize sprint tracking for implementation
---
# How to Run Sprint Planning
Use the `sprint-planning` workflow to initialize the sprint tracking file and organize work for implementation.
---
## When to Use This
- Once at the start of Phase 4 (Implementation)
- After implementation-readiness gate passes
- When starting a new sprint cycle
---
## Prerequisites
- BMad Method installed
- SM (Scrum Master) agent available
- Epic files created from `create-epics-and-stories`
- Implementation-readiness passed (for BMad Method/Enterprise)
---
## Steps
### 1. Load the SM Agent
Start a fresh chat and load the SM (Scrum Master) agent.
### 2. Run the Workflow
```
*sprint-planning
```
### 3. Provide Context
Point the agent to your epic files created during Phase 3.
### 4. Review Sprint Organization
The agent organizes stories into the sprint tracking file.
---
## What You Get
A `sprint-status.yaml` file containing:
- All epics with their stories
- Story status tracking (TODO, IN PROGRESS, READY FOR REVIEW, DONE)
- Dependencies between stories
- Priority ordering
---
## Story Lifecycle States
Stories move through these states in the sprint status file:
| State | Description |
|-------|-------------|
| **TODO** | Story identified but not started |
| **IN PROGRESS** | Story being implemented |
| **READY FOR REVIEW** | Implementation complete, awaiting code review |
| **DONE** | Accepted and complete |
---
## Typical Sprint Flow
### Sprint 0 (Planning Phase)
- Complete Phases 1-3
- PRD/GDD + Architecture complete
- Epics+Stories created via create-epics-and-stories
### Sprint 1+ (Implementation Phase)
**Start of Phase 4:**
1. SM runs `sprint-planning` (once)
**Per Story (repeat until epic complete):**
1. SM runs `create-story`
2. DEV runs `dev-story`
3. DEV runs `code-review`
4. Update sprint-status.yaml
**After Epic Complete:**
- SM runs `retrospective`
- Move to next epic
---
## Tips
- Run sprint-planning only once at Phase 4 start
- Use `sprint-status` during Phase 4 to check current state
- Keep the sprint-status.yaml file as single source of truth
- Update story status after each stage
---
## Related
- [Create Story](./create-story.md) - Prepare stories for implementation
- [Implement Story](./implement-story.md) - Dev workflow
- [Run Code Review](./run-code-review.md) - Quality assurance

129
docs/how-to/workflows/run-test-design.md Normal file
View File

@ -0,0 +1,129 @@
---
sidebar_label: Run Test Design
description: How to create comprehensive test plans using TEA's test-design workflow
---
# How to Run Test Design
Use TEA's `*test-design` workflow to create comprehensive test plans with risk assessment and coverage strategies.
---
## When to Use This
**System-level (Phase 3):**
- After architecture is complete
- Before implementation-readiness gate
- To validate architecture testability
**Epic-level (Phase 4):**
- At the start of each epic
- Before implementing stories in the epic
- To identify epic-specific testing needs
---
## Prerequisites
- BMad Method installed
- TEA agent available
- For system-level: Architecture document complete
- For epic-level: Epic defined with stories
---
## Steps
### 1. Load the TEA Agent
Start a fresh chat and load the TEA (Test Architect) agent.
### 2. Run the Test Design Workflow
```
*test-design
```
### 3. Specify the Mode
TEA will ask if you want:
- **System-level** - For architecture testability review (Phase 3)
- **Epic-level** - For epic-specific test planning (Phase 4)
### 4. Provide Context
For system-level:
- Point to your architecture document
- Reference any ADRs (Architecture Decision Records)
For epic-level:
- Specify which epic you're planning
- Reference the epic file with stories
### 5. Review the Output
TEA generates a comprehensive test design document.
---
## What You Get
### System-Level Output (`test-design-system.md`)
- Testability review of architecture
- ADR → test mapping
- Architecturally Significant Requirements (ASRs)
- Environment needs
- Test infrastructure recommendations
### Epic-Level Output (`test-design-epic-N.md`)
- Risk assessment for the epic
- Test priorities
- Coverage plan
- Regression hotspots (for brownfield)
- Integration risks
- Mitigation strategies
---
## Test Design for Different Tracks
### Greenfield - BMad Method
| Stage | Test Design Focus |
|-------|-------------------|
| Phase 3 | System-level testability review |
| Phase 4 | Per-epic risk assessment and test plan |
### Brownfield - BMad Method/Enterprise
| Stage | Test Design Focus |
|-------|-------------------|
| Phase 3 | System-level + existing test baseline |
| Phase 4 | Regression hotspots, integration risks |
### Enterprise
| Stage | Test Design Focus |
|-------|-------------------|
| Phase 3 | Compliance-aware testability |
| Phase 4 | Security/performance/compliance focus |
---
## Tips
- Run system-level test-design right after architecture
- Run epic-level test-design at the start of each epic
- Update test design if ADRs change
- Use the output to guide `*atdd` and `*automate` workflows
---
## Related
- [TEA Overview](../../explanation/features/tea-overview.md) - Understanding the Test Architect
- [Setup Test Framework](./setup-test-framework.md) - Setting up testing infrastructure
- [Create Architecture](./create-architecture.md) - Architecture workflow

118
docs/how-to/workflows/setup-party-mode.md Normal file
View File

@ -0,0 +1,118 @@
---
sidebar_label: Setup Party Mode
description: How to set up and use Party Mode for multi-agent collaboration
---
# How to Set Up Party Mode
Use Party Mode to orchestrate dynamic multi-agent conversations with your entire BMAD team.
---
## When to Use This
- Exploring complex topics that benefit from diverse expert perspectives
- Brainstorming with agents who can build on each other's ideas
- Getting comprehensive views across multiple domains
- Strategic decisions with trade-offs
---
## Prerequisites
- BMad Method installed with multiple agents
- Any agent loaded that supports party mode
---
## Steps
### 1. Load Any Agent
Start with any agent that supports party mode (most do).
### 2. Start Party Mode
```
*party-mode
```
Or use the full path:
```
/bmad:core:workflows:party-mode
```
### 3. Introduce Your Topic
Present a topic or question for the group to discuss:
```
I'm trying to decide between a monolithic architecture
and microservices for our new platform.
```
### 4. Engage with the Discussion
The facilitator will:
- Select 2-3 most relevant agents based on expertise
- Let agents respond in character
- Enable natural cross-talk and debate
- Continue until you choose to exit
### 5. Exit When Ready
Type "exit" or "done" to conclude the session. Participating agents will say personalized farewells.
---
## What Happens
1. **Agent Roster** - Party Mode loads your complete agent roster
2. **Introduction** - Available team members are introduced
3. **Topic Analysis** - The facilitator analyzes your topic
4. **Agent Selection** - 2-3 most relevant agents are selected
5. **Discussion** - Agents respond, reference each other, engage in cross-talk
6. **Exit** - Session concludes with farewells
---
## Example Party Compositions
### Product Strategy
- PM + Innovation Strategist (CIS) + Analyst
### Technical Design
- Architect + Creative Problem Solver (CIS) + Game Architect
### User Experience
- UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
### Quality Assessment
- TEA + DEV + Architect
---
## Key Features
- **Intelligent agent selection** - Selects based on expertise needed
- **Authentic personalities** - Each agent maintains their unique voice
- **Natural cross-talk** - Agents reference and build on each other
- **Optional TTS** - Voice configurations for each agent
- **Graceful exit** - Personalized farewells
---
## Tips
- Be specific about your topic for better agent selection
- Let the conversation flow naturally
- Ask follow-up questions to go deeper
- Take notes on key insights
- Use for strategic decisions, not routine tasks
---
## Related
- [Party Mode](../../explanation/features/party-mode.md) - Understanding Party Mode
- [Agent Roles](../../explanation/core-concepts/agent-roles.md) - Available agents

114
docs/how-to/workflows/setup-test-framework.md Normal file
View File

@ -0,0 +1,114 @@
---
sidebar_label: Setup Test Framework
description: How to set up a production-ready test framework using TEA
---
# How to Set Up a Test Framework
Use TEA's `*framework` workflow to scaffold a production-ready test framework for your project.
---
## When to Use This
- No existing test framework in your project
- Current test setup isn't production-ready
- Starting a new project that needs testing infrastructure
- Phase 3 (Solutioning) after architecture is complete
---
## Prerequisites
- BMad Method installed
- Architecture completed (or at least tech stack decided)
- TEA agent available
---
## Steps
### 1. Load the TEA Agent
Start a fresh chat and load the TEA (Test Architect) agent.
### 2. Run the Framework Workflow
```
*framework
```
### 3. Answer TEA's Questions
TEA will ask about:
- Your tech stack (React, Node, etc.)
- Preferred test framework (Playwright, Cypress, Jest)
- Testing scope (E2E, integration, unit)
- CI/CD platform (GitHub Actions, etc.)
### 4. Review Generated Output
TEA generates:
- **Test scaffold** - Directory structure and config files
- **Sample specs** - Example tests following best practices
- **`.env.example`** - Environment variable template
- **`.nvmrc`** - Node version specification
- **README updates** - Testing documentation
---
## What You Get
```
tests/
├── e2e/
│ ├── example.spec.ts
│ └── fixtures/
├── integration/
├── unit/
├── playwright.config.ts # or cypress.config.ts
└── README.md
```
---
## Optional: Playwright Utils Integration
TEA can integrate with `@seontechnologies/playwright-utils` for advanced fixtures:
```bash
npm install -D @seontechnologies/playwright-utils
```
Enable during BMad installation or set `tea_use_playwright_utils: true` in config.
**Utilities available:** api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor
---
## Optional: MCP Enhancements
TEA can use Playwright MCP servers for enhanced capabilities:
- `playwright` - Browser automation
- `playwright-test` - Test runner with failure analysis
Configure in your IDE's MCP settings.
---
## Tips
- Run `*framework` only once per repository
- Run after architecture is complete so framework aligns with tech stack
- Follow up with `*ci` to set up CI/CD pipeline
---
## Related
- [TEA Overview](../../explanation/features/tea-overview.md) - Understanding the Test Architect
- [Run Test Design](./run-test-design.md) - Creating test plans
- [Create Architecture](./create-architecture.md) - Architecture workflow

60
docs/modules/bmb-bmad-builder/index.md
View File

@ -1,60 +0,0 @@
# BMB Module Documentation
Create custom agents, workflows, and modules for BMAD.
## Quick Start
- **[Agent Creation Guide](../../tutorials/advanced/create-custom-agent.md)** - Step-by-step guide to building your first agent
- **[Understanding Agent Types](./understanding-agent-types.md)** - Learn the differences between Simple and Expert agents
## Agent Architecture
Comprehensive guides for each agent type (choose based on use case):
- [Understanding Agent Types](./understanding-agent-types.md) - **START HERE** - Architecture vs capability, "The Same Agent, Three Ways"
- [Simple Agent Architecture](./simple-agent-architecture.md) - Self-contained, optimized, personality-driven
- [Expert Agent Architecture](./expert-agent-architecture.md) - Memory, sidecar files, domain restrictions
- Module Agent Architecture _(TODO)_ - Workflow integration, professional tools
## Agent Design Patterns
- [Agent Menu Patterns](./agent-menu-patterns.md) - Menu handlers, triggers, prompts, organization
- [Agent Compilation](./agent-compilation.md) - What compiler auto-injects (AVOID DUPLICATION)
## Reference Examples
Production-ready examples in [bmb/reference/agents/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents):
**Simple Agents** ([simple-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/simple-examples))
- [commit-poet.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml) - Commit message artisan with style customization
**Expert Agents** ([expert-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples))
- [journal-keeper/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper) - Personal journal companion with memory and pattern recognition
**Module Agents** ([module-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/module-examples))
- [security-engineer.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml) - BMM security specialist with threat modeling
- [trend-analyst.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml) - CIS trend intelligence expert
## Installation Guide
For installing standalone simple and expert agents, see:
- [Custom Agent Installation](/docs/modules/bmb-bmad-builder/custom-content-installation.md)
## Key Concepts
### YAML to XML Compilation
Agents are authored in YAML with Handlebars templating. The compiler auto-injects:
1. **Frontmatter** - Name and description from metadata
2. **Activation Block** - Steps, menu handlers, rules (YOU don't write this)
3. **Menu Enhancement** - `*help` and `*exit` commands added automatically
4. **Trigger Prefixing** - Your triggers auto-prefixed with `*`
**Critical:** See [Agent Compilation](./agent-compilation.md) to avoid duplicating auto-injected content.
Source: `tools/cli/lib/agent/compiler.js`

175
docs/modules/bmgd-bmad-game-dev/index.md
View File

@ -1,175 +0,0 @@
# BMGD Documentation
Complete guides for the BMad Game Development Module (BMGD) - AI-powered workflows for game design and development that adapt to your project's needs.
---
## Getting Started
**New to BMGD?** Start here:
- **[Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)** - Get started building your first game
- Installation and setup
- Understanding the game development phases
- Running your first workflows
- Agent-based development flow
**Quick Path:** Install BMGD module → Game Brief → GDD → Architecture → Build
---
## Core Concepts
Understanding how BMGD works:
- **[Agents Guide](../../reference/agents/index.md)** - Complete reference for game development agents
- Game Designer, Game Developer, Game Architect, Game Scrum Master, Game QA, Game Solo Dev
- Agent roles and when to use them
- Agent workflows and menus
- **[Workflows Guide](../../reference/workflows/index.md)** - Complete workflow reference
- Phase 1: Preproduction (Brainstorm, Game Brief)
- Phase 2: Design (GDD, Narrative)
- Phase 3: Technical (Architecture)
- Phase 4: Production (Sprint-based development)
- **[Game Types Guide](../../explanation/game-dev/game-types.md)** - Selecting and using game type templates
- 24 supported game types
- Genre-specific GDD sections
- Hybrid game type handling
- **[Quick-Flow Guide](../../how-to/workflows/bmgd-quick-flow.md)** - Fast-track workflows for rapid development
- Quick-Prototype for testing ideas
- Quick-Dev for flexible implementation
- When to use quick-flow vs full BMGD
---
## Quick References
Essential reference materials:
- **[Glossary](../../reference/glossary/index.md)** - Key game development terminology
---
## Choose Your Path
### I need to...
**Start a new game project**
→ Start with [Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)
→ Run `brainstorm-game` for ideation
→ Create a Game Brief with `create-brief`
**Design my game**
→ Create a GDD with `create-gdd`
→ If story-heavy, add Narrative Design with `create-narrative`
**Plan the technical architecture**
→ Run `create-architecture` with the Game Architect
**Build my game**
→ Use Phase 4 production workflows
→ Follow the sprint-based development cycle
**Quickly test an idea or implement a feature**
→ Use [Quick-Flow](../../how-to/workflows/bmgd-quick-flow.md) for rapid prototyping and development
→ `quick-prototype` to test mechanics, `quick-dev` to implement
**Set up testing and QA**
→ Use Game QA agent for test framework setup
→ Run `test-framework` to initialize testing for Unity/Unreal/Godot
→ Use `test-design` to create test scenarios
→ Plan playtests with `playtest-plan`
**Understand game type templates**
→ See [Game Types Guide](../../explanation/game-dev/game-types.md)
---
## Game Development Phases
BMGD follows four phases aligned with game development:
![BMGD Workflow Overview](./workflow-overview.jpg)
### Phase 1: Preproduction
- **Brainstorm Game** - Ideation with game-specific techniques
- **Game Brief** - Capture vision, market, and fundamentals
### Phase 2: Design
- **GDD (Game Design Document)** - Comprehensive game design
- **Narrative Design** - Story, characters, world (for story-driven games)
### Phase 3: Technical
- **Game Architecture** - Engine, systems, patterns, structure
### Phase 4: Production
- **Sprint Planning** - Epic and story management
- **Story Development** - Implementation workflow
- **Code Review** - Quality assurance
- **Testing** - Automated tests, playtesting, performance
- **Retrospective** - Continuous improvement
---
## BMGD vs BMM
BMGD extends BMM with game-specific capabilities:
| Aspect | BMM | BMGD |
| -------------- | ------------------------------------- | ------------------------------------------------------------------------ |
| **Focus** | General software | Game development |
| **Agents** | PM, Architect, Dev, SM, TEA, Solo Dev | Game Designer, Game Dev, Game Architect, Game SM, Game QA, Game Solo Dev |
| **Planning** | PRD, Tech Spec | Game Brief, GDD |
| **Types** | N/A | 24 game type templates |
| **Narrative** | N/A | Full narrative workflow |
| **Testing** | Web-focused testarch | Engine-specific (Unity, Unreal, Godot) |
| **Production** | Inherited from BMM | BMM workflows with game overrides |
BMGD production workflows inherit from BMM and add game-specific checklists and templates.
---
## Documentation Map
```
BMGD Documentation
├── README.md (this file)
├── quick-start.md # Getting started
├── agents-guide.md # Agent reference
├── workflows-guide.md # Workflow reference
├── quick-flow-guide.md # Rapid prototyping and development
├── game-types-guide.md # Game type templates
├── glossary.md # Terminology
```
---
## External Resources
### Community and Support
- **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help from the community
- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
- **[YouTube Channel](https://www.youtube.com/@BMadCode)** - Video tutorials
### Related Documentation
- **[BMM Documentation](../bmm/index.md)** - Core BMad Method documentation
## Tips for Using This Documentation
1. **Start with Quick Start** if you're new to BMGD
2. **Check Game Types Guide** when creating your GDD
3. **Reference Glossary** for game development terminology
4. **Use Troubleshooting** when you encounter issues
---
**Ready to make games?** → [Start with the Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)

506
docs/modules/bmm-bmad-method/bmad-quick-flow.md
View File

@ -1,506 +0,0 @@
# BMAD Quick Flow
**Track:** Quick Flow
**Primary Agent:** Quick Flow Solo Dev (Barry)
**Ideal For:** Bug fixes, small features, rapid prototyping
---
## Overview
BMAD Quick Flow is the fastest path from idea to production in the BMAD Method ecosystem. It's a streamlined 3-step process designed for rapid spec driven development without sacrificing quality. Perfect for experienced teams who need to move fast or for smaller features or 1 off efforts that don't require extensive planning.
### When to Use Quick Flow
**Perfect For:**
- Bug fixes and patches
- Small feature additions
- Proof of concepts and prototypes
- Mid course corrections or additions of something missed in BMM full planning
- Performance optimizations
- API endpoint additions
- UI component enhancements
- Configuration changes
- Internal tools
**Not Recommended For:**
- Large-scale system redesigns
- Complex multi-team projects
- New product launches
- Projects requiring extensive UX design
- Enterprise-wide initiatives
- Mission-critical systems with compliance requirements
- Ideas with many 'moving pieces'
---
## The Quick Flow Process
Utilizing the Quick Flow Solo Dev, this one agent can do it all!
1. Create an (option) Technical Specification
2. Develop with Tests
3. AI Driven Code Review
That's it! Lets look at each step in more detail though.
### Step 1: Optional Technical Specification
The `create-tech-spec` workflow transforms requirements into implementation-ready specifications.
**Key Features:**
- Conversational spec engineering
- Automatic codebase pattern detection
- Context gathering from existing code
- Implementation-ready task breakdown
- Acceptance criteria definition
**Process Flow:**
1. **Problem Understanding**
- Greet user and gather requirements
- Ask clarifying questions about scope and constraints
- Check for existing project context
2. **Code Investigation (Brownfield)**
- Analyze existing codebase patterns
- Document tech stack and conventions
- Identify files to modify and dependencies
3. **Specification Generation**
- Create structured tech specification
- Define clear tasks and acceptance criteria
- Document technical decisions
- Include development context
4. **Review and Finalize**
- Present spec for validation
- Make adjustments as needed
- Save to sprint artifacts
**Output:** `{implementation_artifacts}/tech-spec-{slug}.md`
### Step 2: Development
The `quick-dev` workflow executes implementation with flexibility and speed.
**Two Execution Modes:**
**Mode A: Tech-Spec Driven**
```bash
# Execute from tech spec
quick-dev tech-spec-feature-x.md
```
- Loads and parses technical specification
- Extracts tasks, context, and acceptance criteria
- Executes all tasks in sequence
- Updates spec status on completion
**Mode B: Direct Instructions**
```bash
# Direct development commands
quick-dev "Add password reset to auth service"
quick-dev "Fix the memory leak in image processing"
```
- Accepts direct development instructions
- Offers optional planning step
- Executes immediately with minimal friction
**Development Process:**
1. **Context Loading**
- Load project context if available
- Understand patterns and conventions
- Identify relevant files and dependencies
2. **Implementation Loop**
For each task:
- Load relevant files and context
- Implement following established patterns
- Write appropriate tests
- Run and verify tests pass
- Mark task complete and continue
3. **Continuous Execution**
- Works through all tasks without stopping
- Handles failures by requesting guidance
- Ensures tests pass before continuing
4. **Verification**
- Confirms all tasks complete
- Validates acceptance criteria
- Updates tech spec status if used
### Step 3: Optional Code Review
The `code-review` workflow provides senior developer review of implemented code.
**When to Use:**
- Production-critical features
- Security-sensitive implementations
- Performance optimizations
- Team development scenarios
- Learning and knowledge transfer
**Review Process:**
1. Load story context and acceptance criteria
2. Analyze code implementation
3. Check against project patterns
4. Validate test coverage
5. Provide structured review notes
6. Suggest improvements if needed
---
## Quick Flow vs Other Tracks
| Aspect | Quick Flow | BMad Method | Enterprise Method |
| ----------------- | ---------------- | --------------- | ------------------ |
| **Planning** | Minimal/Optional | Structured | Comprehensive |
| **Documentation** | Essential only | Moderate | Extensive |
| **Team Size** | 1-2 developers | 3-7 specialists | 8+ enterprise team |
| **Timeline** | Hours to days | Weeks to months | Months to quarters |
| **Ceremony** | Minimal | Balanced | Full governance |
| **Flexibility** | High | Moderate | Structured |
| **Risk Profile** | Medium | Low | Very Low |
---
## Best Practices
### Before Starting Quick Flow
1. **Validate Track Selection**
- Is the feature small enough?
- Do you have clear requirements?
- Is the team comfortable with rapid development?
2. **Prepare Context**
- Have project documentation ready
- Know your codebase patterns
- Identify affected components upfront
3. **Set Clear Boundaries**
- Define in-scope and out-of-scope items
- Establish acceptance criteria
- Identify dependencies
### During Development
1. **Maintain Velocity**
- Don't over-engineer solutions
- Follow existing patterns
- Keep tests proportional to risk
2. **Stay Focused**
- Resist scope creep
- Handle edge cases later if possible
- Document decisions briefly
3. **Communicate Progress**
- Update task status regularly
- Flag blockers immediately
- Share learning with team
### After Completion
1. **Quality Gates**
- Ensure tests pass
- Verify acceptance criteria
- Consider optional code review
2. **Knowledge Transfer**
- Update relevant documentation
- Share key decisions
- Note any discovered patterns
3. **Production Readiness**
- Verify deployment requirements
- Check monitoring needs
- Plan rollback strategy
---
## Quick Flow Templates
### Tech Spec Template
```markdown
# Tech-Spec: {Feature Title}
**Created:** {date}
**Status:** Ready for Development
**Estimated Effort:** Small (1-2 days)
## Overview
### Problem Statement
{Clear description of what needs to be solved}
### Solution
{High-level approach to solving the problem}
### Scope (In/Out)
**In:** {What will be implemented}
**Out:** {Explicitly excluded items}
## Context for Development
### Codebase Patterns
{Key patterns to follow, conventions}
### Files to Reference
{List of relevant files and their purpose}
### Technical Decisions
{Important technical choices and rationale}
## Implementation Plan
### Tasks
- [ ] Task 1: {Specific implementation task}
- [ ] Task 2: {Specific implementation task}
- [ ] Task 3: {Testing and validation}
### Acceptance Criteria
- [ ] AC 1: {Given/When/Then format}
- [ ] AC 2: {Given/When/Then format}
## Additional Context
### Dependencies
{External dependencies or prerequisites}
### Testing Strategy
{How the feature will be tested}
### Notes
{Additional considerations}
```
### Quick Dev Commands
```bash
# From tech spec
quick-dev sprint-artifacts/tech-spec-user-auth.md
# Direct development
quick-dev "Add CORS middleware to API endpoints"
quick-dev "Fix null pointer exception in user service"
quick-dev "Optimize database query for user list"
# With optional planning
quick-dev "Implement file upload feature" --plan
```
---
## Integration with Other Workflows
### Upgrading Tracks
If a Quick Flow feature grows in complexity:
```mermaid
flowchart LR
QF[Quick Flow] --> CHECK{Complexity Increases?}
CHECK -->|Yes| UPGRADE[Upgrade to BMad Method]
CHECK -->|No| CONTINUE[Continue Quick Flow]
UPGRADE --> PRD[Create PRD]
PRD --> ARCH[Architecture Design]
ARCH --> STORIES[Create Epics/Stories]
STORIES --> SPRINT[Sprint Planning]
style QF fill:#e1f5fe
style UPGRADE fill:#fff3e0
style PRD fill:#f3e5f5
style ARCH fill:#e8f5e9
style STORIES fill:#f1f8e9
style SPRINT fill:#e0f2f1
```
### Using Party Mode
For complex Quick Flow challenges:
```bash
# Start Barry
/bmad:bmm:agents:quick-flow-solo-dev
# Begin party mode for collaborative problem-solving
party-mode
```
Party mode brings in relevant experts:
- **Architect** - For design decisions
- **Dev** - For implementation pairing
- **QA** - For test strategy
- **UX Designer** - For user experience
- **Analyst** - For requirements clarity
### Quality Assurance Integration
Quick Flow can integrate with TEA agent for automated testing:
- Test case generation
- Automated test execution
- Coverage analysis
- Test healing
---
## Common Quick Flow Scenarios
### Scenario 1: Bug Fix
```
Requirement: "Users can't reset passwords"
Process: Direct development (no spec needed)
Steps: Investigate → Fix → Test → Deploy
Time: 2-4 hours
```
### Scenario 2: Small Feature
```
Requirement: "Add export to CSV functionality"
Process: Tech spec → Development → Code review
Steps: Spec → Implement → Test → Review → Deploy
Time: 1-2 days
```
### Scenario 3: Performance Fix
```
Requirement: "Optimize slow product search query"
Process: Tech spec → Development → Review
Steps: Analysis → Optimize → Benchmark → Deploy
Time: 1 day
```
### Scenario 4: API Addition
```
Requirement: "Add webhook endpoints for integrations"
Process: Tech spec → Development → Review
Steps: Design → Implement → Document → Deploy
Time: 2-3 days
```
---
## Metrics and KPIs
Track these metrics to ensure Quick Flow effectiveness:
**Velocity Metrics:**
- Features completed per week
- Average cycle time (hours)
- Bug fix resolution time
- Code review turnaround
**Quality Metrics:**
- Defect escape rate
- Test coverage percentage
- Production incident rate
- Code review findings
**Team Metrics:**
- Developer satisfaction
- Knowledge sharing frequency
- Process adherence
- Autonomy index
---
## Troubleshooting Quick Flow
### Common Issues
**Issue: Scope creep during development**
**Solution:** Refer back to tech spec, explicitly document new requirements
**Issue: Unknown patterns or conventions**
**Solution:** Use party-mode to bring in architect or senior dev
**Issue: Testing bottleneck**
**Solution:** Leverage TEA agent for automated test generation
**Issue: Integration conflicts**
**Solution:** Document dependencies, coordinate with affected teams
### Emergency Procedures
**Production Hotfix:**
1. Create branch from production
2. Quick dev with minimal changes
3. Deploy to staging
4. Quick regression test
5. Deploy to production
6. Merge to main
**Critical Bug:**
1. Immediate investigation
2. Party-mode if unclear
3. Quick fix with rollback plan
4. Post-mortem documentation
---
## Related Documentation
- **[Quick Flow Solo Dev Agent](../../reference/agents/barry-quick-flow.md)** - Primary agent for Quick Flow
- **[Agents Guide](../../explanation/core-concepts/agent-roles.md)** - Complete agent reference
- **[Scale Adaptive System](./scale-adaptive-system.md)** - Track selection guidance
- **[Party Mode](../../explanation/features/party-mode.md)** - Multi-agent collaboration
- **[Workflow Implementation](../../how-to/workflows/run-sprint-planning.md)** - Implementation details
---
## FAQ
**Q: How do I know if my feature is too big for Quick Flow?**
A: If it requires more than 3-5 days of work, affects multiple systems significantly, or needs extensive UX design, consider the BMad Method track.
**Q: Can I switch from Quick Flow to BMad Method mid-development?**
A: Yes, you can upgrade. Create the missing artifacts (PRD, architecture) and transition to sprint-based development.
**Q: Is Quick Flow suitable for production-critical features?**
A: Yes, with code review. Quick Flow doesn't sacrifice quality, just ceremony.
**Q: How do I handle dependencies between Quick Flow features?**
A: Document dependencies clearly, consider batching related features, or upgrade to BMad Method for complex interdependencies.
**Q: Can junior developers use Quick Flow?**
A: Yes, but they may benefit from the structure of BMad Method. Quick Flow assumes familiarity with patterns and autonomy.
---
**Ready to ship fast?** → Start with `/bmad:bmm:agents:quick-flow-solo-dev`

540
docs/modules/bmm-bmad-method/faq.md
View File

@ -1,540 +0,0 @@
# BMM Frequently Asked Questions
Quick answers to common questions about the BMad Method Module.
---
## Table of Contents
- [Getting Started](#getting-started)
- [Choosing the Right Level](#choosing-the-right-level)
- [Workflows and Phases](#workflows-and-phases)
- [Planning Documents](#planning-documents)
- [Implementation](#implementation)
- [Brownfield Development](#brownfield-development)
- [Tools and Technical](#tools-and-technical)
---
## Getting Started
### Q: Do I always need to run workflow-init?
**A:** No, once you learn the flow you can go directly to workflows. However, workflow-init is helpful because it:
- Determines your project's appropriate level automatically
- Creates the tracking status file
- Routes you to the correct starting workflow
For experienced users: use the [Quick Reference](../../tutorials/getting-started/quick-start-bmm.md#quick-reference-agent-document-mapping) to go directly to the right agent/workflow.
### Q: Why do I need fresh chats for each workflow?
**A:** Context-intensive workflows (like brainstorming, PRD creation, architecture design) can cause AI hallucinations if run in sequence within the same chat. Starting fresh ensures the agent has maximum context capacity for each workflow. This is particularly important for:
- Planning workflows (PRD, architecture)
- Analysis workflows (brainstorming, research)
- Complex story implementation
Quick workflows like status checks can reuse chats safely.
### Q: Can I skip workflow-status and just start working?
**A:** Yes, if you already know your project level and which workflow comes next. workflow-status is mainly useful for:
- New projects (guides initial setup)
- When you're unsure what to do next
- After breaks in work (reminds you where you left off)
- Checking overall progress
### Q: What's the minimum I need to get started?
**A:** For the fastest path:
1. Install BMad Method: `npx bmad-method@alpha install`
2. For small changes: Load PM agent → run tech-spec → implement
3. For larger projects: Load PM agent → run prd → architect → implement
### Q: How do I know if I'm in Phase 1, 2, 3, or 4?
**A:** Check your `bmm-workflow-status.md` file (created by workflow-init). It shows your current phase and progress. If you don't have this file, you can also tell by what you're working on:
- **Phase 1** - Brainstorming, research, product brief (optional)
- **Phase 2** - Creating either a PRD or tech-spec (always required)
- **Phase 3** - Architecture design (Level 2-4 only)
- **Phase 4** - Actually writing code, implementing stories
---
## Choosing the Right Level
### Q: How do I know which level my project is?
**A:** Use workflow-init for automatic detection, or self-assess using these keywords:
- **Level 0:** "fix", "bug", "typo", "small change", "patch" → 1 story
- **Level 1:** "simple", "basic", "small feature", "add" → 2-10 stories
- **Level 2:** "dashboard", "several features", "admin panel" → 5-15 stories
- **Level 3:** "platform", "integration", "complex", "system" → 12-40 stories
- **Level 4:** "enterprise", "multi-tenant", "multiple products" → 40+ stories
When in doubt, start smaller. You can always run create-prd later if needed.
### Q: Can I change levels mid-project?
**A:** Yes! If you started at Level 1 but realize it's Level 2, you can run create-prd to add proper planning docs. The system is flexible - your initial level choice isn't permanent.
### Q: What if workflow-init suggests the wrong level?
**A:** You can override it! workflow-init suggests a level but always asks for confirmation. If you disagree, just say so and choose the level you think is appropriate. Trust your judgment.
### Q: Do I always need architecture for Level 2?
**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD created during planning.
### Q: What's the difference between Level 1 and Level 2?
**A:**
- **Level 1:** 1-10 stories, uses tech-spec (simpler, faster), no architecture
- **Level 2:** 5-15 stories, uses PRD (product-focused), optional architecture
The overlap (5-10 stories) is intentional. Choose based on:
- Need product-level planning? → Level 2
- Just need technical plan? → Level 1
- Multiple epics? → Level 2
- Single epic? → Level 1
---
## Workflows and Phases
### Q: What's the difference between workflow-status and workflow-init?
**A:**
- **workflow-status:** Checks existing status and tells you what's next (use when continuing work)
- **workflow-init:** Creates new status file and sets up project (use when starting new project)
If status file exists, use workflow-status. If not, use workflow-init.
### Q: Can I skip Phase 1 (Analysis)?
**A:** Yes! Phase 1 is optional for all levels, though recommended for complex projects. Skip if:
- Requirements are clear
- No research needed
- Time-sensitive work
- Small changes (Level 0-1)
### Q: When is Phase 3 (Architecture) required?
**A:**
- **Level 0-1:** Never (skip entirely)
- **Level 2:** Optional (only if system design needed)
- **Level 3-4:** Required (comprehensive architecture mandatory)
### Q: What happens if I skip a recommended workflow?
**A:** Nothing breaks! Workflows are guidance, not enforcement. However, skipping recommended workflows (like architecture for Level 3) may cause:
- Integration issues during implementation
- Rework due to poor planning
- Conflicting design decisions
- Longer development time overall
### Q: How do I know when Phase 3 is complete and I can start Phase 4?
**A:** For Level 3-4, run the implementation-readiness workflow. It validates PRD + Architecture + Epics + UX (optional) are aligned before implementation. Pass the gate check = ready for Phase 4.
### Q: Can I run workflows in parallel or do they have to be sequential?
**A:** Most workflows must be sequential within a phase:
- Phase 1: brainstorm → research → product-brief (optional order)
- Phase 2: PRD must complete before moving forward
- Phase 3: architecture → epics+stories → implementation-readiness (sequential)
- Phase 4: Stories within an epic should generally be sequential, but stories in different epics can be parallel if you have capacity
---
## Planning Documents
### Q: Why no tech-spec at Level 2+?
**A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
- PRD (product vision, functional requirements, non-functional requirements)
- Architecture (system design)
- Epics+Stories (created AFTER architecture is complete)
### Q: Do I need a PRD for a bug fix?
**A:** No! Bug fixes are typically Level 0 (single atomic change). Use Quick Spec Flow:
- Load PM agent
- Run tech-spec workflow
- Implement immediately
PRDs are for Level 2-4 projects with multiple features requiring product-level coordination.
### Q: Can I skip the product brief?
**A:** Yes, product brief is always optional. It's most valuable for:
- Level 3-4 projects needing strategic direction
- Projects with stakeholders requiring alignment
- Novel products needing market research
- When you want to explore solution space before committing
---
## Implementation
### Q: Does create-story include implementation context?
**A:** Yes! The create-story workflow generates story files that include implementation-specific guidance, references existing patterns from your documentation, and provides technical context. The workflow loads your architecture, PRD, and existing project documentation to create comprehensive stories. For Quick Flow projects using tech-spec, the tech-spec itself is already comprehensive, so stories can be simpler.
### Q: How do I mark a story as done?
**A:** After dev-story completes and code-review passes:
1. Open `sprint-status.yaml` (created by sprint-planning)
2. Change the story status from `review` to `done`
3. Save the file
### Q: Can I work on multiple stories at once?
**A:** Yes, if you have capacity! Stories within different epics can be worked in parallel. However, stories within the same epic are usually sequential because they build on each other.
### Q: What if my story takes longer than estimated?
**A:** That's normal! Stories are estimates. If implementation reveals more complexity:
1. Continue working until DoD is met
2. Consider if story should be split
3. Document learnings in retrospective
4. Adjust future estimates based on this learning
### Q: When should I run retrospective?
**A:** After completing all stories in an epic (when epic is done). Retrospectives capture:
- What went well
- What could improve
- Technical insights
- Learnings for future epics
Don't wait until project end - run after each epic for continuous improvement.
---
## Brownfield Development
### Q: What is brownfield vs greenfield?
**A:**
- **Greenfield:** New project, starting from scratch, clean slate
- **Brownfield:** Existing project, working with established codebase and patterns
### Q: Do I have to run document-project for brownfield?
**A:** Highly recommended, especially if:
- No existing documentation
- Documentation is outdated
- AI agents need context about existing code
- Level 2-4 complexity
You can skip it if you have comprehensive, up-to-date documentation including `docs/index.md`.
### Q: What if I forget to run document-project on brownfield?
**A:** Workflows will lack context about existing code. You may get:
- Suggestions that don't match existing patterns
- Integration approaches that miss existing APIs
- Architecture that conflicts with current structure
Run document-project and restart planning with proper context.
### Q: Can I use Quick Spec Flow for brownfield projects?
**A:** Yes! Quick Spec Flow works great for brownfield. It will:
- Auto-detect your existing stack
- Analyze brownfield code patterns
- Detect conventions and ask for confirmation
- Generate context-rich tech-spec that respects existing code
Perfect for bug fixes and small features in existing codebases.
### Q: How does workflow-init handle brownfield with old planning docs?
**A:** workflow-init asks about YOUR current work first, then uses old artifacts as context:
1. Shows what it found (old PRD, epics, etc.)
2. Asks: "Is this work in progress, previous effort, or proposed work?"
3. If previous effort: Asks you to describe your NEW work
4. Determines level based on YOUR work, not old artifacts
This prevents old Level 3 PRDs from forcing Level 3 workflow for new Level 0 bug fix.
### Q: What if my existing code doesn't follow best practices?
**A:** Quick Spec Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide:
- **Yes** → Maintain consistency with current codebase
- **No** → Establish new standards (document why in tech-spec)
BMM respects your choice - it won't force modernization, but it will offer it.
---
## Tools and Technical
### Q: Why are my Mermaid diagrams not rendering?
**A:** Common issues:
1. Missing language tag: Use ` ```mermaid` not just ` ``` `
2. Syntax errors in diagram (validate at mermaid.live)
3. Tool doesn't support Mermaid (check your Markdown renderer)
All BMM docs use valid Mermaid syntax that should render in GitHub, VS Code, and most IDEs.
### Q: Can I use BMM with GitHub Copilot / Cursor / other AI tools?
**A:** Yes! BMM is complementary. BMM handles:
- Project planning and structure
- Workflow orchestration
- Agent Personas and expertise
- Documentation generation
- Quality gates
Your AI coding assistant handles:
- Line-by-line code completion
- Quick refactoring
- Test generation
Use them together for best results.
### Q: What IDEs/tools support BMM?
**A:** BMM requires tools with **agent mode** and access to **high-quality LLM models** that can load and follow complex workflows, then properly implement code changes.
**Recommended Tools:**
- **Claude Code** ⭐ **Best choice**
- Sonnet 4.5 (excellent workflow following, coding, reasoning)
- Opus (maximum context, complex planning)
- Native agent mode designed for BMM workflows
- **Cursor**
- Supports Anthropic (Claude) and OpenAI models
- Agent mode with composer
- Good for developers who prefer Cursor's UX
- **Windsurf**
- Multi-model support
- Agent capabilities
- Suitable for BMM workflows
**What Matters:**
1. **Agent mode** - Can load long workflow instructions and maintain context
2. **High-quality LLM** - Models ranked high on SWE-bench (coding benchmarks)
3. **Model selection** - Access to Claude Sonnet 4.5, Opus, or GPT-4o class models
4. **Context capacity** - Can handle large planning documents and codebases
**Why model quality matters:** BMM workflows require LLMs that can follow multi-step processes, maintain context across phases, and implement code that adheres to specifications. Tools with weaker models will struggle with workflow adherence and code quality.
### Q: Can I customize agents?
**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `_bmad/_config/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
**Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.
### Q: What happens to my planning docs after implementation?
**A:** Keep them! They serve as:
- Historical record of decisions
- Onboarding material for new team members
- Reference for future enhancements
- Audit trail for compliance
For enterprise projects (Level 4), consider archiving completed planning artifacts to keep workspace clean.
### Q: Can I use BMM for non-software projects?
**A:** BMM is optimized for software development, but the methodology principles (scale-adaptive planning, just-in-time design, context injection) can apply to other complex project types. You'd need to adapt workflows and agents for your domain.
---
## Advanced Questions
### Q: What if my project grows from Level 1 to Level 3?
**A:** Totally fine! When you realize scope has grown:
1. Run create-prd to add product-level planning
2. Run create-architecture for system design
3. Use existing tech-spec as input for PRD
4. Continue with updated level
The system is flexible - growth is expected.
### Q: Can I mix greenfield and brownfield approaches?
**A:** Yes! Common scenario: adding new greenfield feature to brownfield codebase. Approach:
1. Run document-project for brownfield context
2. Use greenfield workflows for new feature planning
3. Explicitly document integration points between new and existing
4. Test integration thoroughly
### Q: How do I handle urgent hotfixes during a sprint?
**A:** Use correct-course workflow or just:
1. Save your current work state
2. Load PM agent → quick tech-spec for hotfix
3. Implement hotfix (Level 0 flow)
4. Deploy hotfix
5. Return to original sprint work
Level 0 Quick Spec Flow is perfect for urgent fixes.
### Q: What if I disagree with the workflow's recommendations?
**A:** Workflows are guidance, not enforcement. If a workflow recommends something that doesn't make sense for your context:
- Explain your reasoning to the agent
- Ask for alternative approaches
- Skip the recommendation if you're confident
- Document why you deviated (for future reference)
Trust your expertise - BMM supports your decisions.
### Q: Can multiple developers work on the same BMM project?
**A:** Yes! But the paradigm is fundamentally different from traditional agile teams.
**Key Difference:**
- **Traditional:** Multiple devs work on stories within one epic (months)
- **Agentic:** Each dev owns complete epics (days)
**In traditional agile:** A team of 5 devs might spend 2-3 months on a single epic, with each dev owning different stories.
**With BMM + AI agents:** A single dev can complete an entire epic in 1-3 days. What used to take months now takes days.
**Team Work Distribution:**
- **Recommended:** Split work by **epic** (not story)
- Each developer owns complete epics end-to-end
- Parallel work happens at epic level
- Minimal coordination needed
**For full-stack apps:**
- Frontend and backend can be separate epics (unusual in traditional agile)
- Frontend dev owns all frontend epics
- Backend dev owns all backend epics
- Works because delivery is so fast
**Enterprise Considerations:**
- Use **git submodules** for BMM installation (not .gitignore)
- Allows personal configurations without polluting main repo
- Teams may use different AI tools (Claude Code, Cursor, etc.)
- Developers may follow different methods or create custom agents/workflows
**Quick Tips:**
- Share `sprint-status.yaml` (single source of truth)
- Assign entire epics to developers (not individual stories)
- Coordinate at epic boundaries, not story level
- Use git submodules for BMM in enterprise settings
**For comprehensive coverage of enterprise team collaboration, work distribution strategies, git submodule setup, and velocity expectations, see:**
👉 **[Enterprise Agentic Development Guide](./enterprise-agentic-development.md)**
### Q: What is party mode and when should I use it?
**A:** Party mode is a unique multi-agent collaboration feature where ALL your installed agents (19+ from BMM, CIS, BMB, custom modules) discuss your challenges together in real-time.
**How it works:**
1. Run `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent)
2. Introduce your topic
3. BMad Master selects 2-3 most relevant agents per message
4. Agents cross-talk, debate, and build on each other's ideas
**Best for:**
- Strategic decisions with trade-offs (architecture choices, tech stack, scope)
- Creative brainstorming (game design, product innovation, UX ideation)
- Cross-functional alignment (epic kickoffs, retrospectives, phase transitions)
- Complex problem-solving (multi-faceted challenges, risk assessment)
**Example parties:**
- **Product Strategy:** PM + Innovation Strategist (CIS) + Analyst
- **Technical Design:** Architect + Creative Problem Solver (CIS) + Game Architect
- **User Experience:** UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
**Why it's powerful:**
- Diverse perspectives (technical, creative, strategic)
- Healthy debate reveals blind spots
- Emergent insights from agent interaction
- Natural collaboration across modules
**For complete documentation:**
👉 **[Party Mode Guide](../../explanation/features/party-mode.md)** - How it works, when to use it, example compositions, best practices
---
## Getting Help
### Q: Where do I get help if my question isn't answered here?
**A:**
1. Search [Complete Documentation](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) for related topics
2. Ask in [Discord Community](https://discord.gg/gk8jAdXWmj) (#general-dev)
3. Open a [GitHub Issue](https://github.com/bmad-code-org/BMAD-METHOD/issues)
4. Watch [YouTube Tutorials](https://www.youtube.com/@BMadCode)
### Q: How do I report a bug or request a feature?
**A:** Open a GitHub issue at: <https://github.com/bmad-code-org/BMAD-METHOD/issues>
Please include:
- BMM version (check your installed version)
- Steps to reproduce (for bugs)
- Expected vs actual behavior
- Relevant workflow or agent involved
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../../reference/glossary/index.md) - Terminology reference
- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding levels
- [Brownfield Guide](../../tutorials/advanced/brownfield-onboarding.md) - Existing codebase workflows
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

4
docs/modules/bmm-bmad-method/images/workflow-method-greenfield.svg
View File

File diff suppressed because one or more lines are too long
Side by Side

Before

Width:  |  Height:  |  Size: 87 KiB

622
docs/modules/bmm-bmad-method/quick-spec-flow.md
View File

@ -1,622 +0,0 @@
# BMad Quick Spec Flow
**Perfect for:** Bug fixes, small features, rapid prototyping, and quick enhancements
**Time to implementation:** Minutes, not hours
---
## What is Quick Spec Flow?
Quick Spec Flow is a **streamlined alternative** to the full BMad Method for Quick Flow track projects. Instead of going through Product Brief → PRD → Architecture, you go **straight to a context-aware technical specification** and start coding.
### When to Use Quick Spec Flow
✅ **Use Quick Flow track when:**
- Single bug fix or small enhancement
- Small feature with clear scope (typically 1-15 stories)
- Rapid prototyping or experimentation
- Adding to existing brownfield codebase
- You know exactly what you want to build
❌ **Use BMad Method or Enterprise tracks when:**
- Building new products or major features
- Need stakeholder alignment
- Complex multi-team coordination
- Requires extensive planning and architecture
💡 **Not sure?** Run `workflow-init` to get a recommendation based on your project's needs!
---
## Quick Spec Flow Overview
```mermaid
flowchart TD
START[Step 1: Run Tech-Spec Workflow]
DETECT[Detects project stack<br/>package.json, requirements.txt, etc.]
ANALYZE[Analyzes brownfield codebase<br/>if exists]
TEST[Detects test frameworks<br/>and conventions]
CONFIRM[Confirms conventions<br/>with you]
GENERATE[Generates context-rich<br/>tech-spec]
STORIES[Creates ready-to-implement<br/>stories]
OPTIONAL[Step 2: Optional<br/>Generate Story Context<br/>SM Agent<br/>For complex scenarios only]
IMPL[Step 3: Implement<br/>DEV Agent<br/>Code, test, commit]
DONE[DONE! 🚀]
START --> DETECT
DETECT --> ANALYZE
ANALYZE --> TEST
TEST --> CONFIRM
CONFIRM --> GENERATE
GENERATE --> STORIES
STORIES --> OPTIONAL
OPTIONAL -.->|Optional| IMPL
STORIES --> IMPL
IMPL --> DONE
style START fill:#bfb,stroke:#333,stroke-width:2px
style OPTIONAL fill:#ffb,stroke:#333,stroke-width:2px,stroke-dasharray: 5 5
style IMPL fill:#bbf,stroke:#333,stroke-width:2px
style DONE fill:#f9f,stroke:#333,stroke-width:3px
```
---
## Single Atomic Change
**Best for:** Bug fixes, single file changes, isolated improvements
### What You Get
1. **tech-spec.md** - Comprehensive technical specification with:
- Problem statement and solution
- Detected framework versions and dependencies
- Brownfield code patterns (if applicable)
- Existing test patterns to follow
- Specific file paths to modify
- Complete implementation guidance
2. **story-[slug].md** - Single user story ready for development
### Quick Spec Flow Commands
```bash
# Start Quick Spec Flow (no workflow-init needed!)
# Load PM agent and run tech-spec
# When complete, implement directly:
# Load DEV agent and run dev-story
```
### What Makes It Quick
- ✅ No Product Brief needed
- ✅ No PRD needed
- ✅ No Architecture doc needed
- ✅ Auto-detects your stack
- ✅ Auto-analyzes brownfield code
- ✅ Auto-validates quality
- ✅ Story context optional (tech-spec is comprehensive!)
### Example Single Change Scenarios
- "Fix the login validation bug"
- "Add email field to user registration form"
- "Update API endpoint to return additional field"
- "Improve error handling in payment processing"
---
## Coherent Small Feature
**Best for:** Small features with 2-3 related user stories
### What You Get
1. **tech-spec.md** - Same comprehensive spec as single change projects
2. **epics.md** - Epic organization with story breakdown
3. **story-[epic-slug]-1.md** - First story
4. **story-[epic-slug]-2.md** - Second story
5. **story-[epic-slug]-3.md** - Third story (if needed)
### Quick Spec Flow Commands
```bash
# Start Quick Spec Flow
# Load PM agent and run tech-spec
# Optional: Organize stories as a sprint
# Load SM agent and run sprint-planning
# Implement story-by-story:
# Load DEV agent and run dev-story for each story
```
### Story Sequencing
Stories are **automatically validated** to ensure proper sequence:
- ✅ No forward dependencies (Story 2 can't depend on Story 3)
- ✅ Clear dependency documentation
- ✅ Infrastructure → Features → Polish order
- ✅ Backend → Frontend flow
### Example Small Feature Scenarios
- "Add OAuth social login (Google, GitHub, Twitter)"
- "Build user profile page with avatar upload"
- "Implement basic search with filters"
- "Add dark mode toggle to application"
---
## Smart Context Discovery
Quick Spec Flow automatically discovers and uses:
### 1. Existing Documentation
- Product briefs (if they exist)
- Research documents
- `document-project` output (brownfield codebase map)
### 2. Project Stack
- **Node.js:** package.json → frameworks, dependencies, scripts, test framework
- **Python:** requirements.txt, pyproject.toml → packages, tools
- **Ruby:** Gemfile → gems and versions
- **Java:** pom.xml, build.gradle → Maven/Gradle dependencies
- **Go:** go.mod → modules
- **Rust:** Cargo.toml → crates
- **PHP:** composer.json → packages
### 3. Brownfield Code Patterns
- Directory structure and organization
- Existing code patterns (class-based, functional, MVC)
- Naming conventions (camelCase, snake_case, PascalCase)
- Test frameworks and patterns
- Code style (semicolons, quotes, indentation)
- Linter/formatter configs
- Error handling patterns
- Logging conventions
- Documentation style
### 4. Convention Confirmation
**IMPORTANT:** Quick Spec Flow detects your conventions and **asks for confirmation**:
```
I've detected these conventions in your codebase:
Code Style:
- ESLint with Airbnb config
- Prettier with single quotes, 2-space indent
- No semicolons
Test Patterns:
- Jest test framework
- .test.js file naming
- expect() assertion style
Should I follow these existing conventions? (yes/no)
```
**You decide:** Conform to existing patterns or establish new standards!
---
## Modern Best Practices via WebSearch
Quick Spec Flow stays current by using WebSearch when appropriate:
### For Greenfield Projects
- Searches for latest framework versions
- Recommends official starter templates
- Suggests modern best practices
### For Outdated Dependencies
- Detects if your dependencies are >2 years old
- Searches for migration guides
- Notes upgrade complexity
### Starter Template Recommendations
For greenfield projects, Quick Spec Flow recommends:
**React:**
- Vite (modern, fast)
- Next.js (full-stack)
**Python:**
- cookiecutter templates
- FastAPI starter
**Node.js:**
- NestJS CLI
- express-generator
**Benefits:**
- ✅ Modern best practices baked in
- ✅ Proper project structure
- ✅ Build tooling configured
- ✅ Testing framework set up
- ✅ Faster time to first feature
---
## UX/UI Considerations
For user-facing changes, Quick Spec Flow captures:
- UI components affected (create vs modify)
- UX flow changes (current vs new)
- Responsive design needs (mobile, tablet, desktop)
- Accessibility requirements:
- Keyboard navigation
- Screen reader compatibility
- ARIA labels
- Color contrast standards
- User feedback patterns:
- Loading states
- Error messages
- Success confirmations
- Progress indicators
---
## Auto-Validation and Quality Assurance
Quick Spec Flow **automatically validates** everything:
### Tech-Spec Validation (Always Runs)
Checks:
- ✅ Context gathering completeness
- ✅ Definitiveness (no "use X or Y" statements)
- ✅ Brownfield integration quality
- ✅ Stack alignment
- ✅ Implementation readiness
Generates scores:
```
✅ Validation Passed!
- Context Gathering: Comprehensive
- Definitiveness: All definitive
- Brownfield Integration: Excellent
- Stack Alignment: Perfect
- Implementation Readiness: ✅ Ready
```
### Story Validation (Multi-Story Features)
Checks:
- ✅ Story sequence (no forward dependencies!)
- ✅ Acceptance criteria quality (specific, testable)
- ✅ Completeness (all tech spec tasks covered)
- ✅ Clear dependency documentation
**Auto-fixes issues if found!**
---
## Complete User Journey
### Scenario 1: Bug Fix (Single Change)
**Goal:** Fix login validation bug
**Steps:**
1. **Start:** Load PM agent, say "I want to fix the login validation bug"
2. **PM runs tech-spec workflow:**
- Asks: "What problem are you solving?"
- You explain the validation issue
- Detects your Node.js stack (Express 4.18.2, Jest for testing)
- Analyzes existing UserService code patterns
- Asks: "Should I follow your existing conventions?" → You say yes
- Generates tech-spec.md with specific file paths and patterns
- Creates story-login-fix.md
3. **Implement:** Load DEV agent, run `dev-story`
- DEV reads tech-spec (has all context!)
- Implements fix following existing patterns
- Runs tests (following existing Jest patterns)
- Done!
**Total time:** 15-30 minutes (mostly implementation)
---
### Scenario 2: Small Feature (Multi-Story)
**Goal:** Add OAuth social login (Google, GitHub)
**Steps:**
1. **Start:** Load PM agent, say "I want to add OAuth social login"
2. **PM runs tech-spec workflow:**
- Asks about the feature scope
- You specify: Google and GitHub OAuth
- Detects your stack (Next.js 13.4, NextAuth.js already installed!)
- Analyzes existing auth patterns
- Confirms conventions with you
- Generates:
- tech-spec.md (comprehensive implementation guide)
- epics.md (OAuth Integration epic)
- story-oauth-1.md (Backend OAuth setup)
- story-oauth-2.md (Frontend login buttons)
3. **Optional Sprint Planning:** Load SM agent, run `sprint-planning`
4. **Implement Story 1:**
- Load DEV agent, run `dev-story` for story 1
- DEV implements backend OAuth
5. **Implement Story 2:**
- DEV agent, run `dev-story` for story 2
- DEV implements frontend
- Done!
**Total time:** 1-3 hours (mostly implementation)
## Integration with Phase 4 Workflows
Quick Spec Flow works seamlessly with all Phase 4 implementation workflows:
### create-story (SM Agent)
- ✅ Can work with tech-spec.md instead of PRD
- ✅ Uses epics.md from tech-spec workflow
- ✅ Creates additional stories if needed
### sprint-planning (SM Agent)
- ✅ Works with epics.md from tech-spec
- ✅ Organizes multi-story features for coordinated implementation
- ✅ Tracks progress through sprint-status.yaml
### dev-story (DEV Agent)
- ✅ Reads stories generated by tech-spec
- ✅ Uses tech-spec.md as comprehensive context
- ✅ Implements following detected conventions
## Comparison: Quick Spec vs Full BMM
| Aspect | Quick Flow Track | BMad Method/Enterprise Tracks |
| --------------------- | ---------------------------- | ---------------------------------- |
| **Setup** | None (standalone) | workflow-init recommended |
| **Planning Docs** | tech-spec.md only | Product Brief → PRD → Architecture |
| **Time to Code** | Minutes | Hours to days |
| **Best For** | Bug fixes, small features | New products, major features |
| **Context Discovery** | Automatic | Manual + guided |
| **Story Context** | Optional (tech-spec is rich) | Required (generated from PRD) |
| **Validation** | Auto-validates everything | Manual validation steps |
| **Brownfield** | Auto-analyzes and conforms | Manual documentation required |
| **Conventions** | Auto-detects and confirms | Document in PRD/Architecture |
## When to Graduate from Quick Flow to BMad Method
Start with Quick Flow, but switch to BMad Method when:
- ❌ Project grows beyond initial scope
- ❌ Multiple teams need coordination
- ❌ Stakeholders need formal documentation
- ❌ Product vision is unclear
- ❌ Architectural decisions need deep analysis
- ❌ Compliance/regulatory requirements exist
💡 **Tip:** You can always run `workflow-init` later to transition from Quick Flow to BMad Method!
## Quick Spec Flow - Key Benefits
### 🚀 **Speed**
- No Product Brief
- No PRD
- No Architecture doc
- Straight to implementation
### 🧠 **Intelligence**
- Auto-detects stack
- Auto-analyzes brownfield
- Auto-validates quality
- WebSearch for current info
### 📐 **Respect for Existing Code**
- Detects conventions
- Asks for confirmation
- Follows patterns
- Adapts vs. changes
### ✅ **Quality**
- Auto-validation
- Definitive decisions (no "or" statements)
- Comprehensive context
- Clear acceptance criteria
### 🎯 **Focus**
- Single atomic changes
- Coherent small features
- No scope creep
- Fast iteration
## Getting Started
### Prerequisites
- BMad Method installed (`npx bmad-method install`)
- Project directory with code (or empty for greenfield)
### Quick Start Commands
```bash
# For a quick bug fix or small change:
# 1. Load Quick Dev Solo agent
# 2. Say: "I want to [describe your change]"
# 3. Agent will ask if you want to run tech-spec
# 4. Answer questions about your change
# 5. Get tech-spec + story
# 6. Reload a fresh context with the solo agent and implement!
# For a small feature with multiple stories:
# Same as above, but get epic + 2-3 stories
# Optionally use SM sprint-planning to organize
```
### No workflow-init Required!
Quick Spec Flow is **fully standalone**
## FAQ
### Q: Can I use Quick Spec Flow on an existing project?
**A:** Yes! It's perfect for brownfield projects. It will analyze your existing code, detect patterns, and ask if you want to follow them.
### Q: What if I don't have a package.json or requirements.txt?
**A:** Quick Spec Flow will work in greenfield mode, recommend starter templates, and use WebSearch for modern best practices.
### Q: Do I need to run workflow-init first?
**A:** No! Quick Spec Flow is standalone. But if you want guidance on which flow to use, workflow-init can help.
### Q: Can I use this for frontend changes?
**A:** Absolutely! Quick Spec Flow captures UX/UI considerations, component changes, and accessibility requirements.
### Q: What if my Quick Flow project grows?
**A:** No problem! You can always transition to BMad Method by running workflow-init and create-prd. Your tech-spec becomes input for the PRD.
### Q: Can I skip validation?
**A:** No, validation always runs automatically. But it's fast and catches issues early!
### Q: Will it work with my team's code style?
**A:** Yes! It detects your conventions and asks for confirmation. You control whether to follow existing patterns or establish new ones.
---
## Tips and Best Practices
### 1. **Be Specific in Discovery**
When describing your change, provide specifics:
- ✅ "Fix email validation in UserService to allow plus-addressing"
- ❌ "Fix validation bug"
### 2. **Trust the Convention Detection**
If it detects your patterns correctly, say yes! It's faster than establishing new conventions.
### 3. **Use WebSearch Recommendations for Greenfield**
Starter templates save hours of setup time. Let Quick Spec Flow find the best ones.
### 4. **Review the Auto-Validation**
When validation runs, read the scores. They tell you if your spec is production-ready.
### 5. **Keep Single Changes Truly Atomic**
If your "single change" needs 3+ files, it might be a multi-story feature. Let the workflow guide you.
### 6. **Validate Story Sequence for Multi-Story Features**
When you get multiple stories, check the dependency validation output. Proper sequence matters!
---
## Real-World Examples
### Example 1: Adding Logging (Single Change)
**Input:** "Add structured logging to payment processing"
**Tech-Spec Output:**
- Detected: winston 3.8.2 already in package.json
- Analyzed: Existing services use winston with JSON format
- Confirmed: Follow existing logging patterns
- Generated: Specific file paths, log levels, format example
- Story: Ready to implement in 1-2 hours
**Result:** Consistent logging added, following team patterns, no research needed.
---
### Example 2: Search Feature (Multi-Story)
**Input:** "Add search to product catalog with filters"
**Tech-Spec Output:**
- Detected: React 18.2.0, MUI component library, Express backend
- Analyzed: Existing ProductList component patterns
- Confirmed: Follow existing API and component structure
- Generated:
- Epic: Product Search Functionality
- Story 1: Backend search API with filters
- Story 2: Frontend search UI component
- Auto-validated: Story 1 → Story 2 sequence correct
**Result:** Search feature implemented in 4-6 hours with proper architecture.
---
## Summary
Quick Spec Flow is your **fast path from idea to implementation** for:
- 🐛 Bug fixes
- ✨ Small features
- 🚀 Rapid prototyping
- 🔧 Quick enhancements
**Key Features:**
- Auto-detects your stack
- Auto-analyzes brownfield code
- Auto-validates quality
- Respects existing conventions
- Uses WebSearch for modern practices
- Generates comprehensive tech-specs
- Creates implementation-ready stories
**Time to code:** Minutes, not hours.
**Ready to try it?** Load the PM agent and say what you want to build! 🚀
---
## Next Steps
- **Try it now:** Load PM agent and describe a small change
- **Learn more:** See the [BMM Workflow Guides](./index.md#-workflow-guides) for comprehensive workflow documentation
- **Need help deciding?** Run `workflow-init` to get a recommendation
- **Have questions?** Join us on Discord: <https://discord.gg/gk8jAdXWmj>
---
_Quick Spec Flow - Because not every change needs a Product Brief._

486
docs/modules/bmm-bmad-method/test-architecture.md
View File

@ -1,486 +0,0 @@
# Test Architect (TEA) Agent Guide
## Overview
- **Persona:** Murat, Master Test Architect and Quality Advisor focused on risk-based testing, fixture architecture, ATDD, and CI/CD governance.
- **Mission:** Deliver actionable quality strategies, automation coverage, and gate decisions that scale with project complexity and compliance demands.
- **Use When:** BMad Method or Enterprise track projects, integration risk is non-trivial, brownfield regression risk exists, or compliance/NFR evidence is required. (Quick Flow projects typically don't require TEA)
## Choose Your TEA Engagement Model
BMad does not mandate TEA. There are five valid ways to use it (or skip it). Pick one intentionally.
1. **No TEA**
- Skip all TEA workflows. Use your existing team testing approach.
2. **TEA-only (Standalone)**
- Use TEA on a non-BMad project. Bring your own requirements, acceptance criteria, and environments.
- Typical sequence: `*test-design` (system or epic) -> `*atdd` and/or `*automate` -> optional `*test-review` -> `*trace` for coverage and gate decisions.
- Run `*framework` or `*ci` only if you want TEA to scaffold the harness or pipeline.
3. **Integrated: Greenfield - BMad Method (Simple/Standard Work)**
- Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
- Phase 4: per-epic `*test-design`, optional `*atdd`, then `*automate` and optional `*test-review`.
- Gate (Phase 2): `*trace`.
4. **Integrated: Brownfield - BMad Method or Enterprise (Simple or Complex)**
- Phase 2: baseline `*trace`.
- Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
- Phase 4: per-epic `*test-design` focused on regression and integration risks.
- Gate (Phase 2): `*trace`; `*nfr-assess` (if not done earlier).
- For brownfield BMad Method, follow the same flow with `*nfr-assess` optional.
5. **Integrated: Greenfield - Enterprise Method (Enterprise/Compliance Work)**
- Phase 2: `*nfr-assess`.
- Phase 3: system-level `*test-design`, then `*framework` and `*ci`.
- Phase 4: per-epic `*test-design`, plus `*atdd`/`*automate`/`*test-review`.
- Gate (Phase 2): `*trace`; archive artifacts as needed.
If you are unsure, default to the integrated path for your track and adjust later.
## TEA Workflow Lifecycle
TEA integrates into the BMad development lifecycle during Solutioning (Phase 3) and Implementation (Phase 4):
```mermaid
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','secondaryColor':'#fff','tertiaryColor':'#fff','fontSize':'16px','fontFamily':'arial'}}}%%
graph TB
subgraph Phase2["<b>Phase 2: PLANNING</b>"]
PM["<b>PM: *prd (creates PRD with FRs/NFRs)</b>"]
PlanNote["<b>Business requirements phase</b>"]
NFR2["<b>TEA: *nfr-assess (optional, enterprise)</b>"]
PM -.-> NFR2
NFR2 -.-> PlanNote
PM -.-> PlanNote
end
subgraph Phase3["<b>Phase 3: SOLUTIONING</b>"]
Architecture["<b>Architect: *architecture</b>"]
EpicsStories["<b>PM/Architect: *create-epics-and-stories</b>"]
TestDesignSys["<b>TEA: *test-design (system-level)</b>"]
Framework["<b>TEA: *framework (optional if needed)</b>"]
CI["<b>TEA: *ci (optional if needed)</b>"]
GateCheck["<b>Architect: *implementation-readiness</b>"]
Architecture --> EpicsStories
Architecture --> TestDesignSys
TestDesignSys --> Framework
EpicsStories --> Framework
Framework --> CI
CI --> GateCheck
Phase3Note["<b>Epics created AFTER architecture,</b><br/><b>then system-level test design and test infrastructure setup</b>"]
EpicsStories -.-> Phase3Note
end
subgraph Phase4["<b>Phase 4: IMPLEMENTATION - Per Epic Cycle</b>"]
SprintPlan["<b>SM: *sprint-planning</b>"]
TestDesign["<b>TEA: *test-design (per epic)</b>"]
CreateStory["<b>SM: *create-story</b>"]
ATDD["<b>TEA: *atdd (optional, before dev)</b>"]
DevImpl["<b>DEV: implements story</b>"]
Automate["<b>TEA: *automate</b>"]
TestReview1["<b>TEA: *test-review (optional)</b>"]
Trace1["<b>TEA: *trace (refresh coverage)</b>"]
SprintPlan --> TestDesign
TestDesign --> CreateStory
CreateStory --> ATDD
ATDD --> DevImpl
DevImpl --> Automate
Automate --> TestReview1
TestReview1 --> Trace1
Trace1 -.->|next story| CreateStory
TestDesignNote["<b>Test design: 'How do I test THIS epic?'</b><br/>Creates test-design-epic-N.md per epic"]
TestDesign -.-> TestDesignNote
end
subgraph Gate["<b>EPIC/RELEASE GATE</b>"]
NFR["<b>TEA: *nfr-assess (if not done earlier)</b>"]
TestReview2["<b>TEA: *test-review (final audit, optional)</b>"]
TraceGate["<b>TEA: *trace - Phase 2: Gate</b>"]
GateDecision{"<b>Gate Decision</b>"}
NFR --> TestReview2
TestReview2 --> TraceGate
TraceGate --> GateDecision
GateDecision -->|PASS| Pass["<b>PASS ✅</b>"]
GateDecision -->|CONCERNS| Concerns["<b>CONCERNS ⚠️</b>"]
GateDecision -->|FAIL| Fail["<b>FAIL ❌</b>"]
GateDecision -->|WAIVED| Waived["<b>WAIVED ⏭️</b>"]
end
Phase2 --> Phase3
Phase3 --> Phase4
Phase4 --> Gate
style Phase2 fill:#bbdefb,stroke:#0d47a1,stroke-width:3px,color:#000
style Phase3 fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px,color:#000
style Phase4 fill:#e1bee7,stroke:#4a148c,stroke-width:3px,color:#000
style Gate fill:#ffe082,stroke:#f57c00,stroke-width:3px,color:#000
style Pass fill:#4caf50,stroke:#1b5e20,stroke-width:3px,color:#000
style Concerns fill:#ffc107,stroke:#f57f17,stroke-width:3px,color:#000
style Fail fill:#f44336,stroke:#b71c1c,stroke-width:3px,color:#000
style Waived fill:#9c27b0,stroke:#4a148c,stroke-width:3px,color:#000
```
**Phase Numbering Note:** BMad uses a 4-phase methodology with optional Phase 1 and documentation prerequisite:
- **Documentation** (Optional for brownfield): Prerequisite using `*document-project`
- **Phase 1** (Optional): Discovery/Analysis (`*brainstorm`, `*research`, `*product-brief`)
- **Phase 2** (Required): Planning (`*prd` creates PRD with FRs/NFRs)
- **Phase 3** (Track-dependent): Solutioning (`*architecture` → `*test-design` (system-level) → `*create-epics-and-stories` → TEA: `*framework`, `*ci` → `*implementation-readiness`)
- **Phase 4** (Required): Implementation (`*sprint-planning` → per-epic: `*test-design` → per-story: dev workflows)
**TEA workflows:** `*framework` and `*ci` run once in Phase 3 after architecture. `*test-design` is **dual-mode**:
- **System-level (Phase 3):** Run immediately after architecture/ADR drafting to produce `test-design-system.md` (testability review, ADR → test mapping, Architecturally Significant Requirements (ASRs), environment needs). Feeds the implementation-readiness gate.
- **Epic-level (Phase 4):** Run per-epic to produce `test-design-epic-N.md` (risk, priorities, coverage plan).
Quick Flow track skips Phases 1 and 3.
BMad Method and Enterprise use all phases based on project needs.
When an ADR or architecture draft is produced, run `*test-design` in **system-level** mode before the implementation-readiness gate. This ensures the ADR has an attached testability review and ADR → test mapping. Keep the test-design updated if ADRs change.
### Why TEA is Different from Other BMM Agents
TEA is the only BMM agent that operates in **multiple phases** (Phase 3 and Phase 4) and has its own **knowledge base architecture**.
<details>
<summary><strong>Cross-Phase Operation & Unique Architecture</strong></summary>
### Phase-Specific Agents (Standard Pattern)
Most BMM agents work in a single phase:
- **Phase 1 (Analysis)**: Analyst agent
- **Phase 2 (Planning)**: PM agent
- **Phase 3 (Solutioning)**: Architect agent
- **Phase 4 (Implementation)**: SM, DEV agents
### TEA: Multi-Phase Quality Agent (Unique Pattern)
TEA is **the only agent that operates in multiple phases**:
```
Phase 1 (Analysis) → [TEA not typically used]
↓
Phase 2 (Planning) → [PM defines requirements - TEA not active]
↓
Phase 3 (Solutioning) → TEA: *framework, *ci (test infrastructure AFTER architecture)
↓
Phase 4 (Implementation) → TEA: *test-design (per epic: "how do I test THIS feature?")
→ TEA: *atdd, *automate, *test-review, *trace (per story)
↓
Epic/Release Gate → TEA: *nfr-assess, *trace Phase 2 (release decision)
```
### TEA's 8 Workflows Across Phases
**Standard agents**: 1-3 workflows per phase
**TEA**: 8 workflows across Phase 3, Phase 4, and Release Gate
| Phase | TEA Workflows | Frequency | Purpose |
| ----------- | --------------------------------------------------------- | ---------------- | ---------------------------------------------- |
| **Phase 2** | (none) | - | Planning phase - PM defines requirements |
| **Phase 3** | \*framework, \*ci | Once per project | Setup test infrastructure AFTER architecture |
| **Phase 4** | \*test-design, \*atdd, \*automate, \*test-review, \*trace | Per epic/story | Test planning per epic, then per-story testing |
| **Release** | \*nfr-assess, \*trace (Phase 2: gate) | Per epic/release | Go/no-go decision |
**Note**: `*trace` is a two-phase workflow: Phase 1 (traceability) + Phase 2 (gate decision). This reduces cognitive load while maintaining natural workflow.
### Why TEA Gets Special Treatment
TEA uniquely requires:
- **Extensive domain knowledge**: 32 fragments covering test patterns, CI/CD, fixtures, quality practices, healing strategies, and optional playwright-utils integration
- **Centralized reference system**: `tea-index.csv` for on-demand fragment loading during workflow execution
- **Cross-cutting concerns**: Domain-specific testing patterns (vs project-specific artifacts like PRDs/stories)
- **Optional integrations**: MCP capabilities (healing, exploratory, verification) and playwright-utils support
This architecture enables TEA to maintain consistent, production-ready testing patterns across all BMad projects while operating across multiple development phases.
### Playwright Utils Integration
TEA optionally integrates with `@seontechnologies/playwright-utils`, an open-source library providing fixture-based utilities for Playwright tests.
**Installation:**
```bash
npm install -D @seontechnologies/playwright-utils
```
**Enable during BMAD installation** by answering "Yes" when prompted.
**Supported utilities (10 total):**
- api-request, network-recorder, auth-session, intercept-network-call, recurse
- log, file-utils, burn-in, network-error-monitor
- fixtures-composition (integration patterns)
**Workflows adapt:** automate, framework, test-review, ci, atdd (+ light mention in test-design).
**Knowledge base:** 32 total fragments (21 core patterns + 11 playwright-utils)
</details>
## High-Level Cheat Sheets
These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks** across the **4-Phase Methodology** (Phase 1: Analysis, Phase 2: Planning, Phase 3: Solutioning, Phase 4: Implementation).
**Note:** Quick Flow projects typically don't require TEA (covered in Overview). These cheat sheets focus on BMad Method and Enterprise tracks where TEA adds value.
**Legend for Track Deltas:**
- ➕ = New workflow or phase added (doesn't exist in baseline)
- 🔄 = Modified focus (same workflow, different emphasis or purpose)
- 📦 = Additional output or archival requirement
### Greenfield - BMad Method (Simple/Standard Work)
**Planning Track:** BMad Method (PRD + Architecture)
**Use Case:** New projects with standard complexity
| Workflow Stage | Test Architect | Dev / Team | Outputs |
| -------------------------- | ----------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| **Phase 1**: Discovery | - | Analyst `*product-brief` (optional) | `product-brief.md` |
| **Phase 2**: Planning | - | PM `*prd` (creates PRD with FRs/NFRs) | PRD with functional/non-functional requirements |
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test scaffold, CI pipeline |
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint status file with all epics and stories |
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic (per-epic test plan) | Review epic scope | `test-design-epic-N.md` with risk assessment and test plan |
| **Phase 4**: Story Dev | (Optional) `*atdd` before dev, then `*automate` after | SM `*create-story`, DEV implements | Tests, story implementation |
| **Phase 4**: Story Review | Execute `*test-review` (optional), re-run `*trace` | Address recommendations, update code/tests | Quality report, refreshed coverage matrix |
| **Phase 4**: Release Gate | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Confirm Definition of Done, share release notes | Quality audit, Gate YAML + release summary |
<details>
<summary>Execution Notes</summary>
- Run `*framework` only once per repo or when modern harness support is missing.
- **Phase 3 (Solutioning)**: After architecture is complete, run `*framework` and `*ci` to setup test infrastructure based on architectural decisions.
- **Phase 4 starts**: After solutioning is complete, sprint planning loads all epics.
- **`*test-design` runs per-epic**: At the beginning of working on each epic, run `*test-design` to create a test plan for THAT specific epic/feature. Output: `test-design-epic-N.md`.
- Use `*atdd` before coding when the team can adopt ATDD; share its checklist with the dev agent.
- Post-implementation, keep `*trace` current, expand coverage with `*automate`, optionally review test quality with `*test-review`. For release gate, run `*trace` with Phase 2 enabled to get deployment decision.
- Use `*test-review` after `*atdd` to validate generated tests, after `*automate` to ensure regression quality, or before gate for final audit.
- Clarification: `*test-review` is optional and only audits existing tests; run it after `*atdd` or `*automate` when you want a quality review, not as a required step.
- Clarification: `*atdd` outputs are not auto-consumed; share the ATDD doc/tests with the dev workflow. `*trace` does not run `*atdd`—it evaluates existing artifacts for coverage and gate readiness.
- Clarification: `*ci` is a one-time setup; recommended early (Phase 3 or before feature work), but it can be done later if it was skipped.
</details>
<details>
<summary>Worked Example – “Nova CRM” Greenfield Feature</summary>
1. **Planning (Phase 2):** Analyst runs `*product-brief`; PM executes `*prd` to produce PRD with FRs/NFRs.
2. **Solutioning (Phase 3):** Architect completes `*architecture` for the new module; `*create-epics-and-stories` generates epics/stories based on architecture; TEA sets up test infrastructure via `*framework` and `*ci` based on architectural decisions; gate check validates planning completeness.
3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
4. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` to create test plan for Epic 1, producing `test-design-epic-1.md` with risk assessment.
5. **Story Implementation (Phase 4):** For each story in Epic 1, SM generates story via `*create-story`; TEA optionally runs `*atdd`; Dev implements with guidance from failing tests.
6. **Post-Dev (Phase 4):** TEA runs `*automate`, optionally `*test-review` to audit test quality, re-runs `*trace` to refresh coverage.
7. **Release Gate:** TEA runs `*trace` with Phase 2 enabled to generate gate decision.
</details>
### Brownfield - BMad Method or Enterprise (Simple or Complex)
**Planning Tracks:** BMad Method or Enterprise Method
**Use Case:** Existing codebases - simple additions (BMad Method) or complex enterprise requirements (Enterprise Method)
**🔄 Brownfield Deltas from Greenfield:**
- ➕ Documentation (Prerequisite) - Document existing codebase if undocumented
- ➕ Phase 2: `*trace` - Baseline existing test coverage before planning
- 🔄 Phase 4: `*test-design` - Focus on regression hotspots and brownfield risks
- 🔄 Phase 4: Story Review - May include `*nfr-assess` if not done earlier
| Workflow Stage | Test Architect | Dev / Team | Outputs |
| --------------------------------- | --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Documentation**: Prerequisite ➕ | - | Analyst `*document-project` (if undocumented) | Comprehensive project documentation |
| **Phase 1**: Discovery | - | Analyst/PM/Architect rerun planning workflows | Updated planning artifacts in `{output_folder}` |
| **Phase 2**: Planning | Run ➕ `*trace` (baseline coverage) | PM `*prd` (creates PRD with FRs/NFRs) | PRD with FRs/NFRs, ➕ coverage baseline |
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline |
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint status file with all epics and stories |
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (regression hotspots) | Review epic scope and brownfield risks | `test-design-epic-N.md` with brownfield risk assessment and mitigation |
| **Phase 4**: Story Dev | (Optional) `*atdd` before dev, then `*automate` after | SM `*create-story`, DEV implements | Tests, story implementation |
| **Phase 4**: Story Review | Apply `*test-review` (optional), re-run `*trace`, ➕ `*nfr-assess` if needed | Resolve gaps, update docs/tests | Quality report, refreshed coverage matrix, NFR report |
| **Phase 4**: Release Gate | (Optional) `*test-review` for final audit, Run `*trace` (Phase 2) | Capture sign-offs, share release notes | Quality audit, Gate YAML + release summary |
<details>
<summary>Execution Notes</summary>
- Lead with `*trace` during Planning (Phase 2) to baseline existing test coverage before architecture work begins.
- **Phase 3 (Solutioning)**: After architecture is complete, run `*framework` and `*ci` to modernize test infrastructure. For brownfield, framework may need to integrate with or replace existing test setup.
- **Phase 4 starts**: After solutioning is complete and sprint planning loads all epics.
- **`*test-design` runs per-epic**: At the beginning of working on each epic, run `*test-design` to identify regression hotspots, integration risks, and mitigation strategies for THAT specific epic/feature. Output: `test-design-epic-N.md`.
- Use `*atdd` when stories benefit from ATDD; otherwise proceed to implementation and rely on post-dev automation.
- After development, expand coverage with `*automate`, optionally review test quality with `*test-review`, re-run `*trace` (Phase 2 for gate decision). Run `*nfr-assess` now if non-functional risks weren't addressed earlier.
- Use `*test-review` to validate existing brownfield tests or audit new tests before gate.
</details>
<details>
<summary>Worked Example – “Atlas Payments” Brownfield Story</summary>
1. **Planning (Phase 2):** PM executes `*prd` to create PRD with FRs/NFRs; TEA runs `*trace` to baseline existing coverage.
2. **Solutioning (Phase 3):** Architect triggers `*architecture` capturing legacy payment flows and integration architecture; `*create-epics-and-stories` generates Epic 1 (Payment Processing) based on architecture; TEA sets up `*framework` and `*ci` based on architectural decisions; gate check validates planning.
3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load Epic 1 into sprint status.
4. **Epic 1 Planning (Phase 4):** TEA runs `*test-design` for Epic 1 (Payment Processing), producing `test-design-epic-1.md` that flags settlement edge cases, regression hotspots, and mitigation plans.
5. **Story Implementation (Phase 4):** For each story in Epic 1, SM generates story via `*create-story`; TEA runs `*atdd` producing failing Playwright specs; Dev implements with guidance from tests and checklist.
6. **Post-Dev (Phase 4):** TEA applies `*automate`, optionally `*test-review` to audit test quality, re-runs `*trace` to refresh coverage.
7. **Release Gate:** TEA performs `*nfr-assess` to validate SLAs, runs `*trace` with Phase 2 enabled to generate gate decision (PASS/CONCERNS/FAIL).
</details>
### Greenfield - Enterprise Method (Enterprise/Compliance Work)
**Planning Track:** Enterprise Method (BMad Method + extended security/devops/test strategies)
**Use Case:** New enterprise projects with compliance, security, or complex regulatory requirements
**🏢 Enterprise Deltas from BMad Method:**
- ➕ Phase 1: `*research` - Domain and compliance research (recommended)
- ➕ Phase 2: `*nfr-assess` - Capture NFR requirements early (security/performance/reliability)
- 🔄 Phase 4: `*test-design` - Enterprise focus (compliance, security architecture alignment)
- 📦 Release Gate - Archive artifacts and compliance evidence for audits
| Workflow Stage | Test Architect | Dev / Team | Outputs |
| -------------------------- | ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------ |
| **Phase 1**: Discovery | - | Analyst ➕ `*research`, `*product-brief` | Domain research, compliance analysis, product brief |
| **Phase 2**: Planning | Run ➕ `*nfr-assess` | PM `*prd` (creates PRD with FRs/NFRs), UX `*create-ux-design` | Enterprise PRD with FRs/NFRs, UX design, ➕ NFR documentation |
| **Phase 3**: Solutioning | Run `*framework`, `*ci` AFTER architecture and epic creation | Architect `*architecture`, `*create-epics-and-stories`, `*implementation-readiness` | Architecture, epics/stories, test framework, CI pipeline |
| **Phase 4**: Sprint Start | - | SM `*sprint-planning` | Sprint plan with all epics |
| **Phase 4**: Epic Planning | Run `*test-design` for THIS epic 🔄 (compliance focus) | Review epic scope and compliance requirements | `test-design-epic-N.md` with security/performance/compliance focus |
| **Phase 4**: Story Dev | (Optional) `*atdd`, `*automate`, `*test-review`, `*trace` per story | SM `*create-story`, DEV implements | Tests, fixtures, quality reports, coverage matrices |
| **Phase 4**: Release Gate | Final `*test-review` audit, Run `*trace` (Phase 2), 📦 archive artifacts | Capture sign-offs, 📦 compliance evidence | Quality audit, updated assessments, gate YAML, 📦 audit trail |
<details>
<summary>Execution Notes</summary>
- `*nfr-assess` runs early in Planning (Phase 2) to capture compliance, security, and performance requirements upfront.
- **Phase 3 (Solutioning)**: After architecture is complete, run `*framework` and `*ci` with enterprise-grade configurations (selective testing, burn-in jobs, caching, notifications).
- **Phase 4 starts**: After solutioning is complete and sprint planning loads all epics.
- **`*test-design` runs per-epic**: At the beginning of working on each epic, run `*test-design` to create an enterprise-focused test plan for THAT specific epic, ensuring alignment with security architecture, performance targets, and compliance requirements. Output: `test-design-epic-N.md`.
- Use `*atdd` for stories when feasible so acceptance tests can lead implementation.
- Use `*test-review` per story or sprint to maintain quality standards and ensure compliance with testing best practices.
- Prior to release, rerun coverage (`*trace`, `*automate`), perform final quality audit with `*test-review`, and formalize the decision with `*trace` Phase 2 (gate decision); archive artifacts for compliance audits.
</details>
<details>
<summary>Worked Example – “Helios Ledger” Enterprise Release</summary>
1. **Planning (Phase 2):** Analyst runs `*research` and `*product-brief`; PM completes `*prd` creating PRD with FRs/NFRs; TEA runs `*nfr-assess` to establish NFR targets.
2. **Solutioning (Phase 3):** Architect completes `*architecture` with enterprise considerations; `*create-epics-and-stories` generates epics/stories based on architecture; TEA sets up `*framework` and `*ci` with enterprise-grade configurations based on architectural decisions; gate check validates planning completeness.
3. **Sprint Start (Phase 4):** Scrum Master runs `*sprint-planning` to load all epics into sprint status.
4. **Per-Epic (Phase 4):** For each epic, TEA runs `*test-design` to create epic-specific test plan (e.g., `test-design-epic-1.md`, `test-design-epic-2.md`) with compliance-focused risk assessment.
5. **Per-Story (Phase 4):** For each story, TEA uses `*atdd`, `*automate`, `*test-review`, and `*trace`; Dev teams iterate on the findings.
6. **Release Gate:** TEA re-checks coverage, performs final quality audit with `*test-review`, and logs the final gate decision via `*trace` Phase 2, archiving artifacts for compliance.
</details>
## Command Catalog
<details>
<summary><strong>Optional Playwright MCP Enhancements</strong></summary>
**Two Playwright MCP servers** (actively maintained, continuously updated):
- `playwright` - Browser automation (`npx @playwright/mcp@latest`)
- `playwright-test` - Test runner with failure analysis (`npx playwright run-test-mcp-server`)
**How MCP Enhances TEA Workflows**:
MCP provides additional capabilities on top of TEA's default AI-based approach:
1. `*test-design`:
- Default: Analysis + documentation
- **+ MCP**: Interactive UI discovery with `browser_navigate`, `browser_click`, `browser_snapshot`, behavior observation
Benefit: Discover actual functionality, edge cases, undocumented features
2. `*atdd`, `*automate`:
- Default: Infers selectors and interactions from requirements and knowledge fragments
- **+ MCP**: Generates tests **then** verifies with `generator_setup_page`, `browser_*` tools, validates against live app
Benefit: Accurate selectors from real DOM, verified behavior, refined test code
3. `*automate`:
- Default: Pattern-based fixes from error messages + knowledge fragments
- **+ MCP**: Pattern fixes **enhanced with** `browser_snapshot`, `browser_console_messages`, `browser_network_requests`, `browser_generate_locator`
Benefit: Visual failure context, live DOM inspection, root cause discovery
**Config example**:
```json
{
"mcpServers": {
"playwright": {
"command": "npx",
"args": ["@playwright/mcp@latest"]
},
"playwright-test": {
"command": "npx",
"args": ["playwright", "run-test-mcp-server"]
}
}
}
```
**To disable**: Set `tea_use_mcp_enhancements: false` in `_bmad/bmm/config.yaml` OR remove MCPs from IDE config.
</details>
<details>
<summary><strong>Optional Playwright Utils Integration</strong></summary>
**Open-source Playwright utilities** from SEON Technologies (production-tested, npm published):
- **Package**: `@seontechnologies/playwright-utils` ([npm](https://www.npmjs.com/package/@seontechnologies/playwright-utils) | [GitHub](https://github.com/seontechnologies/playwright-utils))
- **Install**: `npm install -D @seontechnologies/playwright-utils`
**How Playwright Utils Enhances TEA Workflows**:
Provides fixture-based utilities that integrate into TEA's test generation and review workflows:
1. `*framework`:
- Default: Basic Playwright scaffold
- **+ playwright-utils**: Scaffold with api-request, network-recorder, auth-session, burn-in, network-error-monitor fixtures pre-configured
Benefit: Production-ready patterns from day one
2. `*automate`, `*atdd`:
- Default: Standard test patterns
- **+ playwright-utils**: Tests using api-request (schema validation), intercept-network-call (mocking), recurse (polling), log (structured logging), file-utils (CSV/PDF)
Benefit: Advanced patterns without boilerplate
3. `*test-review`:
- Default: Reviews against core knowledge base (21 fragments)
- **+ playwright-utils**: Reviews against expanded knowledge base (32 fragments: 21 core + 11 playwright-utils)
Benefit: Reviews include fixture composition, auth patterns, network recording best practices
4. `*ci`:
- Default: Standard CI workflow
- **+ playwright-utils**: CI workflow with burn-in script (smart test selection) and network-error-monitor integration
Benefit: Faster CI feedback, HTTP error detection
**Utilities available** (10 total): api-request, network-recorder, auth-session, intercept-network-call, recurse, log, file-utils, burn-in, network-error-monitor, fixtures-composition
**Enable during BMAD installation** by answering "Yes" when prompted, or manually set `tea_use_playwright_utils: true` in `_bmad/bmm/config.yaml`.
**To disable**: Set `tea_use_playwright_utils: false` in `_bmad/bmm/config.yaml`.
</details>
<br></br>
| Command | Primary Outputs | Notes | With Playwright MCP Enhancements |
| -------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| `*framework` | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs | Use when no production-ready harness exists | - |
| `*ci` | CI workflow, selective test scripts, secrets checklist | Platform-aware (GitHub Actions default) | - |
| `*test-design` | Combined risk assessment, mitigation plan, and coverage strategy | Risk scoring + optional exploratory mode | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality) |
| `*atdd` | Failing acceptance tests + implementation checklist | TDD red phase + optional recording mode | **+ Recording**: AI generation verified with live browser (accurate selectors from real DOM) |
| `*automate` | Prioritized specs, fixtures, README/script updates, DoD summary | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Pattern fixes enhanced with visual debugging + **+ Recording**: AI verified with live browser |
| `*test-review` | Test quality review report with 0-100 score, violations, fixes | Reviews tests against knowledge base patterns | - |
| `*nfr-assess` | NFR assessment report with actions | Focus on security/performance/reliability | - |
| `*trace` | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision | - |

3
docs/modules/bmm-bmad-method/troubleshooting.md
View File

@ -1,3 +0,0 @@
# BMM Troubleshooting Guide
Common issues and solutions for the BMad Method Module will be listed here as needed.

199
docs/modules/bmm-bmad-method/workflows-analysis.md
View File

@ -1,199 +0,0 @@
# BMM Analysis Workflows (Phase 1)
## Overview
Phase 1 (Analysis) workflows are **optional** exploration and discovery tools that help validate ideas, understand markets, and generate strategic context before planning begins.
**Key principle:** Analysis workflows help you think strategically before committing to implementation. Skip them if your requirements are already clear.
**When to use:** Starting new projects, exploring opportunities, validating market fit, generating ideas, understanding problem spaces.
**When to skip:** Continuing existing projects with clear requirements, well-defined features with known solutions, strict constraints where discovery is complete.
---
## Phase 1 Analysis Workflow Overview
Phase 1 Analysis consists of three categories of optional workflows:
### Discovery & Ideation (Optional)
- **brainstorm-project** - Multi-track solution exploration for software projects
### Research & Validation (Optional)
- **research** - Market, technical, competitive, user, domain, and AI research
- **domain-research** - Industry-specific deep dive research
### Strategic Capture (Recommended for Greenfield)
- **product-brief** - Product vision and strategy definition
These workflows feed into Phase 2 (Planning) workflows, particularly the `prd` workflow.
---
## Quick Reference
| Workflow | Agent | Required | Purpose | Output |
| ---------------------- | ------- | ----------- | -------------------------------------------------------------- | ---------------------------- |
| **brainstorm-project** | Analyst | No | Explore solution approaches and architectures | Solution options + rationale |
| **research** | Analyst | No | Multi-type research (market/technical/competitive/user/domain) | Research reports |
| **product-brief** | Analyst | Recommended | Define product vision and strategy (interactive) | Product Brief document |
---
## Workflow Descriptions
### brainstorm-project
**Purpose:** Generate multiple solution approaches through parallel ideation tracks (architecture, UX, integration, value).
**Agent:** Analyst
**When to Use:**
- Very vague or seed kernal of an idea that needs exploration
- Consider alternatives or enhancements to an idea
- See your idea from different angles and viewpoints
- No idea what you want to build, but want to find some inspiration
---
### research
**Purpose:** Comprehensive multi-type research system consolidating market, technical, competitive, user, and domain analysis.
**Agent:** Analyst
**Research Types:**
| Type | Purpose | Use When |
| --------------- | ------------------------------------------------------ | ----------------------------------- |
| **market** | TAM/SAM/SOM, competitive analysis | Need market viability validation |
| **technical** | Technology evaluation, ADRs | Choosing frameworks/platforms |
| **competitive** | Deep competitor analysis | Understanding competitive landscape |
| **user** | Customer insights, personas, JTBD | Need user understanding |
| **domain** | Industry deep dives, trends | Understanding domain/industry |
| **deep_prompt** | Generate AI research prompts (ChatGPT, Claude, Gemini) | Need deeper AI-assisted research |
**Key Features:**
- Real-time web research
- Multiple analytical frameworks (Porter's Five Forces, SWOT, Technology Adoption Lifecycle)
- Platform-specific optimization for deep_prompt type
- Configurable research depth (quick/standard/comprehensive)
**Example (market):** "SaaS project management tool" → TAM $50B, SAM $5B, SOM $50M, top competitors (Asana, Monday), positioning recommendation.
---
### product-brief
**Purpose:** Interactive product brief creation that guides strategic product vision definition.
**Agent:** Analyst
**When to Use:**
- Starting new product/major feature initiative
- Aligning stakeholders before detailed planning
- Transitioning from exploration to strategy
- Need executive-level product documentation
**Key Outputs:**
- Executive summary
- Problem statement with evidence
- Proposed solution and differentiators
- Target users (segmented)
- MVP scope (ruthlessly defined)
- Financial impact and ROI
- Strategic alignment
- Risks and open questions
**Integration:** Feeds directly into PRD workflow (Phase 2).
---
## Decision Guide
### Starting a Software Project
```
brainstorm-project (if unclear) → research (market/technical) → product-brief → Phase 2 (prd)
```
### Validating an Idea
```
research (market type) → product-brief → Phase 2
```
### Technical Decision Only
```
research (technical type) → Use findings in Phase 3 (architecture)
```
### Understanding Market
```
research (market/competitive type) → product-brief → Phase 2
```
### Domain Research for Complex Industries
```
domain-research → research (compliance/regulatory) → product-brief → Phase 2
```
---
## Integration with Phase 2 (Planning)
Analysis outputs feed directly into Planning:
| Analysis Output | Planning Input |
| --------------------------- | -------------------------- |
| product-brief.md | **prd** workflow |
| market-research.md | **prd** context |
| domain-research.md | **prd** context |
| technical-research.md | **architecture** (Phase 3) |
| competitive-intelligence.md | **prd** positioning |
Planning workflows automatically load these documents if they exist in the output folder.
## Common Patterns
### Greenfield Software (Full Analysis)
```
1. brainstorm-project - explore approaches
2. research (market/technical/domain) - validate viability
3. product-brief - capture strategic vision
4. → Phase 2: prd
```
### Skip Analysis (Clear Requirements)
```
→ Phase 2: prd or tech-spec directly
```
### Technical Research Only
```
1. research (technical) - evaluate technologies
2. → Phase 3: architecture (use findings in ADRs)
```
---
## Related Documentation
- [Phase 2: Planning Workflows](../../../../docs/modules/bmm-bmad-method/workflows-planning.md) - Next phase
- [Phase 3: Solutioning Workflows](../../../../docs/modules/bmm-bmad-method/workflows-solutioning.md)
- [Phase 4: Implementation Workflows](../../../../docs/modules/bmm-bmad-method/workflows-implementation.md)
- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding project complexity
- [Agents Guide](../../../../docs/modules/bmm-bmad-method/agents-guide.md) - Complete agent reference

211
docs/modules/bmm-bmad-method/workflows-implementation.md
View File

@ -1,211 +0,0 @@
# BMM Implementation Workflows (Phase 4)
## Overview
Phase 4 (Implementation) workflows manage the iterative sprint-based development cycle using a **story-centric workflow** where each story moves through a defined lifecycle from creation to completion.
**Key principle:** One story at a time, move it through the entire lifecycle before starting the next.
---
## Complete Workflow Context
Phase 4 is the final phase of the BMad Method workflow. To see how implementation fits into the complete methodology:
The BMad Method consists of four phases working in sequence:
1. **Phase 1 (Analysis)** - Optional exploration and discovery workflows
2. **Phase 2 (Planning)** - Required requirements definition using scale-adaptive system
3. **Phase 3 (Solutioning)** - Technical architecture and design decisions
4. **Phase 4 (Implementation)** - Iterative sprint-based development with story-centric workflow
Phase 4 focuses on the iterative epic and story cycles where stories are implemented, reviewed, and completed one at a time.
For a visual representation of the complete workflow, see: [workflow-method-greenfield.excalidraw](./images/workflow-method-greenfield.excalidraw)
---
## Quick Reference
| Workflow | Agent | When | Purpose |
| ------------------- | ----- | --------------------- | ------------------------------------- |
| **sprint-planning** | SM | Once at Phase 4 start | Initialize sprint tracking file |
| **create-story** | SM | Per story | Create next story from epic backlog |
| **dev-story** | DEV | Per story | Implement story with tests |
| **code-review** | DEV | Per story | Senior dev quality review |
| **retrospective** | SM | After epic complete | Review lessons and extract insights |
| **correct-course** | SM | When issues arise | Handle significant mid-sprint changes |
---
## Agent Roles
### SM (Scrum Master) - Primary Implementation Orchestrator
**Workflows:** sprint-planning, create-story, retrospective, correct-course
**Responsibilities:**
- Initialize and maintain sprint tracking
- Create stories from epic backlog
- Handle course corrections when issues arise
- Facilitate retrospectives after epic completion
- Orchestrate overall implementation flow
### DEV (Developer) - Implementation and Quality
**Workflows:** dev-story, code-review
**Responsibilities:**
- Implement stories with tests
- Perform senior developer code reviews
- Ensure quality and adherence to standards
- Complete story implementation lifecycle
---
## Story Lifecycle States
Stories move through these states in the sprint status file:
1. **TODO** - Story identified but not started
2. **IN PROGRESS** - Story being implemented (create-story → dev-story)
3. **READY FOR REVIEW** - Implementation complete, awaiting code review
4. **DONE** - Accepted and complete
---
## Typical Sprint Flow
### Sprint 0 (Planning Phase)
- Complete Phases 1-3 (Analysis, Planning, Solutioning)
- PRD/GDD + Architecture complete
- **V6: Epics+Stories created via create-epics-and-stories workflow (runs AFTER architecture)**
### Sprint 1+ (Implementation Phase)
**Start of Phase 4:**
1. SM runs `sprint-planning` (once)
**Per Epic:**
- Epic context and stories are already prepared from Phase 3
**Per Story (repeat until epic complete):**
1. SM runs `create-story`
2. DEV runs `dev-story`
3. (Optional) TEA runs `*automate` to generate or expand guardrail tests
4. DEV runs `code-review`
5. If code review fails: DEV fixes issues in `dev-story`, then re-runs `code-review`
**After Epic Complete:**
- SM runs `retrospective`
- Move to next epic
**As Needed:**
- Run `sprint-status` anytime in Phase 4 to inspect sprint-status.yaml and get the next implementation command
- Run `workflow-status` for cross-phase routing and project-level paths
- Run `correct-course` if significant changes needed
---
## Key Principles
### One Story at a Time
Complete each story's full lifecycle before starting the next. This prevents context switching and ensures quality.
### Quality Gates
Every story goes through `code-review` before being marked done. No exceptions.
### Continuous Tracking
The `sprint-status.yaml` file is the single source of truth for all implementation progress.
---
### (BMad Method / Enterprise)
```
PRD (PM) → Architecture (Architect)
→ create-epics-and-stories (PM) ← V6: After architecture!
→ implementation-readiness (Architect)
→ sprint-planning (SM, once)
→ [Per Epic]:
→ story loop (SM/DEV)
→ retrospective (SM)
→ [Next Epic]
Current Phase: 4 (Implementation)
Current Epic: Epic 1 (Authentication)
Current Sprint: Sprint 1
Next Story: Story 1.3 (Email Verification)
Status: TODO
Dependencies: Story 1.2 (DONE) ✅
**Recommendation:** Run `create-story` to generate Story 1.3
After create-story:
1. Run dev-story
2. Run code-review
3. Update sprint-status.yaml to mark story done
```
See: [workflow-status instructions](../workflows/workflow-status/instructions.md)
---
### document-project
**Purpose:** Analyze and document brownfield projects by scanning codebase, architecture, and patterns.
**Agent:** Analyst
**Duration:** 1-3 hours
**When to Use:** Brownfield projects without documentation
**How It Works:**
1. Scans codebase structure
2. Identifies architecture patterns
3. Documents technology stack
4. Creates reference documentation
5. Generates PRD-like document from existing code
**Output:** `project-documentation-{date}.md`
**When to Run:**
- Before starting work on legacy project
- When inheriting undocumented codebase
- Creating onboarding documentation
See: [document-project reference](../../reference/workflows/index.md)
## Related Documentation
- [Phase 1: Analysis Workflows](../../how-to/workflows/run-brainstorming-session.md)
- [Phase 2: Planning Workflows](../../how-to/workflows/create-prd.md)
- [Phase 3: Solutioning Workflows](../../how-to/workflows/create-architecture.md)
## Troubleshooting
**Q: Which workflow should I run next?**
A: Run `workflow-status` - it reads the sprint status file and tells you exactly what to do. During implementation (Phase 4) run `sprint-status` (fast check against sprint-status.yaml).
**Q: Story needs significant changes mid-implementation?**
A: Run `correct-course` to analyze impact and route appropriately.
**Q: Can I work on multiple stories in parallel?**
A: Not recommended. Complete one story's full lifecycle before starting the next. Prevents context switching and ensures quality.
**Q: What if code review finds issues?**
A: DEV runs `dev-story` to make fixes, re-runs tests, then runs `code-review` again until it passes.
_Phase 4 Implementation - One story at a time, done right._

89
docs/modules/bmm-bmad-method/workflows-planning.md
View File

@ -1,89 +0,0 @@
# BMM Planning Workflows (Phase 2)
## Phase 2 Planning Workflow Overview
## Quick Reference
| Workflow | Agent | Track | Purpose |
| -------------------- | ----------- | ----------------------- | ------------------------------------- |
| **prd** | PM | BMad Method, Enterprise | Strategic PRD with FRs/NFRs |
| **create-ux-design** | UX Designer | BMad Method, Enterprise | Optional UX specification (after PRD) |
### prd (Product Requirements Document)
**Purpose:** Strategic PRD with Functional Requirements (FRs) and Non-Functional Requirements (NFRs) for software products (BMad Method track).
**Agent:** PM (with Architect and Analyst support)
**When to Use:**
- Medium to large feature sets
- Multi-screen user experiences
- Complex business logic
- Multiple system integrations
- Phased delivery required
**Scale-Adaptive Structure:**
- **Light:** Focused FRs/NFRs, simplified analysis (10-15 pages)
- **Standard:** Comprehensive FRs/NFRs, thorough analysis (20-30 pages)
- **Comprehensive:** Extensive FRs/NFRs, multi-phase, stakeholder analysis (30-50+ pages)
**Key Outputs:**
- PRD.md (complete requirements with FRs and NFRs)
**Note:** V6 improvement - PRD focuses on WHAT to build (requirements). Epic+Stories are created AFTER architecture via `create-epics-and-stories` workflow for better quality.
**Integration:** Feeds into Architecture (Phase 3)
**Example:** E-commerce checkout → PRD with 15 FRs (user account, cart management, payment flow) and 8 NFRs (performance, security, scalability).
---
### create-ux-design (UX Design)
**Purpose:** UX specification for projects where user experience is the primary differentiator (BMad Method track).
**Agent:** UX Designer
**When to Use:**
- UX is primary competitive advantage
- Complex user workflows needing design thinking
- Innovative interaction patterns
- Design system creation
- Accessibility-critical experiences
**Collaborative Approach:**
1. Visual exploration (generate multiple options)
2. Informed decisions (evaluate with user needs)
3. Collaborative design (refine iteratively)
4. Living documentation (evolves with project)
**Key Outputs:**
- ux-spec.md (complete UX specification)
- User journeys
- Wireframes and mockups
- Interaction specifications
- Design system (components, patterns, tokens)
- Epic breakdown (UX stories)
**Integration:** Feeds PRD or updates epics, then Architecture (Phase 3)
**Example:** Dashboard redesign → Card-based layout with split-pane toggle, 5 card components, 12 color tokens, responsive grid, 3 epics (Layout, Visualization, Accessibility).
## Best Practices
### 1. Do Product Brief from Phase 1 to kickstart the PRD for better results
### 2. Focus on "What" Not "How"
Planning defines **what** to build and **why**. Leave **how** (technical design) to Phase 3 (Solutioning).
### 3. Document-Project First for Brownfield
Always run `document-project` before planning brownfield projects. AI agents need existing codebase context and will make a large quality difference. If you are adding a small addition to an existing project, you might want to consider instead after using document-project to use the quick flow solo dev process instead.

509
docs/modules/bmm-bmad-method/workflows-solutioning.md
View File

@ -1,509 +0,0 @@
# BMM Solutioning Workflows (Phase 3)
## Overview
Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into **how** to build it (technical design). This phase prevents agent conflicts in multi-epic projects by documenting architectural decisions before implementation begins.
**Key principle:** Make technical decisions explicit and documented so all agents implement consistently. Prevent one agent choosing REST while another chooses GraphQL.
**Required for:** BMad Method (complex projects), Enterprise Method
**Optional for:** BMad Method (simple projects), Quick Flow (skip entirely)
---
## Phase 3 Solutioning Workflow Overview
Phase 3 Solutioning has different paths based on the planning track selected:
### Quick Flow Path
- From Planning: tech-spec complete
- Action: Skip Phase 3 entirely
- Next: Phase 4 (Implementation)
### BMad Method & Enterprise Path
- From Planning: PRD with FRs/NFRs complete
- Optional: create-ux-design (if UX is critical)
- Required: architecture - System design with ADRs
- Required: create-epics-and-stories - Break requirements into implementable stories
- Required: implementation-readiness - Gate check validation
- Enterprise additions: Optional security-architecture and devops-strategy (future workflows)
### Gate Check Results
- **PASS** - All criteria met, proceed to Phase 4
- **CONCERNS** - Minor gaps identified, proceed with caution
- **FAIL** - Critical issues, must resolve before Phase 4
---
## Quick Reference
| Workflow | Agent | Track | Purpose |
| ---------------------------- | ----------- | ------------------------ | -------------------------------------------- |
| **create-ux-design** | UX Designer | BMad Method, Enterprise | Optional UX design (after PRD, before arch) |
| **architecture** | Architect | BMad Method, Enterprise | Technical architecture and design decisions |
| **create-epics-and-stories** | PM | BMad Method, Enterprise | Break FRs/NFRs into epics after architecture |
| **implementation-readiness** | Architect | BMad Complex, Enterprise | Validate planning/solutioning completeness |
**When to Skip Solutioning:**
- **Quick Flow:** Simple changes don't need architecture → Skip to Phase 4
**When Solutioning is Required:**
- **BMad Method:** Multi-epic projects need architecture to prevent conflicts
- **Enterprise:** Same as BMad Method, plus optional extended workflows (test architecture, security architecture, devops strategy) added AFTER architecture but BEFORE gate check
---
## Why Solutioning Matters
### The Problem Without Solutioning
```
Agent 1 implements Epic 1 using REST API
Agent 2 implements Epic 2 using GraphQL
Result: Inconsistent API design, integration nightmare
```
### The Solution With Solutioning
```
architecture workflow decides: "Use GraphQL for all APIs"
All agents follow architecture decisions
Result: Consistent implementation, no conflicts
```
### Solutioning vs Planning
| Aspect | Planning (Phase 2) | Solutioning (Phase 3) |
| -------- | ----------------------- | --------------------------------- |
| Question | What and Why? | How? Then What units of work? |
| Output | FRs/NFRs (Requirements) | Architecture + Epics/Stories |
| Agent | PM | Architect → PM |
| Audience | Stakeholders | Developers |
| Document | PRD (FRs/NFRs) | Architecture + Epic Files |
| Level | Business logic | Technical design + Work breakdown |
---
## Workflow Descriptions
### architecture
**Purpose:** Make technical decisions explicit to prevent agent conflicts. Produces decision-focused architecture document optimized for AI consistency.
**Agent:** Architect
**When to Use:**
- Multi-epic projects (BMad Complex, Enterprise)
- Cross-cutting technical concerns
- Multiple agents implementing different parts
- Integration complexity exists
- Technology choices need alignment
**When to Skip:**
- Quick Flow (simple changes)
- BMad Method Simple with straightforward tech stack
- Single epic with clear technical approach
**Adaptive Conversation Approach:**
This is NOT a template filler. The architecture workflow:
1. **Discovers** technical needs through conversation
2. **Proposes** architectural options with trade-offs
3. **Documents** decisions that prevent agent conflicts
4. **Focuses** on decision points, not exhaustive documentation
**Key Outputs:**
**architecture.md** containing:
1. **Architecture Overview** - System context, principles, style
2. **System Architecture** - High-level diagram, component interactions, communication patterns
3. **Data Architecture** - Database design, state management, caching, data flow
4. **API Architecture** - API style (REST/GraphQL/gRPC), auth, versioning, error handling
5. **Frontend Architecture** (if applicable) - Framework, state management, component architecture, routing
6. **Integration Architecture** - Third-party integrations, message queuing, event-driven patterns
7. **Security Architecture** - Auth/authorization, data protection, security boundaries
8. **Deployment Architecture** - Deployment model, CI/CD, environment strategy, monitoring
9. **Architecture Decision Records (ADRs)** - Key decisions with context, options, trade-offs, rationale
10. **FR/NFR-Specific Guidance** - Technical approach per functional requirement, implementation priorities, dependencies
11. **Standards and Conventions** - Directory structure, naming conventions, code organization, testing
**ADR Format (Brief):**
```markdown
## ADR-001: Use GraphQL for All APIs
**Status:** Accepted | **Date:** 2025-11-02
**Context:** PRD requires flexible querying across multiple epics
**Decision:** Use GraphQL for all client-server communication
**Options Considered:**
1. REST - Familiar but requires multiple endpoints
2. GraphQL - Flexible querying, learning curve
3. gRPC - High performance, poor browser support
**Rationale:**
- PRD requires flexible data fetching (Epic 1, 3)
- Mobile app needs bandwidth optimization (Epic 2)
- Team has GraphQL experience
**Consequences:**
- Positive: Flexible querying, reduced versioning
- Negative: Caching complexity, N+1 query risk
- Mitigation: Use DataLoader for batching
**Implications for FRs:**
- FR-001: User Management → GraphQL mutations
- FR-002: Mobile App → Optimized queries
```
**Example:** E-commerce platform → Monolith + PostgreSQL + Redis + Next.js + GraphQL, with ADRs explaining each choice and FR/NFR-specific guidance.
**Integration:** Feeds into create-epics-and-stories workflow. Architecture provides the technical context needed for breaking FRs/NFRs into implementable epics and stories. All dev agents reference architecture during Phase 4 implementation.
---
### create-epics-and-stories
**Purpose:** Transform PRD's functional and non-functional requirements into bite-sized stories organized into deliverable functional epics. This workflow runs AFTER architecture so epics/stories are informed by technical decisions.
**Agent:** PM (Product Manager)
**When to Use:**
- After architecture workflow completes
- When PRD contains FRs/NFRs ready for implementation breakdown
- Before implementation-readiness gate check
**Key Inputs:**
- PRD (FRs/NFRs) from Phase 2 Planning
- architecture.md with ADRs and technical decisions
- Optional: UX design artifacts
**Why After Architecture:**
The create-epics-and-stories workflow runs AFTER architecture because:
1. **Informed Story Sizing:** Architecture decisions (database choice, API style, etc.) affect story complexity
2. **Dependency Awareness:** Architecture reveals technical dependencies between stories
3. **Technical Feasibility:** Stories can be properly scoped knowing the tech stack
4. **Consistency:** All stories align with documented architectural patterns
**Key Outputs:**
Epic files (one per epic) containing:
1. Epic objective and scope
2. User stories with acceptance criteria
3. Story priorities (P0/P1/P2/P3)
4. Dependencies between stories
5. Technical notes referencing architecture decisions
**Example:** E-commerce PRD with FR-001 (User Registration), FR-002 (Product Catalog) → Epic 1: User Management (3 stories), Epic 2: Product Display (4 stories), each story referencing relevant ADRs.
---
### implementation-readiness
**Purpose:** Systematically validate that planning and solutioning are complete and aligned before Phase 4 implementation. Ensures PRD, architecture, and epics are cohesive with no gaps.
**Agent:** Architect
**When to Use:**
- **Always** before Phase 4 for BMad Complex and Enterprise projects
- After create-epics-and-stories workflow completes
- Before sprint-planning workflow
- When stakeholders request readiness check
**When to Skip:**
- Quick Flow (no solutioning)
- BMad Simple (no gate check required)
**Purpose of Gate Check:**
**Prevents:**
- ❌ Architecture doesn't address all FRs/NFRs
- ❌ Epics conflict with architecture decisions
- ❌ Requirements ambiguous or contradictory
- ❌ Missing critical dependencies
**Ensures:**
- ✅ PRD → Architecture → Epics alignment
- ✅ All epics have clear technical approach
- ✅ No contradictions or gaps
- ✅ Team ready to implement
**Check Criteria:**
**PRD/GDD Completeness:**
- Problem statement clear and evidence-based
- Success metrics defined
- User personas identified
- Functional requirements (FRs) complete
- Non-functional requirements (NFRs) specified
- Risks and assumptions documented
**Architecture Completeness:**
- System architecture defined
- Data architecture specified
- API architecture decided
- Key ADRs documented
- Security architecture addressed
- FR/NFR-specific guidance provided
- Standards and conventions defined
**Epic/Story Completeness:**
- All PRD features mapped to stories
- Stories have acceptance criteria
- Stories prioritized (P0/P1/P2/P3)
- Dependencies identified
- Story sequencing logical
**Alignment Checks:**
- Architecture addresses all PRD FRs/NFRs
- Epics align with architecture decisions
- No contradictions between epics
- NFRs have technical approach
- Integration points clear
**Gate Decision Logic:**
**✅ PASS**
- All critical criteria met
- Minor gaps acceptable with documented plan
- **Action:** Proceed to Phase 4
**⚠️ CONCERNS**
- Some criteria not met but not blockers
- Gaps identified with clear resolution path
- **Action:** Proceed with caution, address gaps in parallel
**❌ FAIL**
- Critical gaps or contradictions
- Architecture missing key decisions
- Epics conflict with PRD/architecture
- **Action:** BLOCK Phase 4, resolve issues first
**Key Outputs:**
**implementation-readiness.md** containing:
1. Executive Summary (PASS/CONCERNS/FAIL)
2. Completeness Assessment (scores for PRD, Architecture, Epics)
3. Alignment Assessment (PRD↔Architecture, Architecture↔Epics/Stories, cross-epic consistency)
4. Quality Assessment (story quality, dependencies, risks)
5. Gaps and Recommendations (critical/minor gaps, remediation)
6. Gate Decision with rationale
7. Next Steps
**Example:** E-commerce platform → CONCERNS ⚠️ due to missing security architecture and undefined payment gateway. Recommendation: Complete security section and add payment gateway ADR before proceeding.
---
## Integration with Planning and Implementation
### Planning → Solutioning Flow
**Quick Flow:**
```
Planning (tech-spec by PM)
→ Skip Solutioning
→ Phase 4 (Implementation)
```
**BMad Method:**
```
Planning (prd by PM - FRs/NFRs only)
→ Optional: create-ux-design (UX Designer)
→ architecture (Architect)
→ create-epics-and-stories (PM)
→ implementation-readiness (Architect)
→ Phase 4 (Implementation)
```
**Enterprise:**
```
Planning (prd by PM - FRs/NFRs only)
→ Optional: create-ux-design (UX Designer)
→ architecture (Architect)
→ Optional: security-architecture (Architect, future)
→ Optional: devops-strategy (Architect, future)
→ create-epics-and-stories (PM)
→ implementation-readiness (Architect)
→ Phase 4 (Implementation)
```
**Note on TEA (Test Architect):** TEA is fully operational with 8 workflows across all phases. TEA validates architecture testability during Phase 3 reviews but does not have a dedicated solutioning workflow. TEA's primary setup occurs after architecture in Phase 3 (`*framework`, `*ci`, system-level `*test-design`), with optional Phase 2 baseline `*trace`. Testing execution happens in Phase 4 (`*atdd`, `*automate`, `*test-review`, `*trace`, `*nfr-assess`).
**Note:** Enterprise uses the same planning and architecture as BMad Method. The only difference is optional extended workflows added AFTER architecture but BEFORE create-epics-and-stories.
### Solutioning → Implementation Handoff
**Documents Produced:**
1. **architecture.md** → Guides all dev agents during implementation
2. **ADRs** (in architecture) → Referenced by agents for technical decisions
3. **Epic files** (from create-epics-and-stories) → Work breakdown into implementable units
4. **implementation-readiness.md** → Confirms readiness for Phase 4
**How Implementation Uses Solutioning:**
- **sprint-planning** - Loads architecture and epic files for sprint organization
- **dev-story** - References architecture decisions and ADRs
- **code-review** - Validates code follows architectural standards
---
## Best Practices
### 1. Make Decisions Explicit
Don't leave technology choices implicit. Document decisions with rationale in ADRs so agents understand context.
### 2. Focus on Agent Conflicts
Architecture's primary job is preventing conflicting implementations. Focus on cross-cutting concerns.
### 3. Use ADRs for Key Decisions
Every significant technology choice should have an ADR explaining "why", not just "what".
### 4. Keep It Practical
Don't over-architect simple projects. BMad Simple projects need simple architecture.
### 5. Run Gate Check Before Implementation
Catching alignment issues in solutioning is 10× faster than discovering them mid-implementation.
### 6. Iterate Architecture
Architecture documents are living. Update them as you learn during implementation.
---
## Decision Guide
### Quick Flow
- **Planning:** tech-spec (PM)
- **Solutioning:** Skip entirely
- **Implementation:** sprint-planning → dev-story
### BMad Method
- **Planning:** prd (PM) - creates FRs/NFRs only, NOT epics
- **Solutioning:** Optional UX → architecture (Architect) → create-epics-and-stories (PM) → implementation-readiness (Architect)
- **Implementation:** sprint-planning → create-story → dev-story
### Enterprise
- **Planning:** prd (PM) - creates FRs/NFRs only (same as BMad Method)
- **Solutioning:** Optional UX → architecture (Architect) → Optional extended workflows (security-architecture, devops-strategy) → create-epics-and-stories (PM) → implementation-readiness (Architect)
- **Implementation:** sprint-planning → create-story → dev-story
**Key Difference:** Enterprise adds optional extended workflows AFTER architecture but BEFORE create-epics-and-stories. Everything else is identical to BMad Method.
**Note:** TEA (Test Architect) operates across all phases and validates architecture testability but is not a Phase 3-specific workflow. See [Test Architecture Guide](../../explanation/features/tea-overview.md) for TEA's full lifecycle integration.
---
## Common Anti-Patterns
### ❌ Skipping Architecture for Complex Projects
"Architecture slows us down, let's just start coding."
**Result:** Agent conflicts, inconsistent design, massive rework
### ❌ Over-Engineering Simple Projects
"Let me design this simple feature like a distributed system."
**Result:** Wasted time, over-engineering, analysis paralysis
### ❌ Template-Driven Architecture
"Fill out every section of this architecture template."
**Result:** Documentation theater, no real decisions made
### ❌ Skipping Gate Check
"PRD and architecture look good enough, let's start."
**Result:** Gaps discovered mid-sprint, wasted implementation time
### ✅ Correct Approach
- Use architecture for BMad Method and Enterprise (both required)
- Focus on decisions, not documentation volume
- Enterprise: Add optional extended workflows (test/security/devops) after architecture
- Always run gate check before implementation
---
## Related Documentation
- [Phase 2: Planning Workflows](../../../../docs/modules/bmm-bmad-method/workflows-planning.md) - Previous phase
- [Phase 4: Implementation Workflows](../../../../docs/modules/bmm-bmad-method/workflows-implementation.md) - Next phase
- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding tracks
- [Agents Guide](../../../../docs/modules/bmm-bmad-method/agents-guide.md) - Complete agent reference
---
## Troubleshooting
**Q: Do I always need architecture?**
A: No. Quick Flow skips it. BMad Method and Enterprise both require it.
**Q: How do I know if I need architecture?**
A: If you chose BMad Method or Enterprise track in planning (workflow-init), you need architecture to prevent agent conflicts.
**Q: What's the difference between architecture and tech-spec?**
A: Tech-spec is implementation-focused for simple changes. Architecture is system design for complex multi-epic projects.
**Q: Can I skip gate check?**
A: Only for Quick Flow. BMad Method and Enterprise both require gate check before Phase 4.
**Q: What if gate check fails?**
A: Resolve the identified gaps (missing architecture sections, conflicting requirements) and re-run gate check.
**Q: How long should architecture take?**
A: BMad Method: 1-2 days for architecture. Enterprise: 2-3 days total (1-2 days architecture + 0.5-1 day optional extended workflows). If taking longer, you may be over-documenting.
**Q: Do ADRs need to be perfect?**
A: No. ADRs capture key decisions with rationale. They should be concise (1 page max per ADR).
**Q: Can I update architecture during implementation?**
A: Yes! Architecture is living. Update it as you learn. Use `correct-course` workflow for significant changes.
---
_Phase 3 Solutioning - Technical decisions before implementation._

50
docs/modules/core/party-mode.md
View File

@ -1,50 +0,0 @@
# Party Mode
**Orchestrate dynamic multi-agent conversations with your entire BMAD team.**
Party Mode brings together all your installed BMAD agents for collaborative discussions. Instead of working with a single agent, you can engage with multiple specialized perspectives simultaneously—each agent maintaining their unique personality, expertise, and communication style.
---
## When to Use It
- Exploring complex topics that would benefit from diverse expert perspectives
- Brainstorming with agents who can build on each other's ideas
- Getting a comprehensive view across multiple domains (technical, business, creative, strategic)
- Enjoying dynamic, agent-to-agent conversations where experts challenge and complement each other
---
## How It Works
1. Party Mode loads your complete agent roster and introduces the available team members
2. You present a topic or question
3. The facilitator intelligently selects 2-3 most relevant agents based on expertise needed
4. Agents respond in character, can reference each other, and engage in natural cross-talk
5. The conversation continues until you choose to exit
---
## Key Features
- **Intelligent agent selection** — The system analyzes your topic and selects the most relevant agents based on their expertise, capabilities, and principles
- **Authentic personalities** — Each agent maintains their unique voice, communication style, and domain knowledge throughout the conversation
- **Natural cross-talk** — Agents can reference each other, build on previous points, ask questions, and even respectfully disagree
- **Optional TTS integration** — Each agent response can be read aloud with voice configurations matching their personalities
- **Graceful exit** — Sessions conclude with personalized farewells from participating agents
---
## Workflow Integration
Party Mode is a core workflow designed to be invoked and configured by other modules. When called from another workflow, it accepts contextual parameters:
| Parameter | Description |
|-----------|-------------|
| **Topic focus** | Prebias the discussion toward a specific domain or question |
| **Additional personas** | Inject expert agents into the roster at runtime for specialized perspectives |
| **Participation constraints** | Limit which agents can contribute based on relevance |
### Example
A medical module workflow could invoke Party Mode with expert doctor personas added to the roster, and the conversation pre-focused on a specific diagnosis or treatment decision. The agents would then discuss the medical case with appropriate domain expertise while maintaining their distinct personalities and perspectives.

2
docs/modules/bmm-bmad-method/quick-flow-solo-dev.md → docs/reference/agents/barry-quick-flow.md
View File

@ -309,7 +309,7 @@ Implement OAuth 2.0 authentication with JWT tokens and role-based access control
- **[Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md)** - Getting started with BMM
- **[Agents Guide](../../explanation/core-concepts/agent-roles.md)** - Complete agent reference
- **[Scale Adaptive System](./scale-adaptive-system.md)** - Understanding development tracks
- **[Four Phases](../../explanation/architecture/four-phases.md)** - Understanding development tracks
- **[Workflow Implementation](../../how-to/workflows/run-sprint-planning.md)** - Implementation workflows
- **[Party Mode](../../explanation/features/party-mode.md)** - Multi-agent collaboration

0
docs/modules/bmgd-bmad-game-dev/agents-guide.md → docs/reference/agents/bmgd-agents.md
View File

74
docs/modules/bmm-bmad-method/agents-guide.md → docs/reference/agents/index.md
View File

@ -1,98 +1,92 @@
# BMM Agents Reference
---
sidebar_label: Agents Reference
description: Complete reference for BMad Method agents and their commands
---
Quick reference of what each agent can do based on their available commands.
# Agents Reference
Quick reference of all BMad Method agents and their available commands.
---
## Analyst (Mary) | `/bmad:bmm:agents:analyst`
## Analyst (Mary)
Business analysis and research.
**Capabilities:**
**Commands:**
- `*workflow-status` - Get workflow status or initialize tracking
- `*brainstorm-project` - Guided brainstorming session
- `*research` - Market, domain, competitive, or technical research
- `*product-brief` - Create a product brief (input for PRD)
- `*document-project` - Document existing brownfield projects
- Party mode and advanced elicitation
---
## PM (John) | `/bmad:bmm:agents:pm`
## PM (John)
Product requirements and planning.
**Capabilities:**
**Commands:**
- `*workflow-status` - Get workflow status or initialize tracking
- `*create-prd` - Create Product Requirements Document
- `*create-epics-and-stories` - Break PRD into epics and user stories (after Architecture)
- `*implementation-readiness` - Validate PRD, UX, Architecture, Epics alignment
- `*correct-course` - Course correction during implementation
- Party mode and advanced elicitation
---
## Architect (Winston) | `/bmad:bmm:agents:architect`
## Architect (Winston)
System architecture and technical design.
**Capabilities:**
**Commands:**
- `*workflow-status` - Get workflow status or initialize tracking
- `*create-architecture` - Create architecture document to guide development
- `*implementation-readiness` - Validate PRD, UX, Architecture, Epics alignment
- `*create-excalidraw-diagram` - System architecture or technical diagrams
- `*create-excalidraw-dataflow` - Data flow diagrams
- Party mode and advanced elicitation
---
## SM (Bob) | `/bmad:bmm:agents:sm`
## SM (Bob)
Sprint planning and story preparation.
**Capabilities:**
**Commands:**
- `*sprint-planning` - Generate sprint-status.yaml from epic files
- `*create-story` - Create story from epic (prep for development)
- `*validate-create-story` - Validate story quality
- `*epic-retrospective` - Team retrospective after epic completion
- `*correct-course` - Course correction during implementation
- Party mode and advanced elicitation
---
## DEV (Amelia) | `/bmad:bmm:agents:dev`
## DEV (Amelia)
Story implementation and code review.
**Capabilities:**
**Commands:**
- `*dev-story` - Execute story workflow (implementation with tests)
- `*code-review` - Thorough code review
---
## Quick Flow Solo Dev (Barry) | `/bmad:bmm:agents:quick-flow-solo-dev`
## Quick Flow Solo Dev (Barry)
Fast solo development without handoffs.
**Capabilities:**
**Commands:**
- `*create-tech-spec` - Architect technical spec with implementation-ready stories
- `*quick-dev` - Implement tech spec end-to-end solo
- `*code-review` - Review and improve code
---
## TEA (Murat) | `/bmad:bmm:agents:tea`
## TEA (Murat)
Test architecture and quality strategy.
**Capabilities:**
**Commands:**
- `*framework` - Initialize production-ready test framework
- `*atdd` - Generate E2E tests first (before implementation)
- `*automate` - Comprehensive test automation
@ -104,33 +98,31 @@ Test architecture and quality strategy.
---
## UX Designer (Sally) | `/bmad:bmm:agents:ux-designer`
## UX Designer (Sally)
User experience and UI design.
**Capabilities:**
**Commands:**
- `*create-ux-design` - Generate UX design and UI plan from PRD
- `*validate-design` - Validate UX specification and design artifacts
- `*create-excalidraw-wireframe` - Create website or app wireframe
---
## Technical Writer (Paige) | `/bmad:bmm:agents:tech-writer`
## Technical Writer (Paige)
Technical documentation and diagrams.
**Capabilities:**
- `*document-project` - Comprehensive project documentation (brownfield analysis)
- `*generate-mermaid` - Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
**Commands:**
- `*document-project` - Comprehensive project documentation
- `*generate-mermaid` - Generate Mermaid diagrams
- `*create-excalidraw-flowchart` - Process and logic flow visualizations
- `*create-excalidraw-diagram` - System architecture or technical diagrams
- `*create-excalidraw-dataflow` - Data flow visualizations
- `*validate-doc` - Review documentation against standards
- `*improve-readme` - Review and improve README files
- `*explain-concept` - Create clear technical explanations with examples
- `*standards-guide` - Show BMAD documentation standards reference
- `*explain-concept` - Create clear technical explanations
- `*standards-guide` - Show BMAD documentation standards
---
@ -140,5 +132,11 @@ Available to all agents:
- `*menu` - Redisplay menu options
- `*dismiss` - Dismiss agent
- `*party-mode` - Multi-agent collaboration (most agents)
Party mode is available to most agents for multi-agent collaboration.
---
## Related
- [Agent Roles](../../explanation/core-concepts/agent-roles.md) - Understanding agent responsibilities
- [What Are Agents](../../explanation/core-concepts/what-are-agents.md) - Foundational concepts

0
docs/modules/core/core-tasks.md → docs/reference/configuration/core-tasks.md
View File

0
docs/modules/core/global-core-config.md → docs/reference/configuration/global-config.md
View File

81
docs/reference/faq/brownfield-faq.md Normal file
View File

@ -0,0 +1,81 @@
---
sidebar_label: Brownfield
description: Common questions about brownfield development in the BMad Method
---
# Brownfield Development FAQ
Quick answers to common questions about brownfield (existing codebase) development in the BMad Method.
---
## Q: What is brownfield vs greenfield?
**A:**
- **Greenfield:** New project, starting from scratch, clean slate
- **Brownfield:** Existing project, working with established codebase and patterns
## Q: Do I have to run document-project for brownfield?
**A:** Highly recommended, especially if:
- No existing documentation
- Documentation is outdated
- AI agents need context about existing code
- Level 2-4 complexity
You can skip it if you have comprehensive, up-to-date documentation including `docs/index.md`.
## Q: What if I forget to run document-project on brownfield?
**A:** Workflows will lack context about existing code. You may get:
- Suggestions that don't match existing patterns
- Integration approaches that miss existing APIs
- Architecture that conflicts with current structure
Run document-project and restart planning with proper context.
## Q: Can I use Quick Spec Flow for brownfield projects?
**A:** Yes! Quick Spec Flow works great for brownfield. It will:
- Auto-detect your existing stack
- Analyze brownfield code patterns
- Detect conventions and ask for confirmation
- Generate context-rich tech-spec that respects existing code
Perfect for bug fixes and small features in existing codebases.
## Q: How does workflow-init handle brownfield with old planning docs?
**A:** workflow-init asks about YOUR current work first, then uses old artifacts as context:
1. Shows what it found (old PRD, epics, etc.)
2. Asks: "Is this work in progress, previous effort, or proposed work?"
3. If previous effort: Asks you to describe your NEW work
4. Determines level based on YOUR work, not old artifacts
This prevents old Level 3 PRDs from forcing Level 3 workflow for new Level 0 bug fix.
## Q: What if my existing code doesn't follow best practices?
**A:** Quick Spec Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide:
- **Yes** → Maintain consistency with current codebase
- **No** → Establish new standards (document why in tech-spec)
BMM respects your choice - it won't force modernization, but it will offer it.
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Brownfield Guide](../../tutorials/advanced/brownfield-onboarding.md) - Existing codebase workflows
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

67
docs/reference/faq/getting-started-faq.md Normal file
View File

@ -0,0 +1,67 @@
---
sidebar_label: Getting Started
description: Common questions about getting started with the BMad Method
---
# Getting Started FAQ
Quick answers to common questions about getting started with the BMad Method.
---
## Q: Do I always need to run workflow-init?
**A:** No, once you learn the flow you can go directly to workflows. However, workflow-init is helpful because it:
- Determines your project's appropriate level automatically
- Creates the tracking status file
- Routes you to the correct starting workflow
For experienced users: use the [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) to go directly to the right agent/workflow.
## Q: Why do I need fresh chats for each workflow?
**A:** Context-intensive workflows (like brainstorming, PRD creation, architecture design) can cause AI hallucinations if run in sequence within the same chat. Starting fresh ensures the agent has maximum context capacity for each workflow. This is particularly important for:
- Planning workflows (PRD, architecture)
- Analysis workflows (brainstorming, research)
- Complex story implementation
Quick workflows like status checks can reuse chats safely.
## Q: Can I skip workflow-status and just start working?
**A:** Yes, if you already know your project level and which workflow comes next. workflow-status is mainly useful for:
- New projects (guides initial setup)
- When you're unsure what to do next
- After breaks in work (reminds you where you left off)
- Checking overall progress
## Q: What's the minimum I need to get started?
**A:** For the fastest path:
1. Install BMad Method: `npx bmad-method@alpha install`
2. For small changes: Load PM agent → run tech-spec → implement
3. For larger projects: Load PM agent → run prd → architect → implement
## Q: How do I know if I'm in Phase 1, 2, 3, or 4?
**A:** Check your `bmm-workflow-status.md` file (created by workflow-init). It shows your current phase and progress. If you don't have this file, you can also tell by what you're working on:
- **Phase 1** - Brainstorming, research, product brief (optional)
- **Phase 2** - Creating either a PRD or tech-spec (always required)
- **Phase 3** - Architecture design (Level 2-4 only)
- **Phase 4** - Actually writing code, implementing stories
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

57
docs/reference/faq/implementation-faq.md Normal file
View File

@ -0,0 +1,57 @@
---
sidebar_label: Implementation
description: Common questions about implementation in the BMad Method
---
# Implementation FAQ
Quick answers to common questions about implementation in the BMad Method.
---
## Q: Does create-story include implementation context?
**A:** Yes! The create-story workflow generates story files that include implementation-specific guidance, references existing patterns from your documentation, and provides technical context. The workflow loads your architecture, PRD, and existing project documentation to create comprehensive stories. For Quick Flow projects using tech-spec, the tech-spec itself is already comprehensive, so stories can be simpler.
## Q: How do I mark a story as done?
**A:** After dev-story completes and code-review passes:
1. Open `sprint-status.yaml` (created by sprint-planning)
2. Change the story status from `review` to `done`
3. Save the file
## Q: Can I work on multiple stories at once?
**A:** Yes, if you have capacity! Stories within different epics can be worked in parallel. However, stories within the same epic are usually sequential because they build on each other.
## Q: What if my story takes longer than estimated?
**A:** That's normal! Stories are estimates. If implementation reveals more complexity:
1. Continue working until DoD is met
2. Consider if story should be split
3. Document learnings in retrospective
4. Adjust future estimates based on this learning
## Q: When should I run retrospective?
**A:** After completing all stories in an epic (when epic is done). Retrospectives capture:
- What went well
- What could improve
- Technical insights
- Learnings for future epics
Don't wait until project end - run after each epic for continuous improvement.
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

18
docs/reference/faq/index.md Normal file
View File

@ -0,0 +1,18 @@
---
sidebar_label: FAQ
description: Frequently asked questions about the BMad Method
---
# Frequently Asked Questions
Quick answers to common questions about the BMad Method, organized by topic.
## Topics
- [Getting Started](./getting-started-faq.md) - Questions about starting with BMM
- [Levels & Tracks](./levels-and-tracks-faq.md) - Choosing the right level
- [Workflows](./workflows-faq.md) - Workflow and phase questions
- [Planning](./planning-faq.md) - Planning document questions
- [Implementation](./implementation-faq.md) - Implementation questions
- [Brownfield](./brownfield-faq.md) - Existing codebase questions
- [Tools & Advanced](./tools-faq.md) - Tools, IDEs, and advanced topics

59
docs/reference/faq/levels-and-tracks-faq.md Normal file
View File

@ -0,0 +1,59 @@
---
sidebar_label: Levels & Tracks
description: Common questions about choosing the right level for your project
---
# Levels and Tracks FAQ
Quick answers to common questions about choosing the right level for your BMad Method project.
---
## Q: How do I know which level my project is?
**A:** Use workflow-init for automatic detection, or self-assess using these keywords:
- **Level 0:** "fix", "bug", "typo", "small change", "patch" → 1 story
- **Level 1:** "simple", "basic", "small feature", "add" → 2-10 stories
- **Level 2:** "dashboard", "several features", "admin panel" → 5-15 stories
- **Level 3:** "platform", "integration", "complex", "system" → 12-40 stories
- **Level 4:** "enterprise", "multi-tenant", "multiple products" → 40+ stories
When in doubt, start smaller. You can always run create-prd later if needed.
## Q: Can I change levels mid-project?
**A:** Yes! If you started at Level 1 but realize it's Level 2, you can run create-prd to add proper planning docs. The system is flexible - your initial level choice isn't permanent.
## Q: What if workflow-init suggests the wrong level?
**A:** You can override it! workflow-init suggests a level but always asks for confirmation. If you disagree, just say so and choose the level you think is appropriate. Trust your judgment.
## Q: Do I always need architecture for Level 2?
**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD created during planning.
## Q: What's the difference between Level 1 and Level 2?
**A:**
- **Level 1:** 1-10 stories, uses tech-spec (simpler, faster), no architecture
- **Level 2:** 5-15 stories, uses PRD (product-focused), optional architecture
The overlap (5-10 stories) is intentional. Choose based on:
- Need product-level planning? → Level 2
- Just need technical plan? → Level 1
- Multiple epics? → Level 2
- Single epic? → Level 1
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

48
docs/reference/faq/planning-faq.md Normal file
View File

@ -0,0 +1,48 @@
---
sidebar_label: Planning
description: Common questions about planning documents in the BMad Method
---
# Planning Documents FAQ
Quick answers to common questions about planning documents in the BMad Method.
---
## Q: Why no tech-spec at Level 2+?
**A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
- PRD (product vision, functional requirements, non-functional requirements)
- Architecture (system design)
- Epics+Stories (created AFTER architecture is complete)
## Q: Do I need a PRD for a bug fix?
**A:** No! Bug fixes are typically Level 0 (single atomic change). Use Quick Spec Flow:
- Load PM agent
- Run tech-spec workflow
- Implement immediately
PRDs are for Level 2-4 projects with multiple features requiring product-level coordination.
## Q: Can I skip the product brief?
**A:** Yes, product brief is always optional. It's most valuable for:
- Level 3-4 projects needing strategic direction
- Projects with stakeholders requiring alignment
- Novel products needing market research
- When you want to explore solution space before committing
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

249
docs/reference/faq/tools-faq.md Normal file
View File

@ -0,0 +1,249 @@
---
sidebar_label: Tools & Advanced
description: Common questions about tools, IDEs, and advanced topics in the BMad Method
---
# Tools and Advanced FAQ
Quick answers to common questions about tools, IDEs, and advanced topics in the BMad Method.
---
## Tools and Technical
### Q: Why are my Mermaid diagrams not rendering?
**A:** Common issues:
1. Missing language tag: Use ` ```mermaid` not just ` ``` `
2. Syntax errors in diagram (validate at mermaid.live)
3. Tool doesn't support Mermaid (check your Markdown renderer)
All BMM docs use valid Mermaid syntax that should render in GitHub, VS Code, and most IDEs.
### Q: Can I use BMM with GitHub Copilot / Cursor / other AI tools?
**A:** Yes! BMM is complementary. BMM handles:
- Project planning and structure
- Workflow orchestration
- Agent Personas and expertise
- Documentation generation
- Quality gates
Your AI coding assistant handles:
- Line-by-line code completion
- Quick refactoring
- Test generation
Use them together for best results.
### Q: What IDEs/tools support BMM?
**A:** BMM requires tools with **agent mode** and access to **high-quality LLM models** that can load and follow complex workflows, then properly implement code changes.
**Recommended Tools:**
- **Claude Code** - Best choice
- Sonnet 4.5 (excellent workflow following, coding, reasoning)
- Opus (maximum context, complex planning)
- Native agent mode designed for BMM workflows
- **Cursor**
- Supports Anthropic (Claude) and OpenAI models
- Agent mode with composer
- Good for developers who prefer Cursor's UX
- **Windsurf**
- Multi-model support
- Agent capabilities
- Suitable for BMM workflows
**What Matters:**
1. **Agent mode** - Can load long workflow instructions and maintain context
2. **High-quality LLM** - Models ranked high on SWE-bench (coding benchmarks)
3. **Model selection** - Access to Claude Sonnet 4.5, Opus, or GPT-4o class models
4. **Context capacity** - Can handle large planning documents and codebases
**Why model quality matters:** BMM workflows require LLMs that can follow multi-step processes, maintain context across phases, and implement code that adheres to specifications. Tools with weaker models will struggle with workflow adherence and code quality.
### Q: Can I customize agents?
**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `_bmad/_config/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
**Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.
### Q: What happens to my planning docs after implementation?
**A:** Keep them! They serve as:
- Historical record of decisions
- Onboarding material for new team members
- Reference for future enhancements
- Audit trail for compliance
For enterprise projects (Level 4), consider archiving completed planning artifacts to keep workspace clean.
### Q: Can I use BMM for non-software projects?
**A:** BMM is optimized for software development, but the methodology principles (scale-adaptive planning, just-in-time design, context injection) can apply to other complex project types. You'd need to adapt workflows and agents for your domain.
---
## Advanced Questions
### Q: What if my project grows from Level 1 to Level 3?
**A:** Totally fine! When you realize scope has grown:
1. Run create-prd to add product-level planning
2. Run create-architecture for system design
3. Use existing tech-spec as input for PRD
4. Continue with updated level
The system is flexible - growth is expected.
### Q: Can I mix greenfield and brownfield approaches?
**A:** Yes! Common scenario: adding new greenfield feature to brownfield codebase. Approach:
1. Run document-project for brownfield context
2. Use greenfield workflows for new feature planning
3. Explicitly document integration points between new and existing
4. Test integration thoroughly
### Q: How do I handle urgent hotfixes during a sprint?
**A:** Use correct-course workflow or just:
1. Save your current work state
2. Load PM agent → quick tech-spec for hotfix
3. Implement hotfix (Level 0 flow)
4. Deploy hotfix
5. Return to original sprint work
Level 0 Quick Spec Flow is perfect for urgent fixes.
### Q: What if I disagree with the workflow's recommendations?
**A:** Workflows are guidance, not enforcement. If a workflow recommends something that doesn't make sense for your context:
- Explain your reasoning to the agent
- Ask for alternative approaches
- Skip the recommendation if you're confident
- Document why you deviated (for future reference)
Trust your expertise - BMM supports your decisions.
### Q: Can multiple developers work on the same BMM project?
**A:** Yes! But the paradigm is fundamentally different from traditional agile teams.
**Key Difference:**
- **Traditional:** Multiple devs work on stories within one epic (months)
- **Agentic:** Each dev owns complete epics (days)
**In traditional agile:** A team of 5 devs might spend 2-3 months on a single epic, with each dev owning different stories.
**With BMM + AI agents:** A single dev can complete an entire epic in 1-3 days. What used to take months now takes days.
**Team Work Distribution:**
- **Recommended:** Split work by **epic** (not story)
- Each developer owns complete epics end-to-end
- Parallel work happens at epic level
- Minimal coordination needed
**For full-stack apps:**
- Frontend and backend can be separate epics (unusual in traditional agile)
- Frontend dev owns all frontend epics
- Backend dev owns all backend epics
- Works because delivery is so fast
**Enterprise Considerations:**
- Use **git submodules** for BMM installation (not .gitignore)
- Allows personal configurations without polluting main repo
- Teams may use different AI tools (Claude Code, Cursor, etc.)
- Developers may follow different methods or create custom agents/workflows
**Quick Tips:**
- Share `sprint-status.yaml` (single source of truth)
- Assign entire epics to developers (not individual stories)
- Coordinate at epic boundaries, not story level
- Use git submodules for BMM in enterprise settings
### Q: What is party mode and when should I use it?
**A:** Party mode is a unique multi-agent collaboration feature where ALL your installed agents (19+ from BMM, CIS, BMB, custom modules) discuss your challenges together in real-time.
**How it works:**
1. Run `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent)
2. Introduce your topic
3. BMad Master selects 2-3 most relevant agents per message
4. Agents cross-talk, debate, and build on each other's ideas
**Best for:**
- Strategic decisions with trade-offs (architecture choices, tech stack, scope)
- Creative brainstorming (game design, product innovation, UX ideation)
- Cross-functional alignment (epic kickoffs, retrospectives, phase transitions)
- Complex problem-solving (multi-faceted challenges, risk assessment)
**Example parties:**
- **Product Strategy:** PM + Innovation Strategist (CIS) + Analyst
- **Technical Design:** Architect + Creative Problem Solver (CIS) + Game Architect
- **User Experience:** UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
**Why it's powerful:**
- Diverse perspectives (technical, creative, strategic)
- Healthy debate reveals blind spots
- Emergent insights from agent interaction
- Natural collaboration across modules
**For complete documentation:**
👉 **[Party Mode Guide](../../explanation/features/party-mode.md)** - How it works, when to use it, example compositions, best practices
---
## Getting Help
### Q: Where do I get help if my question isn't answered here?
**A:**
1. Search [Complete Documentation](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) for related topics
2. Ask in [Discord Community](https://discord.gg/gk8jAdXWmj) (#general-dev)
3. Open a [GitHub Issue](https://github.com/bmad-code-org/BMAD-METHOD/issues)
4. Watch [YouTube Tutorials](https://www.youtube.com/@BMadCode)
### Q: How do I report a bug or request a feature?
**A:** Open a GitHub issue at: <https://github.com/bmad-code-org/BMAD-METHOD/issues>
Please include:
- BMM version (check your installed version)
- Steps to reproduce (for bugs)
- Expected vs actual behavior
- Relevant workflow or agent involved
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

69
docs/reference/faq/workflows-faq.md Normal file
View File

@ -0,0 +1,69 @@
---
sidebar_label: Workflows
description: Common questions about BMad Method workflows and phases
---
# Workflows FAQ
Quick answers to common questions about BMad Method workflows and phases.
---
## Q: What's the difference between workflow-status and workflow-init?
**A:**
- **workflow-status:** Checks existing status and tells you what's next (use when continuing work)
- **workflow-init:** Creates new status file and sets up project (use when starting new project)
If status file exists, use workflow-status. If not, use workflow-init.
## Q: Can I skip Phase 1 (Analysis)?
**A:** Yes! Phase 1 is optional for all levels, though recommended for complex projects. Skip if:
- Requirements are clear
- No research needed
- Time-sensitive work
- Small changes (Level 0-1)
## Q: When is Phase 3 (Architecture) required?
**A:**
- **Level 0-1:** Never (skip entirely)
- **Level 2:** Optional (only if system design needed)
- **Level 3-4:** Required (comprehensive architecture mandatory)
## Q: What happens if I skip a recommended workflow?
**A:** Nothing breaks! Workflows are guidance, not enforcement. However, skipping recommended workflows (like architecture for Level 3) may cause:
- Integration issues during implementation
- Rework due to poor planning
- Conflicting design decisions
- Longer development time overall
## Q: How do I know when Phase 3 is complete and I can start Phase 4?
**A:** For Level 3-4, run the implementation-readiness workflow. It validates PRD + Architecture + Epics + UX (optional) are aligned before implementation. Pass the gate check = ready for Phase 4.
## Q: Can I run workflows in parallel or do they have to be sequential?
**A:** Most workflows must be sequential within a phase:
- Phase 1: brainstorm → research → product-brief (optional order)
- Phase 2: PRD must complete before moving forward
- Phase 3: architecture → epics+stories → implementation-readiness (sequential)
- Phase 4: Stories within an epic should generally be sequential, but stories in different epics can be parallel if you have capacity
---
## Related Documentation
- [Quick Start Guide](../../tutorials/getting-started/quick-start-bmm.md) - Get started with BMM
- [Glossary](../glossary/index.md) - Terminology reference
---
**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

12
docs/modules/bmgd-bmad-game-dev/workflows-guide.md → docs/reference/workflows/bmgd-workflows.md
View File

@ -8,7 +8,7 @@ Complete reference for all BMGD workflows organized by development phase.
BMGD workflows are organized into four phases:
![BMGD Workflow Overview](./workflow-overview.jpg)
![BMGD Workflow Overview](../../tutorials/getting-started/images/workflow-overview.jpg)
---
@ -259,7 +259,7 @@ Checks current project status across all phases. Shows completed documents, curr
## Quick-Flow Workflows
Fast-track workflows that skip full planning phases. See **[Quick-Flow Guide](../../../../docs/modules/bmgd-bmad-game-dev/quick-flow-guide.md)** for detailed usage.
Fast-track workflows that skip full planning phases. See **[Quick-Flow Guide](../../how-to/workflows/bmgd-quick-flow.md)** for detailed usage.
### Quick-Prototype
@ -457,7 +457,7 @@ This means:
## Next Steps
- **[Quick Start Guide](../../../../docs/modules/bmgd-bmad-game-dev/quick-start.md)** - Get started with BMGD
- **[Quick-Flow Guide](../../../../docs/modules/bmgd-bmad-game-dev/quick-flow-guide.md)** - Rapid prototyping and development
- **[Agents Guide](../../../../docs/modules/bmgd-bmad-game-dev/agents-guide.md)** - Agent reference
- **[Game Types Guide](../../../../docs/modules/bmgd-bmad-game-dev/game-types-guide.md)** - Game type templates
- **[Quick Start Guide](../../tutorials/getting-started/quick-start-bmgd.md)** - Get started with BMGD
- **[Quick-Flow Guide](../../how-to/workflows/bmgd-quick-flow.md)** - Rapid prototyping and development
- **[Agents Guide](../agents/bmgd-agents.md)** - Agent reference
- **[Game Types Guide](../../explanation/game-dev/game-types.md)** - Game type templates

0
docs/modules/core/core-workflows.md → docs/reference/workflows/core-workflows.md
View File

0
docs/modules/bmm-bmad-method/workflow-document-project-reference.md → docs/reference/workflows/document-project.md
View File

17
docs/reference/workflows/index.md Normal file
View File

@ -0,0 +1,17 @@
---
sidebar_label: Workflows
description: Reference documentation for BMad Method workflows
---
# Workflows Reference
Complete reference documentation for all BMad Method workflows.
## Core Workflows
- [Core Workflows](./core-workflows.md) - Domain-agnostic workflows available to all modules
- [Document Project](./document-project.md) - Brownfield project documentation workflow
## Module-Specific Workflows
- [BMGD Workflows](./bmgd-workflows.md) - Game development workflows

53
docs/modules/bmm-bmad-method/brownfield-guide.md → docs/tutorials/advanced/brownfield-onboarding.md
View File

@ -1,23 +1,42 @@
# BMad Method Brownfield Development Guide
---
sidebar_label: Brownfield Onboarding
description: Learn how to use BMad Method on existing codebases
---
## Working on Existing Projects
# Brownfield Development Tutorial
If you have completed your initial PRD on a new project and want to add new features, or if you have a legacy project you are maintaining, you will want to follow the brownfield process.
Learn how to effectively use BMad Method when working on existing projects and legacy codebases.
This document is intentionally brief, focusing only on what differs from the standard greenfield flow.
## What is Brownfield Development?
**Brownfield** refers to working on existing projects with established codebases and patterns, as opposed to **greenfield** which means starting from scratch with a clean slate.
This tutorial covers the essential workflow for onboarding to brownfield projects with BMad Method.
---
## 1. Clean Up Completed Planning Artifacts
## Prerequisites
- BMad Method installed (`npx bmad-method install`)
- An existing codebase you want to work on
- Access to an AI-powered IDE (Claude Code, Cursor, or Windsurf)
---
## Step 1: Clean Up Completed Planning Artifacts
If you have completed all PRD epics and stories through the BMad process, clean up those files. Archive them, delete them, or rely on version history if needed. Do not keep these files in:
- `docs/`
- `_bmad-output/planning-artifacts/`
- `_bmad-output/implementation-artifacts/`
## 2. Maintain Quality Project Documentation
---
## Step 2: Maintain Quality Project Documentation
Your `docs/` folder should contain succinct, well-organized documentation that accurately represents your project:
- Intent and business rationale
- Business rules
- Architecture
@ -25,7 +44,9 @@ Your `docs/` folder should contain succinct, well-organized documentation that a
For complex projects, consider using the `document-project` workflow. It offers runtime variants that will scan your entire project and document its actual current state.
## 3. Initialize for Brownfield Work
---
## Step 3: Initialize for Brownfield Work
Run `workflow-init`. It should recognize you are in an existing project. If not, explicitly clarify that this is brownfield development for a new feature.
@ -41,6 +62,7 @@ You have two primary options depending on the scope of changes:
### During PRD Creation
When creating a brief or jumping directly into the PRD, ensure the agent:
- Finds and analyzes your existing project documentation
- Reads the proper context about your current system
@ -49,6 +71,7 @@ You can guide the agent explicitly, but the goal is to ensure the new feature in
### UX Considerations
UX work is optional. The decision depends not on whether your project has a UX, but on:
- Whether you will be working on UX changes
- Whether significant new UX designs or patterns are needed
@ -57,6 +80,7 @@ If your changes amount to simple updates to existing screens you are happy with,
### Architecture Considerations
When doing architecture, ensure the architect:
- Uses the proper documented files
- Scans the existing codebase
@ -64,15 +88,16 @@ Pay close attention here to prevent reinventing the wheel or making decisions th
---
## 4. Ad-Hoc Changes
## Next Steps
Not everything requires the full BMad method or even quick-flow. For bug fixes, refactorings, or small targeted changes, simply talk to the agent and have it make the changes directly. This is also a good way to learn about your codebase and understand the modifications being made.
- **[Document Existing Project](../../how-to/brownfield/document-existing-project.md)** - How to document your brownfield codebase
- **[Add Feature to Existing Project](../../how-to/brownfield/add-feature-to-existing.md)** - Adding new functionality
- **[Quick Fix in Brownfield](../../how-to/brownfield/quick-fix-in-brownfield.md)** - Bug fixes and ad-hoc changes
- **[Brownfield FAQ](../../reference/faq/brownfield-faq.md)** - Common questions about brownfield development
---
## 5. Learn and Explore
## Related Documentation
Remember, LLMs are excellent at interpreting and analyzing code—whether it was AI-generated or not. Use the agent to:
- Learn about your project
- Understand how things are built
- Explore unfamiliar parts of the codebase
- [Quick Start Guide](../getting-started/quick-start-bmm.md) - Getting started with BMM
- [Quick Spec Flow](../../explanation/features/quick-flow.md) - Fast path for small changes

12
docs/tutorials/advanced/create-custom-agent.md
View File

@ -53,7 +53,7 @@ my-custom-stuff/
└── workflows/ # Optional: custom workflows
```
See [Custom Content Installation](./custom-content-installation.md) for details.
See [Custom Content Installation](../../how-to/installation/install-custom-modules.md) for details.
## Choosing Your Agent Type
@ -144,16 +144,16 @@ If something isn't right:
### Share
Package your agent as a standalone module (see [Installation Guide](../../bmad-core-concepts/installing/)) and share it with your team or the community.
Package your agent as a standalone module (see [Installation Guide](../../how-to/installation/index.md)) and share it with your team or the community.
## Further Reading
- **[Agent Architecture](./index.md)** - Deep technical details on agent types
- **[Agent Customization](../../bmad-core-concepts/agent-customization/)** - Modify agents without editing core files
- **[Custom Content Installation](./custom-content-installation.md)** - Package and distribute your agents
- **[What Are Agents](../../explanation/core-concepts/what-are-agents.md)** - Deep technical details on agent types
- **[Agent Customization](../../how-to/customization/customize-agents.md)** - Modify agents without editing core files
- **[Custom Content Installation](../../how-to/installation/install-custom-modules.md)** - Package and distribute your agents
---
**Ready?** Start the workflow and create your first agent!
[← Back to BMB Documentation](./index.md)
[← Back to Advanced Tutorials](./index.md)

15
docs/tutorials/advanced/index.md Normal file
View File

@ -0,0 +1,15 @@
---
sidebar_label: Advanced Tutorials
description: Advanced tutorials for extending BMad Method
---
# Advanced Tutorials
Deep-dive tutorials for advanced BMad Method usage.
## Available Tutorials
| Tutorial | Description |
|----------|-------------|
| **[Brownfield Onboarding](./brownfield-onboarding.md)** | Integrate BMad into existing projects |
| **[Create Custom Agent](./create-custom-agent.md)** | Build your own AI agents |

0
docs/modules/bmm-bmad-method/images/README.md → docs/tutorials/getting-started/images/workflow-diagrams-README.md
View File

0
docs/modules/bmm-bmad-method/images/workflow-method-greenfield.excalidraw → docs/tutorials/getting-started/images/workflow-method-greenfield.excalidraw
View File

0
docs/modules/bmgd-bmad-game-dev/workflow-overview.jpg → docs/tutorials/getting-started/images/workflow-overview.jpg
View File

Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 200 KiB

After

Width:  |  Height:  |  Size: 200 KiB

101
docs/tutorials/getting-started/installation.md Normal file
View File

@ -0,0 +1,101 @@
---
sidebar_label: Installation
description: Getting started with BMAD installation
---
# Installation Tutorial
Get BMAD up and running in your project with this step-by-step guide.
---
## Prerequisites
Before you begin, ensure you have:
- **Node.js** 20+ (for the installer)
- **Git** (recommended for version control)
- An **AI-powered IDE** or access to Claude/ChatGPT/Gemini
---
## Quick Install
Run the interactive installer:
```bash
npx bmad-method install
```
This will guide you through the installation process interactively.
---
## What the Installer Does
The interactive installer will:
1. **Choose location** - Where to install BMAD files
2. **Select AI tools** - Claude Code, Cursor, Windsurf, etc.
3. **Choose modules** - BMad Method, Creative Intelligence, BMad Builder
4. **Add custom content** - Your own agents, workflows, or modules
5. **Configure settings** - Accept defaults or customize each module
---
## Module Options
During installation, choose which modules to install:
| Module | Description | Best For |
| -------- | -------------------- | ----------------------------------------------------- |
| **BMM** | BMAD Method Core | Software development projects |
| **BMGD** | Game Development | Game projects with specialized workflows |
| **CIS** | Creative Intel Suite | Creativity unlocking, not software dev specific |
| **BMB** | Builder | Creating custom agents and workflows |
---
## Post-Installation Structure
After installation, your project will have:
```
your-project/
├── _bmad/ # BMAD configuration and agents
│ ├── bmm/ # Method module (if installed)
│ ├── bmgd/ # Game dev module (if installed)
│ ├── core/ # Core utilities (always installed)
│ └── {others}/ # Additional modules
├── _bmad-output/ # Default output folder
├── .claude/ # IDE-specific setup (varies)
└── ... your code
```
---
## Upgrading?
If you're upgrading from a previous version, see the [Upgrade Guide](../../how-to/installation/upgrade-to-v6.md).
---
## Next Steps
After installation:
1. **[Quick Start Guide](./quick-start-bmm.md)** - Build your first feature
2. **[Understanding Workflows](../../explanation/core-concepts/what-are-workflows.md)** - Learn the methodology
3. **[Understanding Agents](../../explanation/core-concepts/what-are-agents.md)** - BMAD's core building blocks
---
## Troubleshooting
**"Command not found: npx"**
Install Node.js 20+ from [nodejs.org](https://nodejs.org)
**"Permission denied"**
Run with appropriate permissions or check your npm configuration
For more help, see [Install BMAD](../../how-to/installation/install-bmad.md) or join our [Discord](https://discord.gg/bmad).

22
docs/tutorials/getting-started/quick-start-bmgd.md
View File

@ -158,12 +158,12 @@ BMGD provides six specialized agents:
| Agent | Icon | When to Use |
| --------------------- | ---- | ----------------------------------------- |
| **Game Designer** | 🎲 | Brainstorming, Game Brief, GDD, Narrative |
| **Game Architect** | 🏛️ | Architecture, technical decisions |
| **Game Developer** | 🕹️ | Implementation, code reviews |
| **Game Scrum Master** | 🎯 | Sprint planning, story management |
| **Game QA** | 🧪 | Test framework, test design, automation |
| **Game Solo Dev** | 🎮 | Quick prototyping, indie development |
| **Game Designer** | 🎲 | Brainstorming, Game Brief, GDD, Narrative |
| **Game Architect** | 🏛️ | Architecture, technical decisions |
| **Game Developer** | 🕹️ | Implementation, code reviews |
| **Game Scrum Master** | 🎯 | Sprint planning, story management |
| **Game QA** | 🧪 | Test framework, test design, automation |
| **Game Solo Dev** | 🎮 | Quick prototyping, indie development |
### Typical Flow
@ -239,11 +239,11 @@ Use `party-mode` to get perspectives from multiple agents when facing complex de
## Next Steps
- **[Agents Guide](./agents-guide.md)** - Learn about each agent's capabilities
- **[Workflows Guide](./workflows-guide.md)** - Detailed workflow reference
- **[Quick-Flow Guide](./quick-flow-guide.md)** - Rapid prototyping and development
- **[Game Types Guide](./game-types-guide.md)** - Understand game type templates
- **[Glossary](./glossary.md)** - Game development terminology
- **[Agents Guide](../../reference/agents/bmgd-agents.md)** - Learn about each agent's capabilities
- **[Workflows Guide](../../reference/workflows/bmgd-workflows.md)** - Detailed workflow reference
- **[Quick-Flow Guide](../../how-to/workflows/bmgd-quick-flow.md)** - Rapid prototyping and development
- **[Game Types Guide](../../explanation/game-dev/game-types.md)** - Understand game type templates
- **[Glossary](../../reference/glossary/index.md)** - Game development terminology
---

4
docs/tutorials/getting-started/quick-start-bmm.md
View File

@ -187,7 +187,7 @@ Testing is not mandated by BMad. Decide how you want to engage TEA:
- **TEA-only (Standalone)** - Use TEA workflows with your own requirements and environment
- **TEA-integrated** - Use TEA as part of the BMad Method or Enterprise flow
See the [Test Architect Guide](./test-architecture.md) for the five TEA engagement models and recommended sequences.
See the [Test Architect Guide](../../explanation/features/tea-overview.md) for the five TEA engagement models and recommended sequences.
#### Context Management Tips
@ -365,7 +365,7 @@ A: Yes, once you learn the flow. Use the Quick Reference in Step 2 to go directl
- **During workflows**: Agents guide you with questions and explanations
- **Community**: [Discord](https://discord.gg/gk8jAdXWmj) - #general-dev, #bugs-issues
- **Complete guide**: [BMM Workflow Documentation](./index.md#-workflow-guides)
- **Complete guide**: [BMM Workflow Documentation](../../reference/workflows/index.md)
- **YouTube tutorials**: [BMad Code Channel](https://www.youtube.com/@BMadCode)
---

40
website/css/custom.css
View File

@ -1,6 +1,8 @@
/**
* BMAD Method Documentation - Custom Styles
* Electric Blue theme optimized for dark mode
*
* NOTE: Layout is left to stock Docusaurus - only visual styling here
*/
/* ============================================
@ -199,10 +201,8 @@
}
/* ============================================
LAYOUT - Spacing and structure
LAYOUT - Only max-width for very wide viewports
============================================ */
/* Max-width container for very wide viewports */
.main-wrapper {
max-width: 1600px;
margin: 0 auto;
@ -218,34 +218,14 @@
margin: 0 auto;
}
/* Remove sidebar border/separator, add spacing instead */
/* Remove sidebar border/separator */
.theme-doc-sidebar-container {
border-right: none !important;
}
/* Sidebar spacing on larger viewports */
@media (min-width: 997px) {
.theme-doc-sidebar-container {
padding-left: 1rem;
padding-right: 1.5rem;
}
/* Add left margin to main content area */
.docMainContainer_node_modules-\@docusaurus-theme-classic-lib-theme-DocPage-Layout-Main-styles-module {
padding-left: 1rem;
}
}
@media (min-width: 1200px) {
.theme-doc-sidebar-container {
padding-left: 1.5rem;
padding-right: 2rem;
}
}
/* Ensure sidebar menu doesn't clip */
.theme-doc-sidebar-menu {
padding-right: 1.5rem;
/* Hide breadcrumbs */
.theme-doc-breadcrumbs {
display: none;
}
/* Lighter chevrons/carets */
@ -259,11 +239,6 @@
opacity: 0.6;
}
/* Add gap between sidebar and content */
.col.docItemCol_node_modules-\@docusaurus-theme-classic-lib-theme-DocItem-Layout-styles-module {
padding-left: 2rem !important;
}
/* ============================================
NAVBAR
============================================ */
@ -272,7 +247,6 @@
box-shadow: 0 1px 2px rgba(0, 0, 0, 0.1);
}
/* Align logo with sidebar content */
@media (min-width: 997px) {
.navbar {
padding-left: 2.5rem;

22
website/sidebars.js
View File

@ -37,28 +37,6 @@ const sidebars = {
link: { type: 'doc', id: 'reference/index' },
items: [{ type: 'autogenerated', dirName: 'reference' }],
},
// ==========================================
// LEGACY STRUCTURE (Being Migrated)
// Remove sections as they become empty
// ==========================================
{
type: 'html',
value:
'<div style="margin: 2rem 0 0.75rem; padding-top: 1rem; border-top: 1px solid var(--ifm-color-emphasis-200);"><span style="font-size: 0.6875rem; color: var(--ifm-color-emphasis-500); text-transform: uppercase; letter-spacing: 0.05em; padding-left: 0.75rem;">Legacy to be migrated</span></div>',
},
{
type: 'category',
label: 'Core Concepts',
collapsed: true,
items: [{ type: 'autogenerated', dirName: 'bmad-core-concepts' }],
},
{
type: 'category',
label: 'Modules',
collapsed: true,
items: [{ type: 'autogenerated', dirName: 'modules' }],
},
],
};