bmad-method 6.0.0-alpha.7 → 6.0.0-alpha.9

package/src/modules/bmm/workflows/2-plan-workflows/create-ux-design/workflow.yaml

@@ -4,7 +4,7 @@ description: "Collaborative UX design facilitation workflow that creates excepti
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
 communication_language: "{config_source}:communication_language"
@@ -25,28 +25,34 @@ brainstorm_file: "{output_folder}/brainstorming.md or brainstorm.md or ideation.
 
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version
+# Strategy: How to load sharded documents (FULL_LOAD, SELECTIVE_LOAD, INDEX_GUIDED)
 input_file_patterns:
   prd:
     whole: "{output_folder}/*prd*.md"
     sharded: "{output_folder}/*prd*/index.md"
+    load_strategy: "FULL_LOAD"
 
   product_brief:
     whole: "{output_folder}/*brief*.md"
     sharded: "{output_folder}/*brief*/index.md"
+    load_strategy: "FULL_LOAD"
 
   epics:
     whole: "{output_folder}/*epic*.md"
     sharded: "{output_folder}/*epic*/index.md"
+    load_strategy: "FULL_LOAD"
 
   brainstorming:
     whole: "{output_folder}/*brainstorm*.md"
     sharded: "{output_folder}/*brainstorm*/index.md"
+    load_strategy: "FULL_LOAD"
 
   document_project:
     sharded: "{output_folder}/docs/index.md"
+    load_strategy: "INDEX_GUIDED"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/create-ux-design"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design"
 instructions: "{installed_path}/instructions.md"
 validation: "{installed_path}/checklist.md"
 template: "{installed_path}/ux-design-template.md"
@@ -64,10 +70,10 @@ web_bundle:
   description: "Collaborative UX design facilitation workflow that creates exceptional user experiences through visual exploration and informed decision-making. Unlike template-driven approaches, this workflow facilitates discovery, generates visual options, and collaboratively designs the UX with the user at every step."
   author: "BMad"
 
-  # Core workflow files (bmad/-relative paths)
-  instructions: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
-  validation: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
-  template: "bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
+  # Core workflow files ({bmad_folder}/-relative paths)
+  instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
+  validation: "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
+  template: "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
 
   # Default configuration values (can be overridden during bundle setup)
   defaults:
@@ -85,9 +91,9 @@ web_bundle:
   # Complete file list - ALL files this workflow depends on
   web_bundle_files:
     # Core workflow files
-    - "bmad/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
-    - "bmad/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
-    - "bmad/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
+    - "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/instructions.md"
+    - "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/checklist.md"
+    - "{bmad_folder}/bmm/workflows/2-plan-workflows/create-ux-design/ux-design-template.md"
 
     # Task dependencies (referenced in instructions.md)
-    - "bmad/core/tasks/workflow.xml"
+    - "{bmad_folder}/core/tasks/workflow.xml"

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

@@ -17,7 +17,7 @@
 ### Core Sections Present
 
 - [ ] Executive Summary with vision alignment
-- [ ] Product magic essence clearly articulated
+- [ ] Product differentiator clearly articulated
 - [ ] Project classification (type, domain, complexity)
 - [ ] Success criteria defined
 - [ ] Product scope (MVP, Growth, Vision) clearly delineated
@@ -38,7 +38,7 @@
 
 - [ ] No unfilled template variables ({{variable}})
 - [ ] All variables properly populated with meaningful content
-- [ ] Product magic woven throughout (not just stated once)
+- [ ] Product differentiator reflected throughout (not just stated once)
 - [ ] Language is clear, specific, and measurable
 - [ ] Project type correctly identified and sections match
 - [ ] Domain complexity appropriately addressed
@@ -210,7 +210,7 @@
 ### Alignment Checks
 
 - [ ] Success metrics in PRD align with story outcomes
-- [ ] Product magic articulated in PRD reflected in epic goals
+- [ ] Product differentiator articulated in PRD reflected in epic goals
 - [ ] Technical preferences in PRD align with story implementation hints
 - [ ] Scope boundaries consistent across all documents
 
@@ -296,14 +296,10 @@ If ANY of these are true, validation FAILS:
 
 ## Validation Summary
 
-**Total Validation Points:** ~85
-
-### Scoring Guide
-
-- **Pass Rate ≥ 95% (81+/85):** ✅ EXCELLENT - Ready for architecture phase
-- **Pass Rate 85-94% (72-80/85):** ⚠️ GOOD - Minor fixes needed
-- **Pass Rate 70-84% (60-71/85):** ⚠️ FAIR - Important issues to address
-- **Pass Rate < 70% (<60/85):** ❌ POOR - Significant rework required
+- **Pass Rate ≥ 95%:** ✅ EXCELLENT - Ready for architecture phase
+- **Pass Rate 85-94%:** ⚠️ GOOD - Minor fixes needed
+- **Pass Rate 70-84%:** ⚠️ FAIR - Important issues to address
+- **Pass Rate < 70%:** ❌ POOR - Significant rework required
 
 ### Critical Issue Threshold
 
@@ -316,7 +312,7 @@ If ANY of these are true, validation FAILS:
 
 **When validating:**
 
-1. **Load ALL documents:**
+1. **Load ALL documents - whole or sharded (but not both of each) for example epics.md vs epics/\*.md:**
    - PRD.md (required)
    - epics.md (required)
    - product-brief.md (if exists)

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

@@ -11,10 +11,24 @@
 
 This document provides the complete epic and story breakdown for {{project_name}}, decomposing the requirements from the [PRD](./PRD.md) into implementable stories.
 
+**Living Document Notice:** This is the initial version. It will be updated after UX Design and Architecture workflows add interaction and technical details to stories.
+
 {{epics_summary}}
 
 ---
 
+## Functional Requirements Inventory
+
+{{fr_inventory}}
+
+---
+
+## FR Coverage Map
+
+{{fr_coverage_map}}
+
+---
+
 <!-- Repeat for each epic (N = 1, 2, 3...) -->
 
 ## Epic {{N}}: {{epic_title_N}}
@@ -49,4 +63,18 @@ So that {{value_benefit}}.
 
 ---
 
+## FR Coverage Matrix
+
+{{fr_coverage_matrix}}
+
+---
+
+## Summary
+
+{{epic_breakdown_summary}}
+
+---
+
 _For implementation: Use the `create-story` workflow to generate individual story implementation plans from this epic breakdown._
+
+_This document will be updated after UX Design and Architecture workflows to incorporate interaction details and technical decisions._

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

@@ -1,9 +1,14 @@
 # Epic and Story Decomposition - Intent-Based Implementation Planning
 
-<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>The workflow execution engine is governed by: {project-root}/{bmad_folder}/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
 <critical>This workflow transforms requirements into BITE-SIZED STORIES for development agents</critical>
 <critical>EVERY story must be completable by a single dev agent in one focused session</critical>
+<critical>BMAD METHOD WORKFLOW POSITION: This is the FIRST PASS at epic breakdown</critical>
+<critical>After this workflow: UX Design will add interaction details → UPDATE epics.md</critical>
+<critical>After UX: Architecture will add technical decisions → UPDATE epics.md AGAIN</critical>
+<critical>Phase 4 Implementation pulls context from: PRD + epics.md + UX + Architecture</critical>
+<critical>This is a LIVING DOCUMENT that evolves through the BMad Method workflow chain</critical>
 <critical>Communicate all responses in {communication_language} and adapt to {user_skill_level}</critical>
 <critical>Generate all documents in {document_output_language}</critical>
 <critical>LIVING DOCUMENT: Write to epics.md continuously as you work - never wait until the end</critical>
@@ -20,21 +25,49 @@ Load required documents (fuzzy match, handle both whole and sharded):
 - domain-brief.md (if exists)
 - product-brief.md (if exists)
 
+**CRITICAL - PRD FRs Are Now Flat and Strategic:**
+
+The PRD contains FLAT, capability-level functional requirements (FR1, FR2, FR3...).
+These are STRATEGIC (WHAT capabilities exist), NOT tactical (HOW they're implemented).
+
+Example PRD FRs:
+
+- FR1: Users can create accounts with email or social authentication
+- FR2: Users can log in securely and maintain sessions
+- FR6: Users can create, edit, and delete content items
+
+**Your job in THIS workflow:**
+
+1. Map each FR to one or more epics
+2. Break each FR into stories with DETAILED acceptance criteria
+3. Add ALL the implementation details that were intentionally left out of PRD
+
 Extract from PRD:
 
-- All functional requirements
+- ALL functional requirements (flat numbered list)
 - Non-functional requirements
 - Domain considerations and compliance needs
 - Project type and complexity
 - MVP vs growth vs vision scope boundaries
-
-Understand the context:
-
-- What makes this product special (the magic)
+- Product differentiator (what makes it special)
 - Technical constraints
 - User types and their goals
-- Success criteria</action>
-  </step>
+- Success criteria
+
+**Create FR Inventory:**
+
+List all FRs to ensure coverage:
+
+- FR1: [description]
+- FR2: [description]
+- ...
+- FRN: [description]
+
+This inventory will be used to validate complete coverage in Step 4.
+</action>
+
+<template-output>fr_inventory</template-output>
+</step>
 
 <step n="2" goal="Propose epic structure from natural groupings">
 <action>Analyze requirements and identify natural epic boundaries
@@ -76,18 +109,56 @@ Present proposed epic structure showing:
 
 - Epic titles with clear value statements
 - High-level scope of each epic
+- **FR COVERAGE MAP: Which FRs does each epic address?**
+  - Example: "Epic 1 (Foundation): Covers infrastructure needs for all FRs"
+  - Example: "Epic 2 (User Management): FR1, FR2, FR3, FR4, FR5"
+  - Example: "Epic 3 (Content System): FR6, FR7, FR8, FR9"
 - Suggested sequencing
-- Why this grouping makes sense</action>
+- Why this grouping makes sense
+
+**Validate FR Coverage:**
+
+Check that EVERY FR from Step 1 inventory is mapped to at least one epic.
+If any FRs are unmapped, add them now or explain why they're deferred.
+</action>
 
 <template-output>epics_summary</template-output>
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+<template-output>fr_coverage_map</template-output>
 </step>
 
-<step n="3" goal="Decompose each epic into bite-sized stories" repeat="for-each-epic">
+<step n="3" goal="Decompose each epic into bite-sized stories with DETAILED AC" repeat="for-each-epic">
 <action>Break down Epic {{N}} into small, implementable stories
 
 INTENT: Create stories sized for single dev agent completion
 
+**CRITICAL - ALTITUDE SHIFT FROM PRD:**
+
+PRD FRs are STRATEGIC (WHAT capabilities):
+
+- ✅ "Users can create accounts"
+
+Epic Stories are TACTICAL (HOW it's implemented):
+
+- Email field with RFC 5322 validation
+- Password requirements: 8+ chars, 1 uppercase, 1 number, 1 special
+- Password strength meter with visual feedback
+- Email verification within 15 minutes
+- reCAPTCHA v3 integration
+- Account creation completes in < 2 seconds
+- Mobile responsive with 44x44px touch targets
+- WCAG 2.1 AA compliant
+
+**THIS IS WHERE YOU ADD ALL THE DETAILS LEFT OUT OF PRD:**
+
+- UI specifics (exact field counts, validation rules, layout details)
+- Performance targets (< 2s, 60fps, etc.)
+- Technical implementation hints (libraries, patterns, APIs)
+- Edge cases (what happens when...)
+- Validation rules (regex patterns, constraints)
+- Error handling (specific error messages, retry logic)
+- Accessibility requirements (ARIA labels, keyboard nav, screen readers)
+- Platform specifics (mobile responsive, browser support)
+
 For each epic, generate:
 
 - Epic title as `epic_title_{{N}}`
@@ -129,41 +200,93 @@ Ensure stories are:
 
 For each story in epic {{N}}, output variables following this pattern:
 
-- story*title*{{N}}_1, story_title_{{N}}\_2, etc.
+- story*title*{{N}}_1, story_title_{{N}}\*2, etc.
 - Each containing: user story, BDD acceptance criteria, prerequisites, technical notes</action>
 
 <template-output>epic*title*{{N}}</template-output>
 <template-output>epic*goal*{{N}}</template-output>
 
 <action>For each story M in epic {{N}}, generate story content</action>
-<template-output>story*title*{{N}}\_{{M}}</template-output>
+<template-output>story-title-{{N}}-{{M}}</template-output>
 
-<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
-<step n="4" goal="Review and finalize epic breakdown">
+<step n="4" goal="Review initial epic breakdown and prepare for updates">
 <action>Review the complete epic breakdown for quality and completeness
 
-Validate:
+**Validate FR Coverage:**
+
+Create FR Coverage Matrix showing each FR mapped to epic(s) and story(ies):
+
+- FR1: [description] → Epic X, Story X.Y
+- FR2: [description] → Epic X, Story X.Z
+- FR3: [description] → Epic Y, Story Y.A
+- ...
+- FRN: [description] → Epic Z, Story Z.B
+
+Confirm: EVERY FR from Step 1 inventory is covered by at least one story.
+If any FRs are missing, add stories now.
+
+**Validate Story Quality:**
 
 - All functional requirements from PRD are covered by stories
-- Epic 1 establishes proper foundation
-- All stories are vertically sliced
-- No forward dependencies exist
+- Epic 1 establishes proper foundation (if greenfield)
+- All stories are vertically sliced (deliver complete functionality, not just one layer)
+- No forward dependencies exist (only backward references)
 - Story sizing is appropriate for single-session completion
 - BDD acceptance criteria are clear and testable
+- Details added (what was missing from PRD FRs: UI specifics, performance targets, etc.)
 - Domain/compliance requirements are properly distributed
 - Sequencing enables incremental value delivery
 
+**BMad Method Next Steps:**
+
+This epic breakdown is the INITIAL VERSION. It will be updated as you progress:
+
+1. **After UX Design Workflow:**
+   - UX Designer will design interactions for capabilities
+   - UPDATE story acceptance criteria with UX specs (mockup references, flow details)
+   - Add interaction patterns, visual design decisions, responsive breakpoints
+
+2. **After Architecture Workflow:**
+   - Architect will define technical implementation approach
+   - UPDATE story technical notes with architecture decisions
+   - Add references to data models, API contracts, tech stack choices, deployment patterns
+
+3. **During Phase 4 Implementation:**
+   - Each story pulls context from: PRD (why) + epics.md (what/how) + UX (interactions) + Architecture (technical)
+   - Stories may be further refined as implementation uncovers edge cases
+   - This document remains the single source of truth for story details
+
 Confirm with {user_name}:
 
 - Epic structure makes sense
-- Story breakdown is actionable
-- Dependencies are clear
-- BDD format provides clarity
-- Ready for architecture and implementation phases</action>
+- All FRs covered by stories (validated via coverage matrix)
+- Story breakdown is actionable with detailed acceptance criteria
+- Ready for UX Design workflow (next BMad Method step)
+  </action>
 
 <template-output>epic_breakdown_summary</template-output>
+<template-output>fr_coverage_matrix</template-output>
+
+<output>**✅ Epic Breakdown Complete (Initial Version)**
+
+**Created:** epics.md with epic and story breakdown
+
+**FR Coverage:** All functional requirements from PRD mapped to stories (see coverage matrix in document)
+
+**Next Steps in BMad Method:**
+
+1. **UX Design** (if UI exists) - Run: `workflow ux-design`
+   → Will add interaction details to stories in epics.md
+
+2. **Architecture** - Run: `workflow create-architecture`
+   → Will add technical details to stories in epics.md
+
+3. **Phase 4 Implementation** - Stories ready for context assembly
+
+**Important:** This is a living document that will be updated as you progress through the workflow chain. The epics.md file will evolve with UX and Architecture inputs before implementation begins.
+</output>
 </step>
 
 </workflow>

package/src/modules/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml

@@ -1,10 +1,10 @@
 # Epic and Story Decomposition Workflow
 name: create-epics-and-stories
-description: "Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents"
+description: "Transform PRD requirements into bite-sized stories organized into deliverable functional epics. This workflow takes a Product Requirements Document (PRD) and breaks it down into epics and user stories that can be easily assigned to development teams. It ensures that all functional requirements are captured in a structured format, making it easier for teams to understand and implement the necessary features."
 author: "BMad"
 
 # Critical variables from config
-config_source: "{project-root}/bmad/bmm/config.yaml"
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
 project_name: "{config_source}:project_name"
 output_folder: "{config_source}:output_folder"
 user_name: "{config_source}:user_name"
@@ -25,17 +25,15 @@ input_file_patterns:
   prd:
     whole: "{output_folder}/*prd*.md"
     sharded: "{output_folder}/*prd*/index.md"
-
   product_brief:
     whole: "{output_folder}/*product*brief*.md"
     sharded: "{output_folder}/*product*brief*/index.md"
-
   domain_brief:
     whole: "{output_folder}/*domain*brief*.md"
     sharded: "{output_folder}/*domain*brief*/index.md"
 
 # Module path and component files
-installed_path: "{project-root}/bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
 instructions: "{installed_path}/instructions.md"
 template: "{installed_path}/epics-template.md"
 
@@ -48,8 +46,8 @@ web_bundle:
   name: "create-epics-and-stories"
   description: "Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents"
   author: "BMad"
-  instructions: "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
-  template: "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
+  instructions: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
+  template: "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
   web_bundle_files:
-    - "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
-    - "bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"
+    - "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md"
+    - "{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md"