External/BMAD-METHOD
1
0
Fork 0
mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix quick udpate status bug in installer

Browse Source
This commit is contained in:
Brian Madison
2025-11-04 21:16:52 -06:00
parent c283344a54
commit 7552ee2e3b
74 changed files with 861 additions and 4448 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
bmad/bmm/docs/README.md
View File

@@ -36,7 +36,7 @@ Understanding how BMM adapts to your needs:
---
## 🤖 Agents & Collaboration
## 🤖 Agents and Collaboration
Complete guide to BMM's AI agent team:
@@ -127,7 +127,7 @@ Comprehensive documentation for all BMM workflows organized by phase:
- Complete story lifecycle
- One-story-at-a-time discipline
- **[Testing & QA Workflows](./workflows-testing.md)** - Comprehensive quality assurance (1,420 lines)
- **[Testing & QA Workflows](./test-architecture.md)** - Comprehensive quality assurance (1,420 lines)
- Test strategy, automation, quality gates
- TEA agent and test healing
- BMad-integrated vs standalone modes
@@ -152,15 +152,16 @@ For detailed technical documentation on specific complex workflows:
---
## 🧪 Testing & Quality
## 🧪 Testing and Quality
Quality assurance guidance:
- **[Test Architect Guide](./tea-README.md)** - Comprehensive testing strategy
- Test design workflows
- Quality gates
- Risk assessment
- NFR validation
<!-- Test Architect documentation to be added -->
- Test design workflows
- Quality gates
- Risk assessment
- NFR validation
---
@@ -178,7 +179,7 @@ Understanding BMM components:
## 🌐 External Resources
### Community & Support
### Community and Support
- **[Discord Community](https://discord.gg/gk8jAdXWmj)** - Get help from the community (#general-dev, #bugs-issues)
- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features

2
bmad/bmm/docs/agents-guide.md
View File

@@ -996,7 +996,7 @@ Quick reference for agent selection:
- [Phase 2: Planning Workflows](./workflows-planning.md)
- [Phase 3: Solutioning Workflows](./workflows-solutioning.md)
- [Phase 4: Implementation Workflows](./workflows-implementation.md)
- [Testing & QA Workflows](./workflows-testing.md)
<!-- Testing & QA Workflows documentation to be added -->
**Advanced References:**

11
bmad/bmm/docs/brownfield-guide.md
View File

@@ -277,7 +277,7 @@ It's better to spend 10-30 minutes generating fresh, accurate docs than to waste
**When to skip:** Bug fixes, well-understood features, time-sensitive changes
See [Workflows Guide](../workflows/README.md) for details.
See the [Workflows section in BMM README](../README.md) for details.
### Phase 2: Planning (Required)
@@ -736,11 +736,11 @@ flowchart TD
- **[Glossary](./glossary.md)** - Key terminology
- **[FAQ](./faq.md)** - Common questions
- **[Troubleshooting](./troubleshooting.md)** - Problem resolution
- **[Workflows Guide](../workflows/README.md)** - Complete workflow reference
- **[Workflow Documentation](./README.md#-workflow-guides)** - Complete workflow reference
---
## Support & Resources
## Support and Resources
**Community:**
@@ -750,9 +750,8 @@ flowchart TD
**Documentation:**
- [BMM Workflows Guide](../workflows/README.md)
- [Test Architect Guide](./tea-README.md)
- [BMM Module README](../README.md)
- [Test Architect Guide](./test-architecture.md) - Comprehensive testing strategy
- [BMM Module README](../README.md) - Complete module and workflow reference
---

6
bmad/bmm/docs/enterprise-agentic-development.md
View File

@@ -9,7 +9,7 @@
## Table of Contents
- [The Paradigm Shift](#the-paradigm-shift)
- [The Evolving Role of Product Managers & UX Designers](#the-evolving-role-of-product-managers--ux-designers)
- [The Evolving Role of Product Managers and UX Designers](#the-evolving-role-of-product-managers-and-ux-designers)
- [How BMad Method Enables PM/UX Technical Evolution](#how-bmad-method-enables-pmux-technical-evolution)
- [Team Collaboration Patterns](#team-collaboration-patterns)
- [Work Distribution Strategies](#work-distribution-strategies)
@@ -59,7 +59,7 @@
---
## The Evolving Role of Product Managers & UX Designers
## The Evolving Role of Product Managers and UX Designers
### The Future is Now
@@ -672,7 +672,7 @@ PMs write BMad PRDs → Stories auto-fed to cloud AI agents → Parallel impleme
- [FAQ](./faq.md) - Common questions
- [Scale Adaptive System](./scale-adaptive-system.md) - Project levels explained
- [Quick Start Guide](./quick-start.md) - Getting started
- [Workflows Guide](../workflows/README.md) - Complete workflow reference
- [Workflow Documentation](./README.md#-workflow-guides) - Complete workflow reference
- [Agents Guide](./agents-guide.md) - Understanding BMad agents
---

12
bmad/bmm/docs/faq.md
View File

@@ -8,11 +8,11 @@ Quick answers to common questions about the BMad Method Module.
- [Getting Started](#getting-started)
- [Choosing the Right Level](#choosing-the-right-level)
- [Workflows & Phases](#workflows--phases)
- [Workflows and Phases](#workflows-and-phases)
- [Planning Documents](#planning-documents)
- [Implementation](#implementation)
- [Brownfield Development](#brownfield-development)
- [Tools & Technical](#tools--technical)
- [Tools and Technical](#tools-and-technical)
---
@@ -26,7 +26,7 @@ Quick answers to common questions about the BMad Method Module.
- Creates the tracking status file
- Routes you to the correct starting workflow
For experienced users: use the [Quick Reference](./quick-start.md#quick-reference-agent--document-mapping) to go directly to the right agent/workflow.
For experienced users: use the [Quick Reference](./quick-start.md#quick-reference-agent-document-mapping) to go directly to the right agent/workflow.
### Q: Why do I need fresh chats for each workflow?
@@ -108,7 +108,7 @@ The overlap (5-10 stories) is intentional. Choose based on:
---
## Workflows & Phases
## Workflows and Phases
### Q: What's the difference between workflow-status and workflow-init?
@@ -339,7 +339,7 @@ BMM respects your choice - it won't force modernization, but it will offer it.
---
## Tools & Technical
## Tools and Technical
### Q: Why are my Mermaid diagrams not rendering?
@@ -399,7 +399,7 @@ Use them together for best results.
**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.
See [IDE Setup Guides](../../../docs/ide-info/) for configuration specifics.
See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for configuration specifics.
### Q: Can I customize agents?

16
bmad/bmm/docs/glossary.md
View File

@@ -7,11 +7,11 @@ Comprehensive terminology reference for the BMad Method Module.
## Navigation
- [Core Concepts](#core-concepts)
- [Scale & Complexity](#scale--complexity)
- [Scale and Complexity](#scale-and-complexity)
- [Planning Documents](#planning-documents)
- [Workflow & Phases](#workflow--phases)
- [Agents & Roles](#agents--roles)
- [Status & Tracking](#status--tracking)
- [Workflow and Phases](#workflow-and-phases)
- [Agents and Roles](#agents-and-roles)
- [Status and Tracking](#status-and-tracking)
- [Project Types](#project-types)
- [Implementation Terms](#implementation-terms)
@@ -41,7 +41,7 @@ A multi-step guided process that orchestrates AI agent activities to produce spe
---
## Scale & Complexity
## Scale and Complexity
### Quick Flow Track
@@ -99,7 +99,7 @@ Game development equivalent of PRD, created by Game Designer agent for game proj
---
## Workflow & Phases
## Workflow and Phases
### Phase 0: Documentation (Prerequisite)
@@ -135,7 +135,7 @@ Dynamic technical guidance generated for each story via epic-tech-context and st
---
## Agents & Roles
## Agents and Roles
### PM (Product Manager)
@@ -183,7 +183,7 @@ Multi-agent collaboration feature where all installed agents (19+ from BMM, CIS,
---
## Status & Tracking
## Status and Tracking
### bmm-workflow-status.yaml

6
bmad/bmm/docs/quick-spec-flow.md
View File

@@ -277,7 +277,7 @@ For user-facing changes, Quick Spec Flow captures:
---
## Auto-Validation & Quality Assurance
## Auto-Validation and Quality Assurance
Quick Spec Flow **automatically validates** everything:
@@ -543,7 +543,7 @@ Quick Spec Flow is **fully standalone**:
---
## Tips & Best Practices
## Tips and Best Practices
### 1. **Be Specific in Discovery**
@@ -643,7 +643,7 @@ Quick Spec Flow is your **fast path from idea to implementation** for:
## Next Steps
- **Try it now:** Load PM agent and describe a small change
- **Learn more:** See `src/modules/bmm/workflows/README.md` for full BMM workflow guide
- **Learn more:** See the [BMM Workflow Guides](./README.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

10
bmad/bmm/docs/quick-start.md
View File

@@ -37,9 +37,9 @@ The interactive installer will guide you through setup and create a `bmad/` fold
### Step 1: Initialize Your Workflow
1. **Load the Analyst agent** in your IDE - See your IDE-specific instructions in [docs/ide-info](../docs/ide-info/) for how to activate agents:
- [Claude Code](../docs/ide-info/claude-code.md)
- [VS Code/Cursor/Windsurf](../docs/ide-info/) - Check your IDE folder
1. **Load the Analyst agent** in your IDE - See your IDE-specific instructions in [docs/ide-info](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for how to activate agents:
- [Claude Code](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/docs/ide-info/claude-code.md)
- [VS Code/Cursor/Windsurf](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) - Check your IDE folder
- Other IDEs also supported
2. **Wait for the agent's menu** to appear
3. **Tell the agent**: "Run workflow-init" or type "\*workflow-init" or select the menu item number
@@ -107,7 +107,7 @@ The next TRULY REQUIRED step is:
When an agent tells you to run a workflow (like `prd`):
1. **Start a new chat** with the specified agent (e.g., PM) - See [docs/ide-info](../docs/ide-info/) for your IDE's specific instructions
1. **Start a new chat** with the specified agent (e.g., PM) - See [docs/ide-info](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for your IDE's specific instructions
2. **Wait for the menu** to appear
3. **Tell the agent** to run it using any of these formats:
- Type the shorthand: `*prd`
@@ -350,7 +350,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 Workflows README](../src/modules/bmm/workflows/README.md)
- **Complete guide**: [BMM Workflow Documentation](./README.md#-workflow-guides)
- **YouTube tutorials**: [BMad Code Channel](https://www.youtube.com/@BMadCode)
---

2
bmad/bmm/docs/scale-adaptive-system.md
View File

@@ -592,7 +592,7 @@ Run `workflow-init` on existing projects to migrate to new tracking system. It d
- **[Brownfield Guide](./brownfield-guide.md)** - Existing codebase workflows
- **[Glossary](./glossary.md)** - Complete terminology
- **[FAQ](./faq.md)** - Common questions
- **[Workflows Guide](../workflows/README.md)** - Complete workflow reference
- **[Workflows Guide](./README.md#-workflow-guides)** - Complete workflow reference
---

94
bmad/bmm/docs/tea-README.md → bmad/bmm/docs/test-architecture.md
View File

@@ -14,44 +14,62 @@ last-redoc-date: 2025-10-14
TEA integrates across the entire BMad development lifecycle, providing quality assurance at every phase:
```
┌──────────────────────────────────────────────────────────┐
│ BMM Phase 2: PLANNING │
│ │
│ PM: *prd │
│ ↓ │
│ TEA: *framework ──→ *ci ──→ *test-design │
│ └─────────┬─────────────┘ │
│ │ (Setup once per project) │
└─────────────────┼──────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ BMM Phase 4: IMPLEMENTATION │
│ (Per Story Cycle) │
│ │
│ ┌─→ SM: *create-story │
│ │ ↓ │
│ │ TEA: *atdd (optional, before dev) │
│ │ ↓ │
│ │ DEV: implements story │
│ │ ↓ │
│ │ TEA: *automate ──→ *test-review (optional) │
│ │ ↓ │
│ │ TEA: *trace (refresh coverage) │
│ │ ↓ │
│ └───[next story] │
└─────────────────┼──────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ EPIC/RELEASE GATE │
│ │
│ TEA: *nfr-assess (if not done earlier) │
│ ↓ │
│ TEA: *test-review (final audit, optional) │
│ ↓ │
│ TEA: *trace (Phase 2: Gate) ──→ PASS | CONCERNS | FAIL | WAIVED │
│ │
└──────────────────────────────────────────────────────────┘
```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</b>"]
Framework["<b>TEA: *framework</b>"]
CI["<b>TEA: *ci</b>"]
TestDesign["<b>TEA: *test-design</b>"]
PM --> Framework
Framework --> CI
CI --> TestDesign
SetupNote["<b>Setup once per project</b>"]
TestDesign -.-> SetupNote
end
subgraph Phase4["<b>Phase 4: IMPLEMENTATION - Per Story Cycle</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>"]
CreateStory --> ATDD
ATDD --> DevImpl
DevImpl --> Automate
Automate --> TestReview1
TestReview1 --> Trace1
Trace1 -.->|next story| CreateStory
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 --> Phase4
Phase4 --> Gate
style Phase2 fill:#bbdefb,stroke:#0d47a1,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
```
### TEA Integration with BMad v6 Workflow

12
bmad/bmm/docs/troubleshooting.md
View File

@@ -30,18 +30,18 @@ flowchart TD
## Table of Contents
- [Setup & Installation Issues](#setup--installation-issues)
- [Setup and Installation Issues](#setup-and-installation-issues)
- [Level Detection Problems](#level-detection-problems)
- [Workflow Issues](#workflow-issues)
- [Context & Documentation Issues](#context--documentation-issues)
- [Context and Documentation Issues](#context-and-documentation-issues)
- [Implementation Issues](#implementation-issues)
- [File & Path Issues](#file--path-issues)
- [File and Path Issues](#file-and-path-issues)
- [Agent Behavior Issues](#agent-behavior-issues)
- [Integration Issues (Brownfield)](#integration-issues-brownfield)
---
## Setup & Installation Issues
## Setup and Installation Issues
### Problem: BMM not found after installation
@@ -238,7 +238,7 @@ workflow-init asks: "Is this work in progress or previous effort?"
---
## Context & Documentation Issues
## Context and Documentation Issues
### Problem: AI agents lack codebase understanding (Brownfield)
@@ -393,7 +393,7 @@ For most brownfield projects, **Deep scan is sufficient**.
---
## File & Path Issues
## File and Path Issues
### Problem: Output files in wrong location

92
bmad/bmm/docs/workflows-analysis.md
View File

@@ -1,7 +1,5 @@
# BMM Analysis Workflows (Phase 1)
**Reading Time:** ~12 minutes
## Overview
Phase 1 (Analysis) workflows are **optional** exploration and discovery tools that help you understand your project space before committing to detailed planning. These workflows facilitate creative thinking, market validation, and strategic alignment.
@@ -17,17 +15,61 @@ Phase 1 (Analysis) workflows are **optional** exploration and discovery tools th
- Continuing an existing project with clear requirements
- Working on well-defined features with known solutions
- Operating under strict time constraints where discovery is complete
- Working under strict constraints where discovery is complete
---
## Phase 1 Workflow Map
```mermaid
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
graph TB
subgraph Creative["<b>CREATIVE EXPLORATION</b>"]
direction TB
BrainstormProject["<b>Analyst: brainstorm-project</b><br/>Multi-track solution exploration"]
BrainstormGame["<b>Analyst: brainstorm-game</b><br/>Game concept generation"]
end
subgraph Strategic["<b>STRATEGIC PLANNING</b>"]
direction TB
ProductBrief["<b>Analyst: product-brief</b><br/>Product vision and strategy"]
GameBrief["<b>Game Designer: game-brief</b><br/>Game vision capture"]
end
subgraph Research["<b>RESEARCH AND INVESTIGATION</b>"]
direction TB
ResearchWF["<b>Analyst: research</b><br/>Market, technical, competitive analysis"]
end
Creative -.->|Software projects| ProductBrief
Creative -.->|Game projects| GameBrief
BrainstormProject -.->|May inform| ResearchWF
BrainstormGame -.->|May inform| ResearchWF
ResearchWF -.->|Feeds into| ProductBrief
ResearchWF -.->|Feeds into| GameBrief
style Creative fill:#e1f5fe,stroke:#01579b,stroke-width:3px,color:#000
style Strategic fill:#f3e5f5,stroke:#4a148c,stroke-width:3px,color:#000
style Research fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
style BrainstormProject fill:#81d4fa,stroke:#0277bd,stroke-width:2px,color:#000
style BrainstormGame fill:#81d4fa,stroke:#0277bd,stroke-width:2px,color:#000
style ProductBrief fill:#ce93d8,stroke:#6a1b9a,stroke-width:2px,color:#000
style GameBrief fill:#ce93d8,stroke:#6a1b9a,stroke-width:2px,color:#000
style ResearchWF fill:#fff59d,stroke:#f57f17,stroke-width:2px,color:#000
```
---
## Quick Reference
| Workflow | Agent | Duration | Required | Purpose |
| ------------------ | ------- | --------- | ----------- | ----------------------------------------------------------- |
| brainstorm-project | Analyst | 30-60 min | No | Explore solution approaches and architectures |
| brainstorm-game | Analyst | 45-90 min | No | Generate game concepts using creative techniques |
| product-brief | PM | 60-90 min | Recommended | Define product vision and strategy |
| game-brief | PM | 60-90 min | Recommended | Capture game vision before GDD |
| research | Analyst | Varies | No | Multi-type research system (market, technical, competitive) |
| Workflow | Agent | Required | Purpose |
| ------------------ | ------------- | ----------- | ----------------------------------------------------------- |
| brainstorm-project | Analyst | No | Explore solution approaches and architectures |
| brainstorm-game | Analyst | No | Generate game concepts using creative techniques |
| product-brief | Analyst | Recommended | Define product vision and strategy |
| game-brief | Game Designer | Recommended | Capture game vision before GDD |
| research | Analyst | No | Multi-type research system (market, technical, competitive) |
---
@@ -40,7 +82,6 @@ Generate multiple solution approaches for software projects through parallel ide
**Agent:** Analyst
**Phase:** 1 (Analysis)
**Required:** No
**Typical Duration:** 30-60 minutes
### When to Use
@@ -125,7 +166,6 @@ Generate and refine game concepts through systematic creative exploration using
**Agent:** Analyst
**Phase:** 1 (Analysis)
**Required:** No
**Typical Duration:** 45-90 minutes
### When to Use
@@ -196,10 +236,9 @@ Each method generates distinct artifacts that are then evaluated against design
Interactive product brief creation that guides users through defining their product vision with multiple input sources and conversational collaboration.
**Agent:** PM
**Agent:** Analyst
**Phase:** 1 (Analysis)
**Required:** Recommended (skip only if PRD already exists)
**Typical Duration:** 60-90 minutes (Interactive), 20-30 minutes (YOLO)
### When to Use
@@ -222,13 +261,13 @@ Interactive product brief creation that guides users through defining their prod
- Step-by-step collaborative development
- Probing questions to refine thinking
- Deep exploration of problem/solution fit
- 60-90 minutes with high-quality output
- High-quality output with thorough exploration
**YOLO Mode**:
- AI generates complete draft from initial context
- User reviews and refines sections iteratively
- 20-30 minutes for rapid draft
- Faster for rapid draft generation
- Best for time-constrained situations or when you have clear vision
### Process Overview
@@ -317,10 +356,9 @@ Interactive product brief creation that guides users through defining their prod
Lightweight, interactive brainstorming and planning session that captures game vision before diving into detailed Game Design Documents.
**Agent:** PM
**Agent:** Game Designer
**Phase:** 1 (Analysis)
**Required:** Recommended for game projects
**Typical Duration:** 60-90 minutes
### When to Use
@@ -338,15 +376,14 @@ Lightweight, interactive brainstorming and planning session that captures game v
### Comparison: Game Brief vs GDD
| Aspect | Game Brief | GDD |
| --------------- | --------------------------- | ------------------------- |
| Purpose | Validate concept | Design for implementation |
| Detail Level | High-level vision | Detailed specifications |
| Time Investment | 1-2 hours | 4-10 hours |
| Audience | Self, team, stakeholders | Development team |
| Scope | Concept validation | Implementation roadmap |
| Format | Conversational, exploratory | Structured, comprehensive |
| Output | 3-5 pages | 10-30+ pages |
| Aspect | Game Brief | GDD |
| ------------ | --------------------------- | ------------------------- |
| Purpose | Validate concept | Design for implementation |
| Detail Level | High-level vision | Detailed specifications |
| Audience | Self, team, stakeholders | Development team |
| Scope | Concept validation | Implementation roadmap |
| Format | Conversational, exploratory | Structured, comprehensive |
| Output | Concise vision document | Comprehensive design doc |
### Comparison: Game Brief vs Product Brief
@@ -441,7 +478,6 @@ Comprehensive, adaptive multi-type research system that consolidates various res
**Agent:** Analyst
**Phase:** 1 (Analysis)
**Required:** No
**Typical Duration:** Varies by type (Quick: 30-60 min, Standard: 2-4 hours, Comprehensive: 4-8 hours)
### Research Types

1876
bmad/bmm/docs/workflows-implementation.md
View File

File diff suppressed because it is too large Load Diff

109
bmad/bmm/docs/workflows-planning.md
View File

@@ -1,25 +1,90 @@
# BMM Planning Workflows (Phase 2)
**Reading Time:** ~15 minutes
## Overview
Phase 2 (Planning) workflows are **required** for all projects. They transform strategic vision into actionable requirements that guide implementation. BMM uses a **scale-adaptive planning system** where the workflow automatically selects the right level of detail based on project complexity.
**Key principle:** One workflow to rule them all - `plan-project` intelligently routes to the appropriate planning flow based on project characteristics.
---
## Phase 2 Planning Flow
```mermaid
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
graph TB
Entry["<b>START: plan-project</b><br/>Discovery and routing"]
subgraph QuickFlow["<b>QUICK FLOW (Levels 0-1)</b>"]
TechSpec["<b>PM: tech-spec</b><br/>Lightweight spec for simple changes"]
end
subgraph StandardFlow["<b>STANDARD PLANNING (Levels 2-4)</b>"]
PRD["<b>PM: prd</b><br/>Strategic PRD"]
GDD["<b>Game Designer: gdd</b><br/>Game design document"]
Narrative["<b>Game Designer: narrative</b><br/>Story-driven design"]
UXDesign["<b>UX Designer: ux</b><br/>UX-first specification"]
Epics["<b>PM: create-epics-and-stories</b><br/>Break requirements into epics and stories"]
end
subgraph Updates["<b>STORY UPDATES (Anytime After Epics Created)</b>"]
CorrectCourse["<b>PM/SM: correct-course</b><br/>Update epics/stories mid-stream"]
end
Entry -->|Level 0-1<br/>Simple| QuickFlow
Entry -->|Level 2-4<br/>Software| PRD
Entry -->|Level 2-4<br/>Game| GDD
Entry -->|Level 2-4<br/>Story-driven| Narrative
Entry -->|Level 2-4<br/>UX-first| UXDesign
PRD --> Epics
GDD --> Epics
Narrative --> Epics
UXDesign -.->|May update| Epics
Epics --> Phase3["<b>Phase 3: Architecture</b>"]
Phase3 -.->|May update| Epics
QuickFlow --> Phase4["<b>Phase 4: Implementation</b>"]
Phase3 --> Phase4
Phase4 -.->|Significant changes| CorrectCourse
CorrectCourse -.->|Updates| Epics
style Entry fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
style QuickFlow fill:#c5e1a5,stroke:#33691e,stroke-width:3px,color:#000
style StandardFlow fill:#e1bee7,stroke:#6a1b9a,stroke-width:3px,color:#000
style Updates fill:#ffcdd2,stroke:#c62828,stroke-width:3px,color:#000
style Phase3 fill:#90caf9,stroke:#0d47a1,stroke-width:2px,color:#000
style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
style TechSpec fill:#aed581,stroke:#1b5e20,stroke-width:2px,color:#000
style PRD fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
style GDD fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
style Narrative fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
style UXDesign fill:#ce93d8,stroke:#4a148c,stroke-width:2px,color:#000
style Epics fill:#ba68c8,stroke:#6a1b9a,stroke-width:3px,color:#000
style CorrectCourse fill:#ef5350,stroke:#c62828,stroke-width:2px,color:#000
```
---
## Quick Reference
| Workflow | Project Levels | Duration | Purpose |
| ------------- | -------------- | ---------- | --------------------------------------- |
| **prd** | 2-4 | 2-6 hours | Strategic PRD + tactical epic breakdown |
| **tech-spec** | 0-1 | 30-90 min | Lightweight technical specification |
| **gdd** | 2-4 (games) | 4-10 hours | Complete game design document |
| **narrative** | 2-4 (story) | 3-8 hours | Story-driven game/experience design |
| **ux** | 2-4 (UX-heavy) | 3-6 hours | UX-first design specification |
| Workflow | Agent | Project Levels | Purpose |
| ---------------------------- | ------------- | -------------- | ---------------------------------------------------- |
| **prd** | PM | 2-4 | Strategic PRD |
| **create-epics-and-stories** | PM | 2-4 | Break PRD/GDD into epics and stories (standalone OK) |
| **tech-spec** | PM | 0-1 | Lightweight technical specification |
| **gdd** | Game Designer | 2-4 (games) | Complete game design document |
| **narrative** | Game Designer | 2-4 (story) | Story-driven game/experience design |
| **ux** | UX Designer | 2-4 (UX-heavy) | UX-first design specification |
**Note:** The `plan-project` workflow is your single entry point. It automatically routes to the right planning workflow based on your answers to discovery questions.
**Critical:** After PRD/GDD/Narrative complete, you must run `create-epics-and-stories` to generate user stories (can be done in same chat or separate chat later). These stories can be updated anytime via UX-Design, Architecture decisions, or `correct-course` during implementation.
---
## Understanding Scale-Adaptive Planning
@@ -73,7 +138,6 @@ Single unified entry point for all planning workflows. Uses conversational disco
**Agent:** PM (orchestrates other agents as needed)
**Phase:** 2 (Planning)
**Required:** Yes (for all projects)
**Typical Duration:** Varies by target workflow
### When to Use
@@ -161,28 +225,24 @@ ELSE:
- **Input**: "Fix null pointer exception in user service"
- **Discovery**: Level 0 (single atomic change)
- **Route**: tech-spec (Quick Spec Flow)
- **Duration**: 20 minutes
**Scenario 2: E-commerce Checkout**
- **Input**: "Build complete checkout flow with payment processing"
- **Discovery**: Level 3 (large feature set), feature-focused
- **Route**: prd (Standard depth)
- **Duration**: 4 hours
**Scenario 3: Roguelike Card Game**
- **Input**: "Roguelike card battler with emotional narrative"
- **Discovery**: Level 3 (large feature set), game project
- **Route**: gdd
- **Duration**: 6 hours
**Scenario 4: Story-Driven Adventure**
- **Input**: "Narrative adventure game with branching story"
- **Discovery**: Level 3, story-central
- **Route**: narrative (then gdd for mechanics)
- **Duration**: 8 hours total
---
@@ -195,7 +255,6 @@ Lightweight technical specification for Levels 0-1 projects (single changes, sim
**Agent:** Architect
**Phase:** 2 (Planning)
**Project Levels:** 0-1
**Typical Duration:** 30-90 minutes
### When to Use
@@ -322,11 +381,6 @@ Strategic PRD with tactical epic breakdown for Levels 2-4 projects. Unified work
**Agent:** PM (with Architect and Analyst support)
**Phase:** 2 (Planning)
**Project Levels:** 2-4
**Typical Duration:**
- Level 2: 2-3 hours (Lightweight)
- Level 3: 3-5 hours (Standard)
- Level 4: 5-8 hours (Comprehensive)
### When to Use
@@ -488,11 +542,6 @@ Complete game design document for Levels 2-4 game projects, adapted from industr
**Agent:** PM (Game Designer persona)
**Phase:** 2 (Planning)
**Project Levels:** 2-4 (games)
**Typical Duration:**
- Level 2: 3-4 hours (Small indie game)
- Level 3: 5-7 hours (Medium game)
- Level 4: 8-12 hours (Large/commercial game)
### When to Use
@@ -666,11 +715,6 @@ Story-driven design workflow for games and experiences where narrative is centra
**Agent:** PM (Narrative Designer persona) + Creative Problem Solver (CIS)
**Phase:** 2 (Planning)
**Project Levels:** 2-4 (story-driven projects)
**Typical Duration:**
- Level 2: 2-4 hours (Linear narrative)
- Level 3: 4-6 hours (Branching narrative)
- Level 4: 6-10 hours (Complex branching with multiple arcs)
### When to Use
@@ -825,11 +869,6 @@ UX specification workflow for projects where user experience is the primary diff
**Agent:** UX Designer
**Phase:** 2 (Planning)
**Project Levels:** 2-4 (UX-heavy projects)
**Typical Duration:**
- Level 2: 2-3 hours (Single feature UX)
- Level 3: 4-5 hours (Multi-screen experience)
- Level 4: 6-8 hours (Platform-wide UX system)
### When to Use

62
bmad/bmm/docs/workflows-solutioning.md
View File

@@ -1,19 +1,56 @@
# BMM Solutioning Workflows (Phase 3)
**Reading Time:** ~8 minutes
## Overview
Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into **how** to build it (technical design). This phase is **required for Levels 3-4** and **optional for Level 2** projects.
**Key principle:** Prevent agent conflicts by making architectural decisions explicit and documented before implementation begins.
---
## Phase 3 Solutioning Flow
```mermaid
%%{init: {'theme':'base', 'themeVariables': { 'primaryColor':'#fff','primaryTextColor':'#000','primaryBorderColor':'#000','lineColor':'#000','fontSize':'16px','fontFamily':'arial'}}}%%
graph TB
FromPRD["<b>FROM Phase 2</b><br/>PRD/GDD/Narrative/UX complete"]
subgraph Solutioning["<b>PHASE 3: SOLUTIONING</b>"]
direction TB
Architecture["<b>Architect: architecture</b><br/>Technical design and decisions"]
GateCheck["<b>Architect: solutioning-gate-check</b><br/>Validation before implementation"]
end
subgraph Optional["<b>OPTIONAL PATHS</b>"]
direction LR
Level2Skip["<b>Level 2:</b><br/>Skip if straightforward"]
end
FromPRD --> Architecture
Architecture --> GateCheck
GateCheck -->|PASS| Phase4["<b>Phase 4: Implementation</b>"]
GateCheck -->|CONCERNS/FAIL| Architecture
FromPRD -.->|Level 2 only| Level2Skip
Level2Skip -.-> Phase4
style FromPRD fill:#e1bee7,stroke:#6a1b9a,stroke-width:2px,color:#000
style Solutioning fill:#90caf9,stroke:#0d47a1,stroke-width:3px,color:#000
style Optional fill:#fff9c4,stroke:#f57f17,stroke-width:3px,color:#000
style Phase4 fill:#ffcc80,stroke:#e65100,stroke-width:2px,color:#000
style Architecture fill:#64b5f6,stroke:#0d47a1,stroke-width:2px,color:#000
style GateCheck fill:#64b5f6,stroke:#0d47a1,stroke-width:2px,color:#000
style Level2Skip fill:#fff59d,stroke:#f57f17,stroke-width:2px,color:#000
```
---
## Quick Reference
| Workflow | Project Levels | Duration | Purpose |
| -------------------------- | -------------- | --------- | ------------------------------------------- |
| **architecture** | 2-4 | 2-6 hours | Technical architecture and design decisions |
| **solutioning-gate-check** | 3-4 | 15-30 min | Validate planning/solutioning completeness |
| Workflow | Project Levels | Purpose |
| -------------------------- | -------------- | ------------------------------------------- |
| **architecture** | 2-4 | Technical architecture and design decisions |
| **solutioning-gate-check** | 3-4 | Validate planning/solutioning completeness |
**When to Skip Solutioning:**
@@ -86,11 +123,6 @@ Collaborative architectural decision facilitation that produces a decision-focus
**Phase:** 3 (Solutioning)
**Project Levels:** 2-4
**Required:** Level 3-4, Optional Level 2
**Typical Duration:**
- Level 2: 1-2 hours (Simple architecture)
- Level 3: 2-4 hours (Standard architecture)
- Level 4: 4-8 hours (Complex architecture with ADRs)
### When to Use
@@ -341,7 +373,6 @@ Systematically validate that all planning and solutioning phases are complete an
**Phase:** 3 (Solutioning)
**Project Levels:** 3-4
**Required:** Level 3-4 only
**Typical Duration:** 15-30 minutes
### When to Use
@@ -544,21 +575,20 @@ Optional:
1. **Critical**: Architecture missing security architecture section
- **Impact**: Epic 1 (Auth) and Epic 4 (Checkout) lack security guidance
- **Recommendation**: Complete security architecture (2 hours)
- **Recommendation**: Complete security architecture
2. **High**: Payment gateway not selected
- **Impact**: Epic 4 (Checkout) cannot proceed
- **Recommendation**: Add ADR for payment gateway selection (1 hour)
- **Recommendation**: Add ADR for payment gateway selection
3. **Medium**: Epic 2, Story 3 too large
- **Impact**: Risk of story scope creep
- **Recommendation**: Split into 2 stories (30 min)
- **Recommendation**: Split into 2 stories
**Gate Decision:** CONCERNS ⚠️
- **Rationale**: Critical and high gaps block Epic 1 and Epic 4
- **Action**: Resolve gaps #1 and #2 before starting implementation
- **Timeline**: Address in 3 hours, then re-run gate check
**Next Steps:**