bmad-method 6.0.0-alpha.4 → 6.0.0-alpha.6

package/{bmad/bmm/testarch/README.md → src/modules/bmm/docs/test-architecture.md}

@@ -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

package/src/modules/bmm/docs/troubleshooting.md

@@ -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
 
@@ -545,7 +545,7 @@ To change locations, edit config.yaml then re-run workflows.
    - Read docs/architecture.md (from document-project)
    - Understand current system design
 3. **For Level 3-4**:
-   - Run architecture-review workflow before planning
+   - Run validate-architecture workflow before planning
    - Use integration-planning workflow
 4. **Explicitly document integration strategy** in architecture:
    - How new components fit existing structure

package/src/modules/bmm/docs/workflows-analysis.md

@@ -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