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

package/bmad/bmm/workflows/2-plan-workflows/prd/instructions.md

@@ -7,24 +7,7 @@
 <critical>Generate all documents in {document_output_language}</critical>
 <critical>LIVING DOCUMENT: Write to PRD.md continuously as you discover - never wait until the end</critical>
 <critical>GUIDING PRINCIPLE: Find and weave the product's magic throughout - what makes it special should inspire every section</critical>
-
-## 📚 Input Document Discovery
-
-This workflow requires: product brief, and may reference market research 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>
 
 <workflow>
 
@@ -37,14 +20,14 @@ This workflow requires: product brief, and may reference market research or brow
   <action>Load the FULL file: {status_file}</action>
   <action>Parse workflow_status section</action>
   <action>Check status of "prd" workflow</action>
-  <action>Get project_level from YAML metadata</action>
+  <action>Get project_track from YAML metadata</action>
   <action>Find first non-completed workflow (next expected workflow)</action>
 
-  <check if="project_level < 2">
-    <output>**Level {{project_level}} Project - Redirecting**
+  <check if="project_track is Quick Flow">
+    <output>**Quick Flow Track - Redirecting**
 
-Level 0-1 projects use tech-spec workflow for simpler planning.
-PRD is for Level 2-4 projects that need comprehensive requirements.</output>
+Quick Flow projects use tech-spec workflow for implementation-focused planning.
+PRD is for BMad Method and Enterprise Method tracks that need comprehensive requirements.</output>
 <action>Exit and suggest tech-spec workflow</action>
 </check>
 
@@ -132,6 +115,7 @@ Weave in the magic:
 <check if="business focus">
 <template-output>business_metrics</template-output>
 </check>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="3" goal="Scope Definition">
@@ -156,6 +140,7 @@ For complex domains:
 <template-output>mvp_scope</template-output>
 <template-output>growth_features</template-output>
 <template-output>vision_features</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="4" goal="Domain-Specific Exploration" optional="true">
@@ -256,8 +241,8 @@ Always relate back to the product magic:
 </check>
 </step>
 
-<step n="7" goal="UX Principles" optional="true">
-<action>Only if product has a UI
+<step n="7" goal="UX Principles" if="project has UI or UX">
+  <action>Only if product has a UI
 
 Light touch on UX - not full design:
 
@@ -271,10 +256,10 @@ Light touch on UX - not full design:
 Connect to the magic:
 "The UI should reinforce [the special moment] through [design approach]"</action>
 
-<check if="has UI">
-  <template-output>ux_principles</template-output>
-  <template-output>key_interactions</template-output>
-</check>
+  <check if="has UI">
+    <template-output>ux_principles</template-output>
+    <template-output>key_interactions</template-output>
+  </check>
 </step>
 
 <step n="8" goal="Functional Requirements Synthesis">
@@ -304,6 +289,7 @@ The magic thread:
 Highlight which requirements deliver the special experience</action>
 
 <template-output>functional_requirements_complete</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="9" goal="Non-Functional Requirements Discovery">
@@ -339,9 +325,6 @@ Skip categories that don't apply!</action>
 <check if="integration matters">
   <template-output>integration_requirements</template-output>
 </check>
-<check if="no NFRs discussed">
-  <template-output>no_nfrs</template-output>
-</check>
 </step>
 
 <step n="10" goal="Review PRD and transition to epics">
@@ -355,9 +338,13 @@ Skip categories that don't apply!</action>
 - Requirements: [count] functional, [count] non-functional
 - Special considerations: [domain/innovation]
 
-Does this capture your product vision?"
+Does this capture your product vision?"</action>
+
+<template-output>prd_summary</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
+
+<action>After PRD review and refinement complete:
 
-After confirmation:
 "Excellent! Now we need to break these requirements into implementable epics and stories.
 
 For the epic breakdown, you have two options:
@@ -379,12 +366,10 @@ This keeps each session focused and manageable."
 If continue:
 "Let's continue with epic breakdown here..."
 [Proceed with epics-stories subworkflow]
-Set project_level and target_scale based on project analysis
+Set project_track based on workflow status (BMad Method or Enterprise Method)
 Generate epic_details for the epics breakdown document</action>
 
-<template-output>prd_summary</template-output>
-<template-output>project_level</template-output>
-<template-output>target_scale</template-output>
+<template-output>project_track</template-output>
 <template-output>epic_details</template-output>
 </step>
 

package/bmad/bmm/workflows/2-plan-workflows/prd/workflow.yaml

@@ -1,6 +1,6 @@
 # Product Requirements Document (PRD) Workflow
 name: prd
-description: "Unified PRD workflow for project levels 2-4. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Level 0-1 use tech-spec workflow."
+description: "Unified PRD workflow for BMad Method and Enterprise Method tracks. Produces strategic PRD and tactical epic breakdown. Hands off to architecture workflow for technical design. Note: Quick Flow track uses tech-spec workflow."
 author: "BMad"
 
 # Critical variables from config

package/bmad/bmm/workflows/2-plan-workflows/tech-spec/epics-template.md

@@ -5,51 +5,73 @@
 
 ---
 
-## Epic: {{epic_title}}
+<!-- Repeat for each epic (N = 1, 2, 3...) -->
 
-**Slug:** {{epic_slug}}
+## Epic {{N}}: {{epic_title_N}}
+
+**Slug:** {{epic_slug_N}}
 
 ### Goal
 
-{{epic_goal}}
+{{epic_goal_N}}
 
 ### Scope
 
-{{epic_scope}}
+{{epic_scope_N}}
 
 ### Success Criteria
 
-{{epic_success_criteria}}
+{{epic_success_criteria_N}}
 
 ### Dependencies
 
-{{epic_dependencies}}
+{{epic_dependencies_N}}
 
 ---
 
-## Story Map
+## Story Map - Epic {{N}}
 
-{{story_map}}
+{{story_map_N}}
 
 ---
 
-## Story Summaries
+## Stories - Epic {{N}}
 
-{{story_summaries}}
+<!-- Repeat for each story (M = 1, 2, 3...) within epic N -->
 
----
+### Story {{N}}.{{M}}: {{story_title_N_M}}
+
+As a {{user_type}},
+I want {{capability}},
+So that {{value_benefit}}.
+
+**Acceptance Criteria:**
+
+**Given** {{precondition}}
+**When** {{action}}
+**Then** {{expected_outcome}}
+
+**And** {{additional_criteria}}
 
-## Implementation Timeline
+**Prerequisites:** {{dependencies_on_previous_stories}}
 
-**Total Story Points:** {{total_points}}
+**Technical Notes:** {{implementation_guidance}}
 
-**Estimated Timeline:** {{estimated_timeline}}
+**Estimated Effort:** {{story_points}} points ({{time_estimate}})
+
+<!-- End story repeat -->
 
 ---
 
-## Implementation Sequence
+## Implementation Timeline - Epic {{N}}
+
+**Total Story Points:** {{total_points_N}}
+
+**Estimated Timeline:** {{estimated_timeline_N}}
+
+---
 
-{{implementation_sequence}}
+<!-- End epic repeat -->
 
 ---
 

package/bmad/bmm/workflows/2-plan-workflows/tech-spec/instructions.md

@@ -10,26 +10,8 @@
 <critical>Level 0: tech-spec + single user story | Level 1: tech-spec + epic/stories</critical>
 <critical>LIVING DOCUMENT: Write to tech-spec.md continuously as you discover - never wait until the end</critical>
 <critical>CONTEXT IS KING: Gather ALL available context before generating specs</critical>
-
 <critical>DOCUMENT OUTPUT: Technical, precise, definitive. Specific versions only. User skill level ({user_skill_level}) affects conversation style ONLY, not document content.</critical>
-
-## 📚 Input Document Discovery
-
-This workflow intelligently discovers and loads all available context including: product brief, research documents, brownfield project documentation, and project setup files.
-
-**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 and detect project level" tag="workflow-status">
 <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>

package/bmad/bmm/workflows/2-plan-workflows/tech-spec/user-story-template.md

@@ -1,65 +1,68 @@
-# Story: {{story_title}}
+# Story {{N}}.{{M}}: {{story_title}}
 
-Status: Draft
+**Status:** Draft
 
-## Story
+---
 
-As a {{role}},
-I want {{capability}},
-so that {{benefit}}.
+## User Story
 
-## Acceptance Criteria
+As a {{user_type}},
+I want {{capability}},
+So that {{value_benefit}}.
 
-{{acceptance_criteria}}
+---
 
-## Tasks / Subtasks
+## Acceptance Criteria
 
-{{tasks_subtasks}}
+**Given** {{precondition}}
+**When** {{action}}
+**Then** {{expected_outcome}}
 
-## Dev Notes
+**And** {{additional_criteria}}
 
-### Technical Summary
+---
 
-{{technical_summary}}
+## Implementation Details
 
-### Tech-Spec Reference
+### Tasks / Subtasks
 
-**Full details:** See [tech-spec.md](../tech-spec.md)
+{{tasks_subtasks}}
 
-The tech-spec contains comprehensive context including:
+### Technical Summary
 
-- Brownfield codebase analysis (if applicable)
-- Framework and library details with versions
-- Existing patterns to follow
-- Integration points and dependencies
-- Complete implementation guidance
+{{technical_summary}}
 
 ### Project Structure Notes
 
 - **Files to modify:** {{files_to_modify}}
 - **Expected test locations:** {{test_locations}}
 - **Estimated effort:** {{story_points}} story points ({{time_estimate}})
-- **Dependencies:** {{dependencies}}
+- **Prerequisites:** {{dependencies}}
 
 ### Key Code References
 
 {{existing_code_references}}
 
-### References
-
-- **Tech Spec:** [tech-spec.md](../tech-spec.md) - Primary context document
-- **Architecture:** {{architecture_references}}
-
 ---
 
-## Dev Agent Record
+## Context References
 
-### Context Reference
+**Tech-Spec:** [tech-spec.md](../tech-spec.md) - Primary context document containing:
 
-**Primary Context:** [tech-spec.md](../tech-spec.md) - Contains all brownfield analysis, framework details, and implementation guidance
+- Brownfield codebase analysis (if applicable)
+- Framework and library details with versions
+- Existing patterns to follow
+- Integration points and dependencies
+- Complete implementation guidance
+
+**Architecture:** {{architecture_references}}
 
 <!-- Additional context XML paths will be added here if story-context workflow is run -->
 
+---
+
+## Dev Agent Record
+
 ### Agent Model Used
 
 <!-- Will be populated during dev-story execution -->
@@ -68,11 +71,11 @@ The tech-spec contains comprehensive context including:
 
 <!-- Will be populated during dev-story execution -->
 
-### Completion Notes List
+### Completion Notes
 
 <!-- Will be populated during dev-story execution -->
 
-### File List
+### Files Modified
 
 <!-- Will be populated during dev-story execution -->
 

package/bmad/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml

@@ -1,5 +1,5 @@
-# Technical Specification Workflow (Level 0)
-name: tech-spec-sm
+# Technical Specification
+name: tech-spec
 description: "Technical specification workflow for Level 0 projects (single atomic changes). Creates focused tech spec for bug fixes, single endpoint additions, or small isolated changes. Tech-spec only - no PRD needed."
 author: "BMad"
 

package/bmad/bmm/workflows/3-solutioning/architecture/instructions.md

@@ -9,24 +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>This workflow replaces architecture with a conversation-driven approach</critical>
-
-## 📚 Input Document Discovery
-
-This workflow requires: PRD and epics/stories, and may reference UX design specifications 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>
+<critical>ELICITATION POINTS: After completing each major architectural decision area (identified by template-output tags for decision_record, project_structure, novel_pattern_designs, implementation_patterns, and architecture_document), invoke advanced elicitation to refine decisions before proceeding</critical>
 
 <step n="0" goal="Validate workflow readiness" tag="workflow-status">
 <action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
@@ -379,6 +363,7 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
 <template-output>decision_record</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="5" goal="Address cross-cutting concerns">
@@ -408,6 +393,7 @@ Provided by Starter: {{yes_if_from_starter}}
 </action>
 
 <template-output>project_structure</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="7" goal="Design novel architectural patterns" optional="true">
@@ -481,6 +467,7 @@ Provided by Starter: {{yes_if_from_starter}}
   </check>
 
 <template-output>novel_pattern_designs</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="8" goal="Define implementation patterns to prevent agent conflicts">
@@ -573,6 +560,7 @@ Enforcement: "All agents MUST follow this pattern"
 </action>
 
 <template-output>implementation_patterns</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="9" goal="Validate architectural coherence">
@@ -626,6 +614,7 @@ Enforcement: "All agents MUST follow this pattern"
   </action>
 
 <template-output>architecture_document</template-output>
+<invoke-task halt="true">{project-root}/bmad/core/tasks/adv-elicit.xml</invoke-task>
 </step>
 
 <step n="11" goal="Validate document completeness">

package/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/instructions.md

@@ -3,24 +3,7 @@
 <critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
 <critical>You MUST have already loaded and processed: {project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml</critical>
 <critical>Communicate all findings and analysis in {communication_language} throughout the assessment</critical>
-
-## 📚 Input Document Discovery
-
-This workflow validates: PRD, epics/stories, architecture, and may reference UX design, tech specs, 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>
 
 <workflow>
 

package/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml

@@ -24,13 +24,13 @@ validation: "{installed_path}/checklist.md"
 # Output configuration
 default_output_file: "{output_folder}/implementation-readiness-report-{{date}}.md"
 
-# Expected input documents (varies by project level)
+# Input requirements
 recommended_inputs:
-  - prd: "{output_folder}/prd*.md"
-  - architecture: "{output_folder}/architecture*.md or {output_folder}/architecture*.md"
-  - tech_spec: "{output_folder}/tech-spec*.md"
-  - epics_stories: "{output_folder}/epic*.md"
-  - ux_artifacts: "{output_folder}/ux*.md"
+  - prd: "Product Requirements Document with FRs and NFRs"
+  - architecture: "System Architecture with decisions and patterns"
+  - tech_spec: "Technical Specification (for Quick Flow track)"
+  - epics: "Epic breakdown with user stories"
+  - ux_design: "UX design specification (if UI components)"
 
 # Smart input file references - handles both whole docs and sharded docs
 # Priority: Whole document first, then sharded version

package/bmad/bmm/workflows/4-implementation/epic-tech-context/workflow.yaml

@@ -1,4 +1,4 @@
-name: tech-spec
+name: epic-tech-context
 description: "Generate a comprehensive Technical Specification from PRD and Architecture with acceptance criteria and traceability mapping"
 author: "BMAD BMM"
 

package/bmad/bmm/workflows/techdoc/documentation-standards.md

@@ -1,14 +1,36 @@
 # Technical Documentation Standards for BMAD
 
-**For Agent: Paige (Documentation Guide)**
+**For Agent: Technical Writer**
 **Purpose: Concise reference for documentation creation and review**
 
 ---
 
-## CRITICAL RULE: CommonMark Strict Compliance
+## CRITICAL RULES
+
+### Rule 1: CommonMark Strict Compliance
 
 ALL documentation MUST follow CommonMark specification exactly. No exceptions.
 
+### Rule 2: NO TIME ESTIMATES
+
+NEVER document time estimates, durations, or completion times for any workflow, task, or activity. This includes:
+
+- Workflow execution time (e.g., "30-60 min", "2-8 hours")
+- Task duration estimates
+- Reading time estimates
+- Implementation time ranges
+- Any temporal measurements
+
+Time varies dramatically based on:
+
+- Project complexity
+- Team experience
+- Tooling and environment
+- Context switching
+- Unforeseen blockers
+
+**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines.
+
 ### CommonMark Essentials
 
 **Headers:**
@@ -122,6 +144,7 @@ Apply in this hierarchy:
 - Alt text for diagrams: Describe what it shows
 - Semantic heading hierarchy (don't skip levels)
 - Tables have headers
+- Emojis are acceptable if user preferences allow (modern accessibility tools support emojis well)
 
 ---
 
@@ -193,6 +216,7 @@ Apply in this hierarchy:
 Before finalizing ANY documentation:
 
 - [ ] CommonMark compliant (no violations)
+- [ ] NO time estimates anywhere (Critical Rule 2)
 - [ ] Headers in proper hierarchy
 - [ ] All code blocks have language tags
 - [ ] Links work and have descriptive text

package/bmad/bmm/workflows/testarch/atdd/atdd-checklist-template.md

@@ -355,8 +355,8 @@ See `tea-index.csv` for complete knowledge fragment mapping.
 
 - Ask in team standup
 - Tag @{tea_agent_username} in Slack/Discord
-- Refer to `testarch/README.md` for workflow documentation
-- Consult `testarch/knowledge/` for testing best practices
+- Refer to `./bmm/docs/tea-README.md` for workflow documentation
+- Consult `./bmm/testarch/knowledge` for testing best practices
 
 ---