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

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

@@ -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-implementation.md

@@ -10,18 +10,18 @@ Phase 4 (Implementation) workflows manage the iterative sprint-based development
 
 ## Quick Reference
 
-| Workflow              | Agent     | Duration       | Purpose                              |
-| --------------------- | --------- | -------------- | ------------------------------------ |
-| **sprint-planning**   | SM        | 30-60 min      | Initialize sprint tracking file      |
-| **epic-tech-context** | Architect | 15-30 min/epic | Epic-specific technical guidance     |
-| **create-story**      | SM        | 10-20 min      | Create next story from epics         |
-| **story-context**     | PM        | 10-15 min      | Assemble dynamic story context       |
-| **dev-story**         | DEV       | 2-8 hours      | Implement story with tests           |
-| **code-review**       | DEV       | 30-60 min      | Senior dev review of completed story |
-| **correct-course**    | SM        | 30-90 min      | Handle mid-sprint changes            |
-| **retrospective**     | SM        | 60-90 min      | Post-epic review and lessons         |
-| **workflow-status**   | All       | 2-5 min        | Check "what should I do now?"        |
-| **document-project**  | Analyst   | 1-3 hours      | Document brownfield projects         |
+| Workflow              | Agent   | Duration       | Purpose                              |
+| --------------------- | ------- | -------------- | ------------------------------------ |
+| **sprint-planning**   | SM      | 30-60 min      | Initialize sprint tracking file      |
+| **epic-tech-context** | SM      | 15-30 min/epic | Epic-specific technical guidance     |
+| **create-story**      | SM      | 10-20 min      | Create next story from epics         |
+| **story-context**     | PM      | 10-15 min      | Assemble dynamic story context       |
+| **dev-story**         | DEV     | 2-8 hours      | Implement story with tests           |
+| **code-review**       | DEV     | 30-60 min      | Senior dev review of completed story |
+| **correct-course**    | SM      | 30-90 min      | Handle mid-sprint changes            |
+| **retrospective**     | SM      | 60-90 min      | Post-epic review and lessons         |
+| **workflow-status**   | All     | 2-5 min        | Check "what should I do now?"        |
+| **document-project**  | Analyst | 1-3 hours      | Document brownfield projects         |
 
 ---
 
@@ -69,13 +69,12 @@ Every story moves through this lifecycle:
 
 Phase 4 involves coordination between agents:
 
-| Agent         | Primary Workflows                                            | Role                        |
-| ------------- | ------------------------------------------------------------ | --------------------------- |
-| **SM**        | sprint-planning, create-story, correct-course, retrospective | Orchestration, tracking     |
-| **Architect** | epic-tech-context                                            | Technical guidance per epic |
-| **PM**        | story-context                                                | Context assembly            |
-| **DEV**       | dev-story, code-review                                       | Implementation, quality     |
-| **Analyst**   | document-project                                             | Documentation (brownfield)  |
+| Agent       | Primary Workflows                                                               | Role                       |
+| ----------- | ------------------------------------------------------------------------------- | -------------------------- |
+| **SM**      | sprint-planning, epic-tech-context, create-story, correct-course, retrospective | Orchestration, tracking    |
+| **PM**      | story-context                                                                   | Context assembly           |
+| **DEV**     | dev-story, code-review                                                          | Implementation, quality    |
+| **Analyst** | document-project                                                                | Documentation (brownfield) |
 
 ---
 
@@ -256,7 +255,7 @@ epics:
 
 Generate epic-specific technical context document that provides implementation guidance, patterns, and technical decisions for a single epic. Bridges architecture and story implementation.
 
-**Agent:** Architect
+**Agent:** SM (Scrum Master)
 **Phase:** 4 (Implementation)
 **Required:** Optional (recommended for Level 3-4)
 **Typical Duration:** 15-30 minutes per epic
@@ -974,7 +973,7 @@ Tests Added:
 
 ### Purpose
 
-Perform a Senior Developer code review on a completed story flagged Ready for Review, leveraging story-context, epic tech-spec, repo docs, MCP servers for latest best-practices, and web search as fallback.
+Perform a Senior Developer code review on a completed story flagged Ready for Review, leveraging story-context, epic-tech-context, repo docs, MCP servers for latest best-practices, and web search as fallback.
 
 **Agent:** DEV (Senior Developer persona)
 **Phase:** 4 (Implementation)

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

@@ -70,7 +70,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
 

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._