ros/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git synced 2026-01-30 04:32:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: comprehensive style guide update with reference and glossary standards

Browse Source 
Style Guide Additions:
- Add Reference Structure section with 6 document types (Index, Catalog,
  Deep-Dive, Configuration, Glossary, Comprehensive)
- Add Glossary Structure section with table-based format leveraging
  Starlight's right-nav for navigation
- Include checklists for both new document types

Reference Docs Updated:
- agents/index.md: Catalog format, universal commands tip admonition
- configuration/core-tasks.md: Configuration format with admonitions
- configuration/global-config.md: Table-based config reference
- workflows/index.md: Minimal index format
- workflows/core-workflows.md: Catalog format
- workflows/document-project.md: Deep-dive with Quick Facts admonition
- workflows/bmgd-workflows.md: Comprehensive format, removed ~30 hr rules

Glossary Rewritten:
- Converted from 373 lines with ### headers to 123 lines with tables
- Right nav now shows 9 categories instead of 50+ terms
- Added italic context markers (*BMGD.*, *Brownfield.*, etc.)
- Alphabetized terms within categories
- Removed redundant inline TOC

All Docs:
- Remove horizontal rules (---) per style guide
- Remove "Related" sections (sidebar handles navigation)
- Standardize admonition usage
- Archive deleted workflow customization docs

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
forcetrainer
2026-01-12 00:23:05 -05:00
parent e465ce4bb5
commit e535f94325
67 changed files with 1530 additions and 2661 deletions
Download Patch File Download Diff File Expand all files Collapse all files

64
docs/explanation/agents/barry-quick-flow.md
View File

@@ -2,12 +2,13 @@
title: "Quick Flow Solo Dev Agent (Barry)"
---
Barry is the elite solo developer who takes projects from concept to deployment with ruthless efficiency — no handoffs, no delays, just pure focused development.
**Agent ID:** `_bmad/bmm/agents/quick-flow-solo-dev.md`
**Icon:** 🚀
**Module:** BMM
---
:::note[Agent Info]
- **Agent ID:** `_bmad/bmm/agents/quick-flow-solo-dev.md`
- **Icon:** 🚀
- **Module:** BMM
:::
## Overview
@@ -31,8 +32,6 @@ Barry is the elite solo developer who lives and breathes the BMad Quick Flow wor
- Documentation happens alongside development, not after
- Ship early, ship often
---
## Menu Commands
Barry owns the entire BMad Quick Flow path, providing a streamlined 3-step development process that eliminates handoffs and maximizes velocity.
@@ -61,8 +60,6 @@ Barry owns the entire BMad Quick Flow path, providing a streamlined 3-step devel
- **Description:** Bring in other experts when I need specialized backup
- **Use when:** You need collaborative problem-solving or specialized expertise
---
## When to Use Barry
### Ideal Scenarios
@@ -81,8 +78,6 @@ Barry owns the entire BMad Quick Flow path, providing a streamlined 3-step devel
- **Proof of Concepts** - Rapid prototyping with production-quality code
- **Performance Optimizations** - System improvements and scalability work
---
## The BMad Quick Flow Process
Barry orchestrates a simple, efficient 3-step process:
@@ -180,8 +175,6 @@ flowchart LR
- Security considerations
- Maintainability and documentation
---
## Collaboration with Other Agents
### Natural Partnerships
@@ -201,8 +194,6 @@ In party mode, Barry often acts as:
- **Performance Optimizer** - Ensuring scalable solutions
- **Code Review Authority** - Validating technical approaches
---
## Tips for Working with Barry
### For Best Results
@@ -228,8 +219,6 @@ In party mode, Barry often acts as:
4. **Over-planning** - I excel at rapid, pragmatic development
5. **Not Using Party Mode** - Missing collaborative insights for complex problems
---
## Example Workflow
```bash
@@ -306,35 +295,34 @@ Implement OAuth 2.0 authentication with JWT tokens and role-based access control
- [ ] Given admin role, when accessing admin endpoint, then allow access
```
---
## Common Questions
## Related Documentation
- [When should I use Barry vs other agents?](#when-should-i-use-barry-vs-other-agents)
- [Is the code review step mandatory?](#is-the-code-review-step-mandatory)
- [Can I skip the tech spec step?](#can-i-skip-the-tech-spec-step)
- [How does Barry differ from the Dev agent?](#how-does-barry-differ-from-the-dev-agent)
- [Can Barry handle enterprise-scale projects?](#can-barry-handle-enterprise-scale-projects)
- **[Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)** - Getting started with BMM
- **[Agents Guide](/docs/explanation/core-concepts/agent-roles.md)** - Complete agent reference
- **[Four Phases](/docs/explanation/architecture/four-phases.md)** - Understanding development tracks
- **[Workflow Implementation](/docs/how-to/workflows/run-sprint-planning.md)** - Implementation workflows
- **[Party Mode](/docs/explanation/features/party-mode.md)** - Multi-agent collaboration
### When should I use Barry vs other agents?
---
Use Barry for Quick Flow development (small to medium features), rapid prototyping, or when you need elite solo development. For large, complex projects requiring full team collaboration, consider the full BMad Method with specialized agents.
## Frequently Asked Questions
### Is the code review step mandatory?
**Q: When should I use Barry vs other agents?**
A: Use Barry for Quick Flow development (small to medium features), rapid prototyping, or when you need elite solo development. For large, complex projects requiring full team collaboration, consider the full BMad Method with specialized agents.
No, it's optional but highly recommended for critical features, team projects, or when learning best practices.
**Q: Is the code review step mandatory?**
A: No, it's optional but highly recommended for critical features, team projects, or when learning best practices.
### Can I skip the tech spec step?
**Q: Can I skip the tech spec step?**
A: Yes, the quick-dev workflow accepts direct instructions. However, tech specs are recommended for complex features or team collaboration.
Yes, the quick-dev workflow accepts direct instructions. However, tech specs are recommended for complex features or team collaboration.
**Q: How does Barry differ from the Dev agent?**
A: Barry handles the complete Quick Flow process (spec → dev → review) with elite architectural expertise, while the Dev agent specializes in pure implementation tasks. Barry is your autonomous end-to-end solution.
### How does Barry differ from the Dev agent?
**Q: Can Barry handle enterprise-scale projects?**
A: For enterprise-scale projects requiring full team collaboration, consider using the Enterprise Method track. Barry is optimized for rapid delivery in the Quick Flow track where solo execution wins.
Barry handles the complete Quick Flow process (spec → dev → review) with elite architectural expertise, while the Dev agent specializes in pure implementation tasks. Barry is your autonomous end-to-end solution.
---
### Can Barry handle enterprise-scale projects?
**Ready to ship some code?** → Start with `/bmad:bmm:agents:quick-flow-solo-dev`
For enterprise-scale projects requiring full team collaboration, consider using the Enterprise Method track. Barry is optimized for rapid delivery in the Quick Flow track where solo execution wins.
:::tip[Ready to Ship?]
Start with `/bmad:bmm:agents:quick-flow-solo-dev`
:::

28
docs/explanation/agents/index.md
View File

@@ -3,26 +3,18 @@ title: "Understanding Agents"
description: Understanding BMad agents and their roles
---
Comprehensive guides to BMad's AI agents - their roles, capabilities, and how to work with them effectively.
---
Comprehensive guides to BMad's AI agents — their roles, capabilities, and how to work with them effectively.
## Agent Guides
### BMM Agents
| Agent | Description |
|-------|-------------|
| **[Agent Roles](/docs/explanation/core-concepts/agent-roles.md)** | Overview of all BMM agent roles and responsibilities |
| **[Quick Flow Solo Dev (Barry)](/docs/explanation/agents/barry-quick-flow.md)** | The dedicated agent for rapid development |
| **[Game Development Agents](/docs/explanation/game-dev/agents.md)** | Complete guide to BMGD's specialized game dev agents |
- **[Agent Roles](/docs/explanation/core-concepts/agent-roles.md)** - Overview of all BMM agent roles and responsibilities
- **[Quick Flow Solo Dev (Barry)](/docs/explanation/agents/barry-quick-flow.md)** - The dedicated agent for rapid development
## Getting Started
### BMGD Agents
- **[Game Development Agents](/docs/explanation/game-dev/agents.md)** - Complete guide to BMGD's specialized game dev agents
---
## Related
- **[What Are Agents?](/docs/explanation/core-concepts/what-are-agents.md)** - Core concept explanation
- **[Party Mode](/docs/explanation/features/party-mode.md)** - Multi-agent collaboration
- **[Customize Agents](/docs/how-to/customization/customize-agents.md)** - How to customize agent behavior
1. Read **[What Are Agents?](/docs/explanation/core-concepts/what-are-agents.md)** for the core concept explanation
2. Review **[Agent Roles](/docs/explanation/core-concepts/agent-roles.md)** to understand available agents
3. Choose an agent that fits your workflow needs

25
docs/explanation/architecture/four-phases.md
View File

@@ -6,8 +6,6 @@ description: Understanding the four phases of the BMad Method
BMad Method uses a four-phase approach that adapts to project complexity while ensuring consistent quality.
---
## Phase Overview
| Phase | Name | Purpose | Required? |
@@ -17,8 +15,6 @@ BMad Method uses a four-phase approach that adapts to project complexity while e
| **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.
@@ -38,8 +34,6 @@ Exploration and discovery workflows that help validate ideas and understand mark
- Well-defined features
- Continuing existing work
---
## Phase 2: Planning (Required)
Requirements definition using the scale-adaptive system to match planning depth to project complexity.
@@ -52,8 +46,6 @@ Requirements definition using the scale-adaptive system to match planning depth
**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.
@@ -73,8 +65,6 @@ Technical architecture and design decisions that prevent agent conflicts during
**Key principle:**
Make technical decisions explicit so all agents implement consistently.
---
## Phase 4: Implementation (Required)
Iterative sprint-based development with story-centric workflow.
@@ -86,10 +76,9 @@ Iterative sprint-based development with story-centric workflow.
- `code-review` - Quality assurance
- `retrospective` - Continuous improvement
**Key principle:**
One story at a time, complete each story's full lifecycle before starting the next.
---
:::tip[Key Principle]
One story at a time — complete each story's full lifecycle before starting the next.
:::
## Phase Flow by Track
@@ -116,11 +105,3 @@ Phase 1 → Phase 2 (PRD) → Phase 3 (architecture + extended) → Phase 4 (imp
```
Same as BMad Method with optional extended workflows.
---
## Related
- [Why Solutioning Matters](/docs/explanation/architecture/why-solutioning-matters.md)
- [Preventing Agent Conflicts](/docs/explanation/architecture/preventing-agent-conflicts.md)
- [Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)

43
docs/explanation/architecture/preventing-agent-conflicts.md
View File

@@ -6,8 +6,6 @@ description: How architecture prevents conflicts when multiple agents implement
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
@@ -43,8 +41,6 @@ With architecture:
- ADR specifies state management approach
- All agents implement consistently
---
## How Architecture Prevents Conflicts
### 1. Explicit Decisions via ADRs
@@ -70,8 +66,6 @@ Explicit documentation of:
- Code organization
- Testing patterns
---
## Architecture as Shared Context
Think of architecture as the shared context that all agents read before implementing:
@@ -88,8 +82,6 @@ Agent C reads architecture → implements Epic 3
Result: Consistent implementation
```
---
## Key ADR Topics
Common decisions that prevent conflicts:
@@ -103,36 +95,17 @@ Common decisions that prevent conflicts:
| Styling | CSS Modules vs Tailwind vs Styled Components |
| Testing | Jest + Playwright vs Vitest + Cypress |
---
## Anti-Patterns to Avoid
## 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
:::caution[Common Mistakes]
- **Implicit Decisions** — "We'll figure out the API style as we go" leads to inconsistency
- **Over-Documentation** — Documenting every minor choice causes analysis paralysis
- **Stale Architecture** — Documents written once and never updated cause agents to follow outdated patterns
:::
:::tip[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](/docs/explanation/architecture/why-solutioning-matters.md)
- [Four Phases](/docs/explanation/architecture/four-phases.md)
- [Create Architecture](/docs/how-to/workflows/create-architecture.md)
:::

26
docs/explanation/architecture/why-solutioning-matters.md
View File

@@ -6,8 +6,6 @@ description: Understanding why the solutioning phase is critical for multi-epic
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
```
@@ -18,8 +16,6 @@ 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
```
@@ -30,8 +26,6 @@ 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) |
@@ -43,8 +37,6 @@ By documenting technical decisions explicitly, all agents implement consistently
| 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.
@@ -56,8 +48,6 @@ This prevents:
- Naming convention mismatches
- Security approach variations
---
## When Solutioning is Required
| Track | Solutioning Required? |
@@ -67,9 +57,9 @@ This prevents:
| BMad Method Complex | Yes |
| Enterprise | Yes |
**Rule of thumb:** If you have multiple epics that could be implemented by different agents, you need solutioning.
---
:::tip[Rule of Thumb]
If you have multiple epics that could be implemented by different agents, you need solutioning.
:::
## The Cost of Skipping
@@ -80,12 +70,6 @@ Skipping solutioning on complex projects leads to:
- **Longer development time** overall
- **Technical debt** from inconsistent patterns
:::caution[Cost Multiplier]
Catching alignment issues in solutioning is 10× faster than discovering them during implementation.
---
## Related
- [Four Phases](/docs/explanation/architecture/four-phases.md) - Overview of all phases
- [Preventing Agent Conflicts](/docs/explanation/architecture/preventing-agent-conflicts.md) - Detailed conflict prevention
- [Create Architecture](/docs/how-to/workflows/create-architecture.md) - How to do it
:::

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

@@ -2,10 +2,13 @@
title: "Custom Content"
---
BMad supports several categories of custom content that extend the platform's capabilities — from simple personal agents to full-featured professional modules.
BMad supports several categories of officially supported custom content that extend the platform's capabilities. Custom content can be created manually or with the recommended assistance of the BMad Builder (BoMB) Module. The BoMB Agents provides workflows and expertise to plan and build any custom content you can imagine.
:::tip[Recommended Approach]
Use the BMad Builder (BoMB) Module for guided workflows and expertise when creating custom content.
:::
This flexibility transforms the platform beyond its current capabilities, enabling:
This flexibility enables:
- Extensions and add-ons for existing modules (BMad Method, Creative Intelligence Suite)
- Completely new modules, workflows, templates, and agents outside software engineering
@@ -96,7 +99,9 @@ The distinction between simple and expert agents lies in their structure:
- When installed, the sidecar folder (`[agentname]-sidecar`) is placed in the user memory location
- has metadata type: expert
:::note[Key Distinction]
The key distinction is the presence of a sidecar folder. As web and consumer agent tools evolve to support common memory mechanisms, storage formats, and MCP, the writable memory files will adapt to support these evolving standards.
:::
Custom agents can be:
@@ -117,4 +122,6 @@ A custom workflow created outside of a larger module can still be distributed an
- Slash commands
- Manual command/prompt execution when supported by tools
:::tip[Core Concept]
At its core, a custom workflow is a single or series of prompts designed to achieve a specific outcome.
:::

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

@@ -3,64 +3,43 @@ title: "BMad Builder (BMB)"
description: Create custom agents, workflows, and modules for BMad
---
Create custom agents, workflows, and modules for BMad.
---
Create custom agents, workflows, and modules for BMad — from simple personal assistants to full-featured professional tools.
## Quick Start
- **[Agent Creation Guide](/docs/tutorials/advanced/create-custom-agent.md)** - Step-by-step guide to building your first agent
---
| Resource | Description |
|----------|-------------|
| **[Agent Creation Guide](/docs/tutorials/advanced/create-custom-agent.md)** | Step-by-step guide to building your first agent |
| **[Install Custom Modules](/docs/how-to/installation/install-custom-modules.md)** | Installing standalone simple and expert agents |
## 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
---
| Type | Description |
|------|-------------|
| **Simple Agent** | Self-contained, optimized, personality-driven |
| **Expert Agent** | Memory, sidecar files, domain restrictions |
| **Module Agent** | 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 `*`
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 `*`
---
:::note[Learn More]
See [Custom Content Types](/docs/explanation/bmad-builder/custom-content-types.md) for detailed explanations of all content categories.
:::
## 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](/docs/how-to/installation/install-custom-modules.md)
---
## Related
- [Custom Content Types](/docs/explanation/bmad-builder/custom-content-types.md) - Understanding content types
- [Create Custom Agent](/docs/tutorials/advanced/create-custom-agent.md) - Tutorial
| Agent | Type | Description |
|-------|------|-------------|
| **commit-poet** | Simple | Commit message artisan with style customization |
| **journal-keeper** | Expert | Personal journal companion with memory and pattern recognition |
| **security-engineer** | Module | BMM security specialist with threat modeling |
| **trend-analyst** | Module | CIS trend intelligence expert |

42
docs/explanation/bmm/index.md
View File

@@ -2,28 +2,22 @@
title: "BMM Documentation"
---
Complete guides for the BMad Method Module (BMM) — AI-powered agile development workflows that adapt to your project's complexity.
Complete guides for the BMad Method Module (BMM) - AI-powered agile development workflows that adapt to your project's complexity.
## Getting Started
---
## 🚀 Getting Started
:::tip[Quick Path]
Install → workflow-init → Follow agent guidance
:::
**New to BMM?** Start here:
- **[Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)** - Step-by-step guide to building your first project
- Installation and setup
- Understanding the four phases
- Running your first workflows
- Agent-based development flow
| Resource | Description |
|----------|-------------|
| **[Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)** | Step-by-step guide to building your first project |
| **[Complete Workflow Diagram](../../tutorials/getting-started/images/workflow-method-greenfield.svg)** | Visual flowchart showing all phases, agents, and decision points |
**Quick Path:** Install → workflow-init → Follow agent guidance
### 📊 Visual Overview
**[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
## Core Concepts
The BMad Method is meant to be adapted and customized to your specific needs. In this realm there is no one size fits all - your needs are unique, and BMad Method is meant to support this (and if it does not, can be further customized or extended with new modules).
@@ -45,7 +39,7 @@ First know there is the full BMad Method Process and then there is a Quick Flow
- **TEA engagement (optional)** - Choose TEA engagement: none, TEA-only (standalone), or integrated by track. See **[Test Architect Guide](/docs/explanation/features/tea-overview.md)**.
## 🤖 Agents and Collaboration
## Agents and Collaboration
Complete guide to BMM's AI agent team:
@@ -63,7 +57,7 @@ Complete guide to BMM's AI agent team:
- Agent customization in party mode
- Best practices
## 🔧 Working with Existing Code
## Working with Existing Code
Comprehensive guide for brownfield development:
@@ -74,14 +68,14 @@ Comprehensive guide for brownfield development:
- Phase-by-phase workflow guidance
- Common scenarios
## 📚 Quick References
## Quick References
Essential reference materials:
- **[Glossary](/docs/reference/glossary/index.md)** - Key terminology and concepts
- **[FAQ](/docs/explanation/faq/index.md)** - Frequently asked questions across all topics
## 🎯 Choose Your Path
## Choose Your Path
### I need to...
@@ -95,7 +89,7 @@ Essential reference materials:
→ Read [Brownfield Development Guide](/docs/how-to/brownfield/index.md)
→ Pay special attention to documentation requirements for brownfield projects
## 📋 Workflow Guides
## Workflow Guides
Comprehensive documentation for all BMM workflows organized by phase:
@@ -124,7 +118,7 @@ Comprehensive documentation for all BMM workflows organized by phase:
- Test strategy, automation, quality gates
- TEA agent and test healing
## 🌐 External Resources
## External Resources
### Community and Support
@@ -132,4 +126,6 @@ Comprehensive documentation for all BMM workflows organized by phase:
- **[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 and walkthroughs
**Ready to begin?** → [Start with the Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)
:::tip[Ready to Begin?]
[Start with the Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)
:::

25
docs/explanation/core-concepts/agent-roles.md
View File

@@ -3,11 +3,8 @@ title: "Agent Roles in BMad Method"
description: Understanding the different 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 |
@@ -21,8 +18,6 @@ BMad Method uses specialized AI agents, each with a distinct role, expertise, an
| **UX Designer** | User experience | Phase 2-3 |
| **Quick Flow Solo Dev** | Fast solo development | All phases (Quick Flow) |
---
## Phase 1: Analysis
### Analyst (Mary)
@@ -43,8 +38,6 @@ Business analysis and research specialist.
**When to use:** Starting new projects, exploring ideas, validating market fit, documenting existing codebases.
---
## Phase 2: Planning
### PM (John)
@@ -80,8 +73,6 @@ User experience and UI design specialist.
**When to use:** When UX is a primary differentiator, complex user workflows, design system creation.
---
## Phase 3: Solutioning
### Architect (Winston)
@@ -100,8 +91,6 @@ System architecture and technical design expert.
**When to use:** Multi-epic projects, cross-cutting technical decisions, preventing agent conflicts.
---
## Phase 4: Implementation
### SM (Bob)
@@ -138,8 +127,6 @@ Story implementation and code review specialist.
**When to use:** Writing code, implementing stories, reviewing quality.
---
## Cross-Phase Agents
### TEA (Murat)
@@ -159,8 +146,6 @@ Test architecture and quality strategy expert.
**When to use:** Setting up testing, creating test plans, quality gates.
---
## Quick Flow
### Quick Flow Solo Dev (Barry)
@@ -179,8 +164,6 @@ Fast solo development without handoffs.
**When to use:** Bug fixes, small features, rapid prototyping.
---
## Choosing the Right Agent
| Task | Agent |
@@ -194,11 +177,3 @@ Fast solo development without handoffs.
| Writing code | DEV |
| Setting up tests | TEA |
| Quick bug fix | Quick Flow Solo Dev |
---
## Related
- [What Are Agents](/docs/explanation/core-concepts/what-are-agents.md) - Foundational concepts
- [Agent Reference](/docs/reference/agents/index.md) - Complete command reference
- [Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md)

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

@@ -2,7 +2,6 @@
title: "BMad Core Concepts"
---
Understanding the fundamental building blocks of the BMad Method.
## The Essentials
@@ -34,7 +33,3 @@ Start here to understand what BMad is and how it works:
### Advanced
- **[Web Bundles](/docs/explanation/features/web-bundles.md)** - Use BMad in Gemini Gems and Custom GPTs
---
**Next:** Read the [Agents Guide](/docs/explanation/core-concepts/what-are-agents.md) to understand the core building block of BMad.

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

@@ -2,7 +2,6 @@
title: "Agents"
---
Agents are AI assistants that help you accomplish tasks. Each agent has a unique personality, specialized capabilities, and an interactive menu.
## Agent Types
@@ -72,6 +71,10 @@ All agents share these building blocks:
## Which Should You Use?
:::tip[Quick Decision]
Choose **Simple** for focused, one-off tasks with no memory needs. Choose **Expert** when you need persistent context and complex workflows.
:::
**Choose Simple when:**
- You need a task done quickly and reliably
- The scope is well-defined and won't change much
@@ -90,7 +93,3 @@ BMad provides the **BMad Builder (BMB)** module for creating your own agents. Se
## Customizing Existing Agents
You can modify any agent's behavior without editing core files. See [BMad Customization](/docs/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](/docs/explanation/core-concepts/what-are-workflows.md) to see how agents accomplish complex tasks.

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

@@ -2,7 +2,6 @@
title: "Modules"
---
Modules are organized collections of agents and workflows that solve specific problems or address particular domains.
## What is a Module?
@@ -16,6 +15,10 @@ A module is a self-contained package that includes:
## Official Modules
:::note[Core is Always Installed]
The Core module is automatically included with every BMad installation. It provides the foundation that other modules build upon.
:::
### Core Module
Always installed, provides shared functionality:
- Global configuration
@@ -73,7 +76,3 @@ 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](/docs/how-to/installation/index.md) for details.
---
**Next:** Read the [Installation Guide](/docs/how-to/installation/index.md) to set up BMad with the modules you need.

19
docs/explanation/core-concepts/what-are-workflows.md
View File

@@ -2,13 +2,10 @@
title: "Workflows"
---
Workflows are like prompts on steroids. They harness the untapped power and control of LLMs through progressive disclosure—breaking complex tasks into focused steps that execute sequentially. Instead of random AI slop where you hope for the best, workflows give you repeatable, reliable, high-quality outputs.
This guide explains what workflows are, why they're powerful, and how to think about designing them.
---
## What Is a Workflow?
A workflow is a structured process where the AI executes steps sequentially to accomplish a task. Each step has a specific purpose, and the AI moves through them methodically—whether that involves extensive collaboration or minimal user interaction.
@@ -71,9 +68,9 @@ When workflows involve users, they should be **facilitative, not directive**. Th
The AI figures out exact wording and question order based on conversation context. This makes interactions feel natural and responsive rather than robotic and interrogative.
**When to be prescriptive**: Some workflows require exact scripts—medical intake, legal compliance, safety-critical procedures. But these are the exception, not the rule. Default to facilitative intent-based approaches unless compliance or regulation demands otherwise.
---
:::caution[When to Be Prescriptive]
Some workflows require exact scripts—medical intake, legal compliance, safety-critical procedures. But these are the exception. Default to facilitative intent-based approaches unless compliance or regulation demands otherwise.
:::
## Why Workflows Matter
@@ -85,8 +82,6 @@ Workflows solve three fundamental problems with AI interactions:
**Quality**: Sequential enforcement prevents shortcuts. The AI must complete each step fully before moving on, ensuring thorough, complete outputs instead of rushed, half-baked results.
---
## How Workflows Work
### The Basic Structure
@@ -150,8 +145,6 @@ All BMad planning workflows and the BMB module (will) use this tri-modal pattern
This tri-modal approach gives you the best of both worlds: the creativity and flexibility to build what you need, the quality assurance of validation that can run anytime, and the ability to iterate while staying true to standards that make the artifacts valuable across sessions and team members.
---
## Design Decisions
Before building a workflow, answer these questions:
@@ -166,8 +159,6 @@ Before building a workflow, answer these questions:
**Intent or prescriptive?**: Is this intent-based facilitation (most workflows) or prescriptive compliance (medical, legal, regulated)?
---
## Learning from Examples
The best way to understand workflows is to study real examples. Look at the official BMad modules:
@@ -181,8 +172,6 @@ Study the workflow.md files to understand how each workflow starts. Examine step
Copy patterns that work. Adapt them to your domain. The structure is consistent across all workflows—the content and steps change, but the architecture stays the same.
---
## When to Use Workflows
Use workflows when:
@@ -206,8 +195,6 @@ Modified BMad Workflows
If there's only one thing to do and it can be explained in under about 300 lines - don't bother with step files. Instead, you can still have
a short single file workflow.md file.
---
## The Bottom Line
Workflows transform AI from a tool that gives variable, unpredictable results into a reliable system for complex, multi-step processes. Through progressive disclosure, sequential execution, guided facilitation, and thoughtful design, workflows give you control and repeatability that ad-hoc prompting alone can't match.

24
docs/explanation/creative-intelligence/index.md
View File

@@ -3,17 +3,12 @@ title: "Creative Intelligence Suite (CIS)"
description: AI-powered creative facilitation with the Creative Intelligence Suite
---
AI-powered creative facilitation transforming strategic thinking through expert coaching across five specialized domains.
---
## 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)
@@ -22,8 +17,6 @@ CIS provides structured creative methodologies through distinctive agent persona
- **Victor** - Innovation Oracle (bold strategic precision)
- **Sophia** - Master Storyteller (whimsical narrator)
---
## Interactive Workflows
**5 Workflows** with **150+ Creative Techniques:**
@@ -63,8 +56,6 @@ Business model disruption:
- Story circles
- Compelling pitch structures
---
## Quick Start
### Direct Workflow
@@ -83,8 +74,6 @@ agent cis/brainstorming-coach
> *brainstorm
```
---
## Key Differentiators
- **Facilitation Over Generation** - Guides discovery through questions
@@ -93,8 +82,6 @@ agent cis/brainstorming-coach
- **Persona-Driven** - Unique communication styles
- **Rich Method Libraries** - 150+ proven techniques
---
## Integration Points
CIS workflows integrate with:
@@ -103,8 +90,6 @@ CIS workflows integrate with:
- **BMB** - Creative module design
- **Custom Modules** - Shared creative resource
---
## Best Practices
1. **Set clear objectives** before starting sessions
@@ -113,9 +98,6 @@ CIS workflows integrate with:
4. **Take breaks** when energy flags
5. **Document insights** as they emerge
---
## Related
- [Facilitation Over Generation](/docs/explanation/philosophy/facilitation-over-generation.md) - Core philosophy
- [Brainstorming Techniques](/docs/explanation/features/brainstorming-techniques.md) - Technique reference
:::tip[Learn More]
See [Facilitation Over Generation](/docs/explanation/philosophy/facilitation-over-generation.md) for the core philosophy behind CIS.
:::

15
docs/explanation/features/advanced-elicitation.md
View File

@@ -2,13 +2,10 @@
title: "Advanced Elicitation"
---
**Push the LLM to rethink its work through 50+ reasoning methods—essentially, LLM brainstorming.**
Push the LLM to rethink its work through 50+ reasoning methods — essentially, LLM brainstorming.
Advanced Elicitation is the inverse of Brainstorming. Instead of pulling ideas out of you, the LLM applies sophisticated reasoning techniques to re-examine and enhance content it has just generated. It's the LLM brainstorming with itself to find better approaches, uncover hidden issues, and discover improvements it missed on the first pass.
---
## When to Use It
- After a workflow generates a section of content and you want to explore alternatives
@@ -17,8 +14,6 @@ Advanced Elicitation is the inverse of Brainstorming. Instead of pulling ideas o
- To stress-test assumptions, explore edge cases, or find weaknesses in generated plans
- When you want the LLM to "think again" but with structured reasoning methods
---
## How It Works
### 1. Context Analysis
@@ -44,8 +39,6 @@ Based on context, 5 methods are intelligently selected from a library of 50+ tec
### 4. Party Mode Integration (Optional)
If Party Mode is active, BMad agents participate randomly in the elicitation process, adding their unique perspectives to the methods.
---
## Method Categories
| Category | Focus | Example Methods |
@@ -62,8 +55,6 @@ If Party Mode is active, BMad agents participate randomly in the elicitation pro
| **Philosophical** | Conceptual clarity | Occam's Razor, Ethical Dilemmas |
| **Retrospective** | Reflection and lessons | Hindsight Reflection, Lessons Learned Extraction |
---
## Key Features
- **50+ reasoning methods** — Spanning core logic to advanced multi-step reasoning frameworks
@@ -72,8 +63,6 @@ If Party Mode is active, BMad agents participate randomly in the elicitation pro
- **User control** — Accept or discard each enhancement before proceeding
- **Party Mode integration** — Agents can participate when Party Mode is active
---
## Workflow Integration
Advanced Elicitation is a core workflow designed to be invoked by other workflows during content generation:
@@ -96,8 +85,6 @@ When called from a workflow:
A specification generation workflow could invoke Advanced Elicitation after producing each major section (requirements, architecture, implementation plan). The workflow would pass the generated section, and Advanced Elicitation would offer methods like "Stakeholder Round Table" to gather diverse perspectives on requirements, or "Red Team vs Blue Team" to stress-test the architecture for vulnerabilities.
---
## Advanced Elicitation vs. Brainstorming
| | **Advanced Elicitation** | **Brainstorming** |

23
docs/explanation/features/brainstorming-techniques.md
View File

@@ -2,14 +2,13 @@
title: "Brainstorming"
---
Facilitate structured creative sessions using 60+ proven ideation techniques.
**Facilitate structured creative sessions using 60+ proven ideation techniques.**
The Brainstorming workflow is an interactive facilitation system that helps you unlock your own creativity. The AI acts as coach, guide, and creative partner — using proven techniques to draw out ideas and insights that are already within you.
The Brainstorming workflow is an interactive facilitation system that helps you unlock your own creativity. The AI acts as coach, guide, and creative partner—using proven techniques to draw out ideas and insights that are already within you.
**Important:** Every idea comes from you. The workflow creates the conditions for your best thinking to emerge through guided exploration, but you are the source.
---
:::note[Important]
Every idea comes from you. The workflow creates the conditions for your best thinking to emerge through guided exploration, but you are the source.
:::
## When to Use It
@@ -19,8 +18,6 @@ The Brainstorming workflow is an interactive facilitation system that helps you
- Systematically developing ideas from raw concepts to actionable plans
- Team ideation (with collaborative techniques) or personal creative exploration
---
## How It Works
### 1. Session Setup
@@ -44,8 +41,6 @@ All your generated ideas are organized into themes and prioritized.
### 5. Action Planning
Top ideas get concrete next steps, resource requirements, and success metrics.
---
## What You Get
A comprehensive session document that captures the entire journey:
@@ -57,9 +52,7 @@ A comprehensive session document that captures the entire journey:
- Prioritized ideas with action plans
- Session highlights and key breakthroughs
This document becomes a permanent record of your creative process—valuable for future reference, sharing with stakeholders, or continuing the session later.
---
This document becomes a permanent record of your creative process — valuable for future reference, sharing with stakeholders, or continuing the session later.
## Technique Categories
@@ -76,8 +69,6 @@ This document becomes a permanent record of your creative process—valuable for
| **Cultural** | Traditional knowledge and cross-cultural approaches |
| **Introspective Delight** | Inner wisdom and authentic exploration |
---
## Key Features
- **Interactive coaching** — Pulls ideas *out* of you, doesn't generate them for you
@@ -85,8 +76,6 @@ This document becomes a permanent record of your creative process—valuable for
- **Session preservation** — Every step, insight, and action plan is documented
- **Continuation support** — Pause sessions and return later, or extend with additional techniques
---
## Workflow Integration
Brainstorming is a core workflow designed to be invoked and configured by other modules. When called from another workflow, it accepts contextual parameters:

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

@@ -2,8 +2,7 @@
title: "Party Mode: Multi-Agent Collaboration"
---
**Get all your AI agents in one conversation**
Get all your AI agents in one conversation.
## What is Party Mode?
@@ -20,8 +19,6 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent or at ke
- **Sprint retrospectives** - Party mode powers the retrospective workflow
- **Sprint planning** - Multi-agent collaboration for planning sessions
---
## How It Works
**The basics:**
@@ -34,8 +31,6 @@ Type `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent or at ke
**That's it.** No complex merging, no runtime magic. Just agents talking.
---
## Quick Start
```bash
@@ -51,8 +46,6 @@ Ask questions, respond to agents, direct the conversation
Type: exit
```
---
## Fun Examples
### Example 1: Calling Out Bad Architecture
@@ -69,8 +62,6 @@ Type: exit
_(Watch them debate whose fault it really was - it's therapeutic)_
---
### Example 2: Creative Brainstorming
**You:** "How do we make onboarding feel magical instead of boring?"
@@ -85,8 +76,6 @@ _(Watch them debate whose fault it really was - it's therapeutic)_
_(Ideas cross-pollinate and evolve)_
---
### Example 3: Technical Decision
**You:** "Monolith or microservices for MVP?"
@@ -101,12 +90,6 @@ _(Ideas cross-pollinate and evolve)_
_(Multiple perspectives reveal the right answer)_
## Related Documentation
- [Agents Reference](/docs/reference/agents/index.md) - Complete agent reference
- [Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md) - Getting started with BMM
- [Setup Party Mode](/docs/how-to/workflows/setup-party-mode.md) - How to use it
---
_Better decisions through diverse perspectives. Welcome to party mode._
:::tip[Better Decisions]
Better decisions through diverse perspectives. Welcome to party mode.
:::

76
docs/explanation/features/quick-flow.md
View File

@@ -3,18 +3,14 @@ title: "Quick Spec Flow"
description: Understanding Quick Spec Flow for rapid development in BMad Method
---
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
---
- **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:
### Use Quick Flow when:
- Single bug fix or small enhancement
- Small feature with clear scope (typically 1-15 stories)
@@ -22,16 +18,16 @@ Quick Spec Flow is a streamlined alternative to the full BMad Method for Quick F
- Adding to existing brownfield codebase
- You know exactly what you want to build
### ❌ Use BMad Method or Enterprise when:
### 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!
---
:::tip[Not Sure?]
Run `workflow-init` to get a recommendation based on your project's needs.
:::
## Quick Flow Overview
@@ -61,19 +57,15 @@ flowchart TD
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!)
---
- 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
@@ -119,19 +111,15 @@ 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
---
- Context gathering completeness
- Definitiveness (no "use X or Y" statements)
- Brownfield integration quality
- Stack alignment
- Implementation readiness
## Comparison: Quick Flow vs Full BMM
@@ -145,25 +133,17 @@ Quick Spec Flow **automatically validates** everything:
| **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
- 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
- [Quick Spec](/docs/how-to/workflows/quick-spec.md) - How to use Quick Flow
- [Quick Start Guide](/docs/tutorials/getting-started/getting-started-bmadv6.md) - Getting started
- [Four Phases](/docs/explanation/architecture/four-phases.md) - Understanding the full methodology
:::tip[Transition Tip]
You can always run `workflow-init` later to transition from Quick Flow to BMad Method.
:::

22
docs/explanation/features/tea-overview.md
View File

@@ -16,8 +16,6 @@ TEA was built to solve AI-generated tests that rot in review. For the problem st
- **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.
@@ -50,8 +48,6 @@ BMad does not mandate TEA. There are five valid ways to use it (or skip it). Pic
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):
@@ -153,8 +149,6 @@ 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**.
@@ -209,9 +203,6 @@ TEA uniquely requires:
This architecture enables TEA to maintain consistent, production-ready testing patterns across all BMad projects while operating across multiple development phases.
---
## 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).
@@ -366,8 +357,6 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
</details>
---
## TEA Command Catalog
| Command | Primary Outputs | Notes | With Playwright MCP Enhancements |
@@ -381,8 +370,6 @@ These cheat sheets map TEA workflows to the **BMad Method and Enterprise tracks*
| `*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 | - |
---
## Playwright Utils Integration
TEA optionally integrates with `@seontechnologies/playwright-utils`, an open-source library providing fixture-based utilities for Playwright tests. This integration enhances TEA's test generation and review workflows with production-ready patterns.
@@ -431,8 +418,6 @@ TEA optionally integrates with `@seontechnologies/playwright-utils`, an open-sou
</details>
---
## Playwright MCP Enhancements
TEA can leverage Playwright MCP servers to enhance test generation with live browser verification. MCP provides interactive capabilities on top of TEA's default AI-based approach.
@@ -488,10 +473,3 @@ TEA can leverage Playwright MCP servers to enhance test generation with live bro
Benefit: Visual failure context, live DOM inspection, root cause discovery
</details>
---
## Related Documentation
- [Setup Test Framework](/docs/how-to/workflows/setup-test-framework.md) - How to set up testing infrastructure
- [Run Test Design](/docs/how-to/workflows/run-test-design.md) - Creating test plans

7
docs/explanation/features/web-bundles.md
View File

@@ -2,12 +2,11 @@
title: "Web Bundles"
---
Use BMad agents in Gemini Gems and Custom GPTs.
## Status
> **Note:** The Web Bundling Feature is being rebuilt from the ground up. Current v6 bundles may be incomplete or missing functionality.
:::caution[Status]
The Web Bundling Feature is being rebuilt from the ground up. Current v6 bundles may be incomplete or missing functionality.
:::
## What Are Web Bundles?

51
docs/explanation/game-dev/agents.md
View File

@@ -2,27 +2,22 @@
title: "BMGD Agents Guide"
---
Complete reference for BMGD's six specialized game development agents.
---
## Agent Overview
BMGD provides six agents, each with distinct expertise:
| Agent | Name | Role | Phase Focus |
| ------------------------ | ---------------- | ----------------------------------------------------------- | ----------- |
| 🎲 **Game Designer** | Samus Shepard | Lead Game Designer + Creative Vision Architect | Phases 1-2 |
| 🏛️ **Game Architect** | Cloud Dragonborn | Principal Game Systems Architect + Technical Director | Phase 3 |
| 🕹️ **Game Developer** | Link Freeman | Senior Game Developer + Technical Implementation Specialist | Phase 4 |
| 🎯 **Game Scrum Master** | Max | Game Development Scrum Master + Sprint Orchestrator | Phase 4 |
| 🧪 **Game QA** | GLaDOS | Game QA Architect + Test Automation Specialist | All Phases |
| 🎮 **Game Solo Dev** | Indie | Elite Indie Game Developer + Quick Flow Specialist | All Phases |
| Agent | Name | Role | Phase Focus |
|-------|------|------|-------------|
| **Game Designer** | Samus Shepard | Lead Game Designer + Creative Vision Architect | Phases 1-2 |
| **Game Architect** | Cloud Dragonborn | Principal Game Systems Architect + Technical Director | Phase 3 |
| **Game Developer** | Link Freeman | Senior Game Developer + Technical Implementation Specialist | Phase 4 |
| **Game Scrum Master** | Max | Game Development Scrum Master + Sprint Orchestrator | Phase 4 |
| **Game QA** | GLaDOS | Game QA Architect + Test Automation Specialist | All Phases |
| **Game Solo Dev** | Indie | Elite Indie Game Developer + Quick Flow Specialist | All Phases |
---
## 🎲 Game Designer (Samus Shepard)
## Game Designer (Samus Shepard)
### Role
@@ -62,9 +57,7 @@ Talks like an excited streamer - enthusiastic, asks about player motivations, ce
| `party-mode` | Multi-agent collaboration |
| `advanced-elicitation` | Deep exploration (web only) |
---
## 🏛️ Game Architect (Cloud Dragonborn)
## Game Architect (Cloud Dragonborn)
### Role
@@ -102,9 +95,7 @@ Speaks like a wise sage from an RPG - calm, measured, uses architectural metapho
| `party-mode` | Multi-agent collaboration |
| `advanced-elicitation` | Deep exploration (web only) |
---
## 🕹️ Game Developer (Link Freeman)
## Game Developer (Link Freeman)
### Role
@@ -144,9 +135,7 @@ Speaks like a speedrunner - direct, milestone-focused, always optimizing for the
| `party-mode` | Multi-agent collaboration |
| `advanced-elicitation` | Deep exploration (web only) |
---
## 🎯 Game Scrum Master (Max)
## Game Scrum Master (Max)
### Role
@@ -190,9 +179,7 @@ Talks in game terminology - milestones are save points, handoffs are level trans
| `party-mode` | Multi-agent collaboration |
| `advanced-elicitation` | Deep exploration (web only) |
---
## 🧪 Game QA (GLaDOS)
## Game QA (GLaDOS)
### Role
@@ -265,9 +252,7 @@ GLaDOS has access to a comprehensive game testing knowledge base (`gametest/qa-i
- Smoke testing
- Test prioritization (P0-P3)
---
## 🎮 Game Solo Dev (Indie)
## Game Solo Dev (Indie)
### Role
@@ -324,8 +309,6 @@ Use **Full BMGD workflow** when:
- You're working with stakeholders/publishers
- Long-term maintainability is critical
---
## Agent Selection Guide
### By Phase
@@ -359,8 +342,6 @@ Use **Full BMGD workflow** when:
| "Quick prototype this idea" | Game Solo Dev |
| "Ship this feature fast" | Game Solo Dev |
---
## Multi-Agent Collaboration
### Party Mode
@@ -391,8 +372,6 @@ Game QA integrates at multiple points:
- During Implementation: Create automated tests
- Before Release: Performance and certification testing
---
## Project Context
All agents share the principle:
@@ -401,8 +380,6 @@ All agents share the principle:
The `project-context.md` file (if present) serves as the authoritative source for project decisions and constraints.
---
## Next Steps
- **[Quick Start Guide](/docs/tutorials/getting-started/quick-start-bmgd.md)** - Get started with BMGD

25
docs/explanation/game-dev/bmgd-vs-bmm.md
View File

@@ -3,11 +3,8 @@ title: "BMGD vs BMM"
description: Understanding the differences between BMGD and BMM
---
BMGD (BMad Game Development) extends BMM (BMad Method) with game-specific capabilities. This page explains the key differences.
---
## Quick Comparison
| Aspect | BMM | BMGD |
@@ -20,8 +17,6 @@ BMGD (BMad Game Development) extends BMM (BMad Method) with game-specific capabi
| **Testing** | Web-focused | Engine-specific (Unity, Unreal, Godot) |
| **Production** | BMM workflows | BMM workflows with game overrides |
---
## Agent Differences
### BMM Agents
@@ -46,8 +41,6 @@ BMGD agents understand game-specific concepts like:
- Engine-specific patterns
- Playtesting and QA
---
## Planning Documents
### BMM Planning
@@ -65,8 +58,6 @@ The GDD (Game Design Document) includes:
- Art and audio direction
- Genre-specific sections
---
## Game Type Templates
BMGD includes 24 game type templates that auto-configure GDD sections:
@@ -83,8 +74,6 @@ Each template provides:
- Testing considerations
- Common pitfalls to avoid
---
## Narrative Support
BMGD includes full narrative workflow for story-driven games:
@@ -97,8 +86,6 @@ BMGD includes full narrative workflow for story-driven games:
BMM has no equivalent for narrative design.
---
## Testing Differences
### BMM Testing (TEA)
@@ -113,8 +100,6 @@ BMM has no equivalent for narrative design.
- Playtest planning
- Balance validation
---
## Production Workflow
BMGD production workflows **inherit from BMM** and add game-specific:
@@ -125,8 +110,6 @@ BMGD production workflows **inherit from BMM** and add game-specific:
This means you get all of BMM's implementation structure plus game-specific enhancements.
---
## When to Use Each
### Use BMM when:
@@ -140,11 +123,3 @@ This means you get all of BMM's implementation structure plus game-specific enha
- Creating interactive experiences
- Game prototyping
- Game jams
---
## Related
- [BMGD Overview](/docs/explanation/game-dev/index.md) - Getting started with BMGD
- [Game Types Guide](/docs/explanation/game-dev/game-types.md) - Understanding game templates
- [Quick Start BMGD](/docs/tutorials/getting-started/quick-start-bmgd.md) - Tutorial

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

@@ -2,17 +2,12 @@
title: "BMGD Game Types Guide"
---
Reference for selecting and using BMGD's 24 supported game type templates.
---
## Overview
When creating a GDD, BMGD offers game type templates that provide genre-specific sections. This ensures your design document covers mechanics and systems relevant to your game's genre.
---
## Supported Game Types
### Action & Combat
@@ -30,8 +25,6 @@ Side-scrolling or 3D platforming with combat mechanics. Think Hollow Knight, Cel
- Level design patterns
- Boss design
---
#### Shooter
**Tags:** shooter, combat, aiming, fps, tps
@@ -46,8 +39,6 @@ Projectile combat with aiming mechanics. Covers FPS, TPS, and arena shooters.
- Level/arena design
- Multiplayer considerations
---
#### Fighting
**Tags:** fighting, combat, competitive, combos, pvp
@@ -62,8 +53,6 @@ Projectile combat with aiming mechanics. Covers FPS, TPS, and arena shooters.
- Competitive balance
- Netcode requirements
---
### Strategy & Tactics
#### Strategy
@@ -80,8 +69,6 @@ Resource management with tactical decisions. RTS, 4X, and grand strategy.
- Map/scenario design
- Victory conditions
---
#### Turn-Based Tactics
**Tags:** tactics, turn-based, grid, positioning
@@ -96,8 +83,6 @@ Grid-based movement with turn order. XCOM-likes and tactical RPGs.
- Unit progression
- Procedural mission generation
---
#### Tower Defense
**Tags:** tower-defense, waves, placement, strategy
@@ -112,8 +97,6 @@ Wave-based defense with tower placement.
- Map design patterns
- Meta-progression
---
### RPG & Progression
#### RPG
@@ -130,8 +113,6 @@ Character progression with stats, inventory, and quests.
- Combat system (action/turn-based)
- Skill trees and builds
---
#### Roguelike
**Tags:** roguelike, procedural, permadeath, runs
@@ -146,8 +127,6 @@ Procedural generation with permadeath and run-based progression.
- Item/ability synergies
- Meta-progression systems
---
#### Metroidvania
**Tags:** metroidvania, exploration, abilities, interconnected
@@ -162,8 +141,6 @@ Interconnected world with ability gating.
- Secret and collectible placement
- Power-up progression
---
### Narrative & Story
#### Adventure
@@ -180,8 +157,6 @@ Story-driven exploration and narrative. Point-and-click and narrative adventures
- Dialogue systems
- Story branching
---
#### Visual Novel
**Tags:** visual-novel, narrative, choices, story
@@ -196,8 +171,6 @@ Narrative choices with branching story.
- UI/presentation
- Save/load states
---
#### Text-Based
**Tags:** text, parser, interactive-fiction, mud
@@ -212,8 +185,6 @@ Text input/output games. Parser games, choice-based IF, MUDs.
- Text presentation
- Save state management
---
### Simulation & Management
#### Simulation
@@ -230,8 +201,6 @@ Realistic systems with management and building. Includes tycoons and sim games.
- Building/construction
- Failure states
---
#### Sandbox
**Tags:** sandbox, creative, building, freedom
@@ -246,8 +215,6 @@ Creative freedom with building and minimal objectives.
- Sharing/community features
- Optional objectives
---
### Sports & Racing
#### Racing
@@ -264,8 +231,6 @@ Vehicle control with tracks and lap times.
- Progression/career mode
- Multiplayer racing
---
#### Sports
**Tags:** sports, teams, realistic, physics
@@ -280,8 +245,6 @@ Team-based or individual sports simulation.
- Season/career modes
- Multiplayer modes
---
### Multiplayer
#### MOBA
@@ -298,8 +261,6 @@ Multiplayer team battles with hero selection.
- Matchmaking
- Economy (gold/items)
---
#### Party Game
**Tags:** party, multiplayer, minigames, casual
@@ -314,8 +275,6 @@ Local multiplayer with minigames.
- Scoring systems
- Player count flexibility
---
### Horror & Survival
#### Survival
@@ -332,8 +291,6 @@ Resource gathering with crafting and persistent threats.
- Threat systems
- Base building
---
#### Horror
**Tags:** horror, atmosphere, tension, fear
@@ -348,8 +305,6 @@ Atmosphere and tension with limited resources.
- Lighting and visibility
- Enemy/threat design
---
### Casual & Progression
#### Puzzle
@@ -366,8 +321,6 @@ Logic-based challenges and problem-solving.
- Level structure
- Scoring/rating
---
#### Idle/Incremental
**Tags:** idle, incremental, automation, progression
@@ -382,8 +335,6 @@ Passive progression with upgrades and automation.
- Number scaling
- Offline progress
---
#### Card Game
**Tags:** card, deck-building, strategy, turns
@@ -398,8 +349,6 @@ Deck building with card mechanics.
- Rarity and collection
- Competitive balance
---
### Rhythm
#### Rhythm
@@ -416,8 +365,6 @@ Music synchronization with timing-based gameplay.
- Music licensing
- Input methods
---
## Hybrid Game Types
Many games combine multiple genres. BMGD supports hybrid selection:
@@ -449,8 +396,6 @@ You: It's a roguelike with card game combat
Agent: I'll include sections for both Roguelike and Card Game...
```
---
## Game Type Selection Tips
### 1. Start with Core Fantasy
@@ -482,8 +427,6 @@ One type should be primary (most gameplay time). Others add flavor:
- **Primary:** Platformer (core movement and exploration)
- **Secondary:** Metroidvania (ability gating structure)
---
## GDD Section Mapping
When you select a game type, BMGD adds these GDD sections:
@@ -497,8 +440,6 @@ When you select a game type, BMGD adds these GDD sections:
| Multiplayer | Matchmaking, Netcode, Balance |
| Simulation | Systems, Economy, AI |
---
## Next Steps
- **[Quick Start Guide](/docs/tutorials/getting-started/quick-start-bmgd.md)** - Get started with BMGD

23
docs/explanation/game-dev/index.md
View File

@@ -3,10 +3,7 @@ title: "BMGD - Game Development Module"
description: AI-powered workflows for game design and development with BMGD
---
Complete guides for the BMad Game Development Module (BMGD) - AI-powered workflows for game design and development that adapt to your project's needs.
---
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
@@ -18,17 +15,15 @@ Complete guides for the BMad Game Development Module (BMGD) - AI-powered workflo
- Running your first workflows
- Agent-based development flow
**Quick Path:** Install BMGD module → Game Brief → GDD → Architecture → Build
---
:::tip[Quick Path]
Install BMGD module → Game Brief → GDD → Architecture → Build
:::
## Core Documentation
- **[Game Types Guide](/docs/explanation/game-dev/game-types.md)** - Selecting and using game type templates (24 supported types)
- **[BMGD vs BMM](/docs/explanation/game-dev/bmgd-vs-bmm.md)** - Understanding the differences
---
## Game Development Phases
BMGD follows four phases aligned with game development:
@@ -51,8 +46,6 @@ BMGD follows four phases aligned with game development:
- **Testing** - Automated tests, playtesting, performance
- **Retrospective** - Continuous improvement
---
## Choose Your Path
### I need to...
@@ -75,11 +68,3 @@ BMGD follows four phases aligned with game development:
**Quickly test an idea**
→ Use [Quick-Flow](/docs/how-to/workflows/bmgd-quick-flow.md) for rapid prototyping
---
## Related
- [Game Types Guide](/docs/explanation/game-dev/game-types.md) - Understanding game type templates
- [BMGD vs BMM](/docs/explanation/game-dev/bmgd-vs-bmm.md) - Comparison with core method
- [Glossary](/docs/reference/glossary/index.md) - Terminology reference

43
docs/explanation/philosophy/facilitation-over-generation.md
View File

@@ -6,16 +6,15 @@ description: Understanding CIS's facilitation-first approach to creative work
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..."
```
:::note[Generation Example]
**User:** "Give me marketing ideas"
**AI:** "Here are 10 marketing ideas..."
:::
This approach:
- Produces generic, predictable outputs
@@ -23,20 +22,19 @@ This approach:
- 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?"
```
:::note[Facilitation Example]
**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
@@ -44,8 +42,6 @@ This approach:
- Captures context and nuance
- Enables deeper creative exploration
---
## Key Principles
### 1. Questions Over Answers
@@ -85,8 +81,6 @@ Each CIS agent has a distinct personality:
These personas create engaging experiences that maintain creative flow.
---
## When Generation is Appropriate
CIS does generate when appropriate:
@@ -97,8 +91,6 @@ CIS does generate when appropriate:
But the core creative work happens through facilitated discovery.
---
## Benefits
### For Individuals
@@ -112,10 +104,3 @@ But the core creative work happens through facilitated discovery.
- Aligned understanding
- Documented rationale
- Stronger buy-in to outcomes
---
## Related
- [Creative Intelligence Suite](/docs/explanation/creative-intelligence/index.md) - CIS overview
- [Brainstorming Techniques](/docs/explanation/features/brainstorming-techniques.md) - Available techniques

7
docs/explanation/philosophy/testing-as-engineering.md
View File

@@ -110,10 +110,3 @@ The three-part stack addresses each gap:
| No review | TEA `*test-review` audits quality with scoring |
This approach is sometimes called *context engineering*—loading domain-specific standards into AI context automatically rather than relying on prompts alone. TEA's `tea-index.csv` manifest loads relevant knowledge fragments so the AI doesn't relearn testing patterns each session.
## Related
- [TEA Overview](/docs/explanation/features/tea-overview.md) — Workflow details and cheat sheets
- [Setup Test Framework](/docs/how-to/workflows/setup-test-framework.md) — Implementation guide
- [The Testing Meta Most Teams Have Not Caught Up To Yet](https://dev.to/muratkeremozcan/the-testing-meta-most-teams-have-not-caught-up-to-yet-5765) — Original article by Murat K Ozcan
- [Playwright-Utils Repository](https://github.com/seontechnologies/playwright-utils) — Source and documentation