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

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

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

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

@@ -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:**
 
@@ -70,7 +107,7 @@ Phase 3 (Solutioning) workflows translate **what** to build (from Planning) into
 **Level 3-4 (Required Solutioning):**
 
 - Planning: Standard/Comprehensive PRD
-- Solutioning: **Required** architecture + epic tech-spec
+- Solutioning: **Required** architecture + epic-tech-context
 - Gate Check: **Required** solutioning-gate-check
 - Implementation: dev-story guided by architecture
 
@@ -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:**
 

package/src/modules/bmm/tasks/daily-standup.xml

@@ -64,7 +64,7 @@
       <i>Primary: Sarah (PO), Bob (SM), James (Dev)</i>
       <i>Secondary: Murat (TEA)</i>
     </context>
-    <context type="architecture-review">
+    <context type="validate-architecture">
       <i>Primary: Winston (Architect), James (Dev), Murat (TEA)</i>
       <i>Secondary: Sarah (PO)</i>
     </context>

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md

@@ -9,26 +9,8 @@
 <critical>Communicate all responses in {communication_language} and tailor to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
 <critical>SAVE PROGRESS after each major step - use <template-output> tags throughout</critical>
-
 <critical>DOCUMENT OUTPUT: Professional, specific, actionable UX design decisions WITH RATIONALE. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
-
-## 📚 Input Document Discovery
-
-This workflow requires: PRD or product brief, and may reference epics/stories, brainstorming documents, or brownfield project documentation.
-
-**Discovery Process** (execute for each referenced document):
-
-1. **Search for whole document first** - Use fuzzy file matching to find the complete document
-2. **Check for sharded version** - If whole document not found, look for `{doc-name}/index.md`
-3. **If sharded version found**:
-   - Read `index.md` to understand the document structure
-   - Read ALL section files listed in the index
-   - Treat the combined content as if it were a single document
-4. **Brownfield projects**: The `document-project` workflow always creates `{output_folder}/docs/index.md`
-
-**Priority**: If both whole and sharded versions exist, use the whole document.
-
-**Fuzzy matching**: Be flexible with document names - users may use variations in naming conventions.
+<critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</critical>
 
 <step n="0" goal="Validate workflow readiness" tag="workflow-status">
 <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>

package/src/modules/bmm/workflows/2-plan-workflows/prd/checklist.md

@@ -234,21 +234,22 @@
 - [ ] Dependencies on external systems documented
 - [ ] Data requirements specified
 
-### Level-Appropriate Detail
+### Track-Appropriate Detail
 
-**If Level 2:**
-
-- [ ] PRD supports lightweight tech-spec workflow
-- [ ] 5-15 story scope reasonable for project size
-- [ ] Complexity appropriate for small team/solo dev
-
-**If Level 3-4:**
+**If BMad Method:**
 
 - [ ] PRD supports full architecture workflow
 - [ ] Epic structure supports phased delivery
-- [ ] Scope appropriate for team-based development
+- [ ] Scope appropriate for product/platform development
 - [ ] Clear value delivery through epic sequence
 
+**If Enterprise Method:**
+
+- [ ] PRD addresses enterprise requirements (security, compliance, multi-tenancy)
+- [ ] Epic structure supports extended planning phases
+- [ ] Scope includes security, devops, and test strategy considerations
+- [ ] Clear value delivery with enterprise gates
+
 ---
 
 ## 10. Quality and Polish

package/src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md

@@ -9,55 +9,44 @@
 
 ## Overview
 
-This document provides the detailed epic breakdown for {{project_name}}, expanding on the high-level epic list in the [PRD](./PRD.md).
+This document provides the complete epic and story breakdown for {{project_name}}, decomposing the requirements from the [PRD](./PRD.md) into implementable stories.
 
-Each epic includes:
+{{epics_summary}}
 
-- Expanded goal and value proposition
-- Complete story breakdown with user stories
-- Acceptance criteria for each story
-- Story sequencing and dependencies
+---
 
-**Epic Sequencing Principles:**
+<!-- Repeat for each epic (N = 1, 2, 3...) -->
 
-- Epic 1 establishes foundational infrastructure and initial functionality
-- Subsequent epics build progressively, each delivering significant end-to-end value
-- Stories within epics are vertically sliced and sequentially ordered
-- No forward dependencies - each story builds only on previous work
+## Epic {{N}}: {{epic_title_N}}
 
----
+{{epic_goal_N}}
 
-{{epic_details}}
+<!-- Repeat for each story (M = 1, 2, 3...) within epic N -->
 
----
+### Story {{N}}.{{M}}: {{story_title_N_M}}
 
-## Story Guidelines Reference
+As a {{user_type}},
+I want {{capability}},
+So that {{value_benefit}}.
 
-**Story Format:**
+**Acceptance Criteria:**
 
-```
-**Story [EPIC.N]: [Story Title]**
+**Given** {{precondition}}
+**When** {{action}}
+**Then** {{expected_outcome}}
 
-As a [user type],
-I want [goal/desire],
-So that [benefit/value].
+**And** {{additional_criteria}}
 
-**Acceptance Criteria:**
-1. [Specific testable criterion]
-2. [Another specific criterion]
-3. [etc.]
+**Prerequisites:** {{dependencies_on_previous_stories}}
+
+**Technical Notes:** {{implementation_guidance}}
 
-**Prerequisites:** [Dependencies on previous stories, if any]
-```
+<!-- End story repeat -->
 
-**Story Requirements:**
+---
 
-- **Vertical slices** - Complete, testable functionality delivery
-- **Sequential ordering** - Logical progression within epic
-- **No forward dependencies** - Only depend on previous work
-- **AI-agent sized** - Completable in 2-4 hour focused session
-- **Value-focused** - Integrate technical enablers into value-delivering stories
+<!-- End epic repeat -->
 
 ---
 
-**For implementation:** Use the `create-story` workflow to generate individual story implementation plans from this epic breakdown.
+_For implementation: Use the `create-story` workflow to generate individual story implementation plans from this epic breakdown._