bmad-method 6.0.0-alpha.20 → 6.0.0-alpha.22

package/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/tech-spec-template.md

@@ -0,0 +1,74 @@
+---
+title: '{title}'
+slug: '{slug}'
+created: '{date}'
+status: 'in-progress'
+stepsCompleted: []
+tech_stack: []
+files_to_modify: []
+code_patterns: []
+test_patterns: []
+---
+
+# Tech-Spec: {title}
+
+**Created:** {date}
+
+## Overview
+
+### Problem Statement
+
+{problem_statement}
+
+### Solution
+
+{solution}
+
+### Scope
+
+**In Scope:**
+{in_scope}
+
+**Out of Scope:**
+{out_of_scope}
+
+## Context for Development
+
+### Codebase Patterns
+
+{codebase_patterns}
+
+### Files to Reference
+
+| File | Purpose |
+| ---- | ------- |
+
+{files_table}
+
+### Technical Decisions
+
+{technical_decisions}
+
+## Implementation Plan
+
+### Tasks
+
+{tasks}
+
+### Acceptance Criteria
+
+{acceptance_criteria}
+
+## Additional Context
+
+### Dependencies
+
+{dependencies}
+
+### Testing Strategy
+
+{testing_strategy}
+
+### Notes
+
+{notes}

package/src/modules/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.md

@@ -0,0 +1,79 @@
+---
+name: create-tech-spec
+description: Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec.
+main_config: '{project-root}/_bmad/bmm/config.yaml'
+web_bundle: true
+
+# Checkpoint handler paths
+advanced_elicitation: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
+party_mode_exec: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
+quick_dev_workflow: '{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md'
+---
+
+# Create Tech-Spec Workflow
+
+**Goal:** Create implementation-ready technical specifications through conversational discovery, code investigation, and structured documentation.
+
+**READY FOR DEVELOPMENT STANDARD:**
+
+A specification is considered "Ready for Development" ONLY if it meets the following:
+
+- **Actionable**: Every task has a clear file path and specific action.
+- **Logical**: Tasks are ordered by dependency (lowest level first).
+- **Testable**: All ACs follow Given/When/Then and cover happy path and edge cases.
+- **Complete**: All investigation results from Step 2 are inlined; no placeholders or "TBD".
+- **Self-Contained**: A fresh agent can implement the feature without reading the workflow history.
+
+---
+
+**Your Role:** You are an elite developer and spec engineer. You ask sharp questions, investigate existing code thoroughly, and produce specs that contain ALL context a fresh dev agent needs to implement the feature. No handoffs, no missing context - just complete, actionable specs.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution:
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self-contained instruction file that must be followed exactly
+- **Just-In-Time Loading**: Only the current step file is in memory - never load future step files until directed
+- **Sequential Enforcement**: Sequence within step files must be completed in order, no skipping or optimization
+- **State Tracking**: Document progress in output file frontmatter using `stepsCompleted` array
+- **Append-Only Building**: Build the tech-spec by updating content as directed
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order, never deviate
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: Only proceed to next step when user selects [c] (Continue)
+5. **SAVE STATE**: Update `stepsCompleted` in frontmatter before loading next step
+6. **LOAD NEXT**: When directed, load and read entire next step file, then execute
+
+### Critical Rules (NO EXCEPTIONS)
+
+- **NEVER** load multiple step files simultaneously
+- **ALWAYS** read entire step file before execution
+- **NEVER** skip steps or optimize the sequence
+- **ALWAYS** update frontmatter of output file when completing a step
+- **ALWAYS** follow the exact instructions in the step file
+- **ALWAYS** halt at menus and wait for user input
+- **NEVER** create mental todo lists from future steps
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from `{main_config}` and resolve:
+
+- `project_name`, `output_folder`, `planning_artifacts`, `implementation_artifacts`, `user_name`
+- `communication_language`, `document_output_language`, `user_skill_level`
+- `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. First Step Execution
+
+Load, read the full file, and then execute `steps/step-01-understand.md` to begin the workflow.

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-01-mode-detection.md

@@ -40,7 +40,7 @@ First, check if the project uses Git version control:
 
 ### 2. Load Project Context
 
-Check if `{project_context}` exists (`**/project-context.md`). If found, load it - this is foundational reference for ALL implementation decisions.
+Check if `{project_context}` exists (`**/project-context.md`). If found, load it as a foundational reference for ALL implementation decisions.
 
 ### 3. Parse User Input
 

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/steps/step-05-adversarial-review.md

@@ -79,7 +79,7 @@ Evaluate severity (Critical, High, Medium, Low) and validity (real, noise, undec
 DO NOT exclude findings based on severity or validity unless explicitly asked to do so.
 Order findings by severity.
 Number the ordered findings (F1, F2, F3, etc.).
-If WriteTodos or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the todo; otherwise present findings as a table with columns: ID, Severity, Validity, Description
+If TodoWrite or similar tool is available, turn each finding into a TODO, include ID, severity, validity, and description in the TODO; otherwise present findings as a table with columns: ID, Severity, Validity, Description
 
 ---
 

package/src/modules/bmm/workflows/bmad-quick-flow/quick-dev/workflow.md

@@ -28,8 +28,9 @@ This uses **step-file architecture** for focused execution:
 Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 
 - `user_name`, `communication_language`, `user_skill_level`
-- `output_folder`, `sprint_artifacts`
+- `output_folder`, `planning_artifacts`,  `implementation_artifacts`
 - `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Paths
 
@@ -42,7 +43,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `create_tech_spec_workflow` = `{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml`
 - `workflow_init` = `{project-root}/_bmad/bmm/workflows/workflow-status/init/workflow.yaml`
 - `party_mode_exec` = `{project-root}/_bmad/core/workflows/party-mode/workflow.md`
-- `advanced_elicitation` = `{project-root}/_bmad/core/tasks/advanced-elicitation.xml`
+- `advanced_elicitation` = `{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml`
 
 ---
 

package/src/modules/bmm/workflows/document-project/checklist.md

@@ -1,6 +1,6 @@
 # Document Project Workflow - Validation Checklist
 
-## Scan Level and Resumability (v1.2.0)
+## Scan Level and Resumability
 
 - [ ] Scan level selection offered (quick/deep/exhaustive) for initial_scan and full_rescan modes
 - [ ] Deep-dive mode automatically uses exhaustive scan (no choice given)
@@ -223,7 +223,7 @@
 
 All items in the following sections must be checked:
 
-- ✓ Scan Level and Resumability (v1.2.0)
+- ✓ Scan Level and Resumability
 - ✓ Write-as-you-go Architecture
 - ✓ Batching Strategy (if deep/exhaustive scan)
 - ✓ Project Detection and Classification

package/src/modules/bmm/workflows/generate-project-context/steps/step-01-discover.md

@@ -8,6 +8,7 @@
 - 💬 FOCUS on discovering existing project context and technology stack
 - 🎯 IDENTIFY critical implementation rules that AI agents need
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/generate-project-context/steps/step-02-generate.md

@@ -8,6 +8,7 @@
 - 💬 FOCUS on unobvious rules that AI agents need to be reminded of
 - 🎯 KEEP CONTENT LEAN - optimize for LLM context efficiency
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 
@@ -28,7 +29,7 @@ This step will generate content and present choices for each rule category:
 
 ## PROTOCOL INTEGRATION:
 
-- When 'A' selected: Execute {project-root}/_bmad/core/tasks/advanced-elicitation.xml
+- When 'A' selected: Execute {project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml
 - When 'P' selected: Execute {project-root}/_bmad/core/workflows/party-mode
 - PROTOCOLS always return to display this step's A/P/C menu after the A or P have completed
 - User accepts/rejects protocol changes before proceeding

package/src/modules/bmm/workflows/generate-project-context/steps/step-03-complete.md

@@ -8,6 +8,7 @@
 - 💬 FOCUS on finalizing a lean, LLM-optimized project context
 - 🎯 ENSURE all critical rules are captured and actionable
 - ⚠️ ABSOLUTELY NO TIME ESTIMATES - AI development speed has fundamentally changed
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ## EXECUTION PROTOCOLS:
 

package/src/modules/bmm/workflows/generate-project-context/workflow.md

@@ -32,6 +32,7 @@ Load config from `{project-root}/_bmad/bmm/config.yaml` and resolve:
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`, `user_skill_level`
 - `date` as system-generated current datetime
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
 
 ### Paths
 

package/src/modules/bmm/workflows/workflow-status/init/instructions.md

@@ -15,8 +15,8 @@
 - BMM artifacts: PRD, epics, architecture, UX, brief, research, brainstorm
 - Implementation: stories, sprint-status, workflow-status
 - Codebase: source directories, package files, git repo
-- Check both {output_folder} and {implementation_artifacts} locations
-  </action>
+- Check both {planning_artifacts} and {implementation_artifacts} locations
+</action>
 
 <action>Categorize into one of these states:
 
@@ -25,7 +25,7 @@
 - ACTIVE: Has stories or sprint status
 - LEGACY: Has code but no BMM artifacts
 - UNCLEAR: Mixed state needs clarification
-  </action>
+</action>
 
 <ask>What's your project called? {{#if project_name}}(Config shows: {{project_name}}){{/if}}</ask>
 <action>Store project_name</action>
@@ -68,7 +68,7 @@ Choice [1-4]</ask>
 
   <check if="choice == 2">
     <ask>Archive existing work? (y/n)</ask>
-    <action if="y">Move artifacts to {output_folder}/archive/</action>
+    <action if="y">Move artifacts to {planning_artifacts}/archive/</action>
     <output>Ready for fresh start!</output>
     <action>Continue to step 3</action>
   </check>
@@ -323,10 +323,10 @@ Choice:</ask>
 
 <check if="y">
   <action>Generate YAML from template with all variables</action>
-  <action>Save to {output_folder}/bmm-workflow-status.yaml</action>
+  <action>Save to {planning_artifacts}/bmm-workflow-status.yaml</action>
   <action>Identify next workflow and agent</action>
 
-<output>✅ **Created:** {output_folder}/bmm-workflow-status.yaml
+<output>✅ **Created:** {planning_artifacts}/bmm-workflow-status.yaml
 
 **Next:** {{next_workflow_name}}
 **Agent:** {{next_agent}}

package/src/modules/bmm/workflows/workflow-status/init/workflow.yaml

@@ -7,6 +7,7 @@ author: "BMad"
 config_source: "{project-root}/_bmad/bmm/config.yaml"
 output_folder: "{config_source}:output_folder"
 implementation_artifacts: "{config_source}:implementation_artifacts"
+planning_artifacts: "{config_source}:planning_artifacts"
 user_name: "{config_source}:user_name"
 project_name: "{config_source}:project_name"
 communication_language: "{config_source}:communication_language"
@@ -23,7 +24,7 @@ template: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow-status-te
 path_files: "{project-root}/_bmad/bmm/workflows/workflow-status/paths/"
 
 # Output configuration
-default_output_file: "{output_folder}/bmm-workflow-status.yaml"
+default_output_file: "{planning_artifacts}/bmm-workflow-status.yaml"
 
 standalone: true
 web_bundle: false

package/src/modules/bmm/workflows/workflow-status/instructions.md

@@ -34,7 +34,7 @@
 </step>
 
 <step n="1" goal="Check for status file">
-<action>Search {output_folder}/ for file: bmm-workflow-status.yaml</action>
+<action>Search {planning_artifacts}/ for file: bmm-workflow-status.yaml</action>
 
 <check if="no status file found">
   <output>No workflow status found.</output>
@@ -343,11 +343,11 @@ Your choice:</ask>
   <!-- ============================================= -->
   <check if="action == complete_workflow">
     <action>Get {{workflow_id}} parameter (required)</action>
-    <action>Get {{output_file}} parameter (required - path to created file)</action>
+    <action>Get {{default_output_file}} parameter (required - path to created file)</action>
 
     <critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
     <action>Update workflow status in YAML:</action>
-    - In workflow_status section, update: {{workflow_id}}: {{output_file}}
+    - In workflow_status section, update: {{workflow_id}}: {{default_output_file}}
 
     <action>Find {{workflow_id}} in loaded path YAML</action>
     <action>Determine next workflow from path sequence</action>
@@ -359,7 +359,7 @@ Your choice:</ask>
     <template-output>next_workflow = {{determined next workflow}}</template-output>
     <template-output>next_agent = {{determined next agent from path file}}</template-output>
     <template-output>completed_workflow = {{workflow_id}}</template-output>
-    <template-output>output_file = {{output_file}}</template-output>
+    <template-output>default_output_file = {{default_output_file}}</template-output>
 
   </check>
 

package/src/modules/bmm/workflows/workflow-status/paths/enterprise-brownfield.yaml

@@ -7,116 +7,97 @@ field_type: "brownfield"
 description: "Enterprise-grade planning for complex brownfield additions with extended requirements"
 
 phases:
-  - prerequisite: true
+  - phase: 0
     name: "Documentation"
     conditional: "if_undocumented"
-    note: "NOT a phase - prerequisite for brownfield without docs (nearly mandatory for enterprise)"
+    note: "Prerequisite for brownfield without docs"
     workflows:
       - id: "document-project"
         required: true
+        workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
         agent: "analyst"
-        command: "document-project"
+        command: "/bmad:bmm:workflows:document-project"
         output: "Comprehensive project documentation"
-        purpose: "Understand existing codebase - critical for enterprise brownfield"
-
-  - phase: 0
-    name: "Discovery (Required)"
-    required: true
-    note: "Analysis phase required for enterprise projects"
+        purpose: "Understand existing codebase before planning"
+  - phase: 1
+    name: "Analysis (Optional)"
+    optional: true
+    note: "User-selected during workflow-init"
     workflows:
       - id: "brainstorm-project"
+        exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
         optional: true
         agent: "analyst"
-        command: "brainstorm-project"
-        note: "Uses core brainstorming workflow with project context template"
+        command: "/bmad:bmm:workflows:brainstorming"
         included_by: "user_choice"
-
+        note: "Uses core brainstorming workflow with project context template"
       - id: "research"
-        recommended: true
+        exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.md"
+        optional: true
         agent: "analyst"
-        command: "research"
+        command: "/bmad:bmm:workflows:research"
         included_by: "user_choice"
-        note: "Highly recommended - compliance, integration, risk research"
-
+        note: "Can have multiple research workflows"
       - id: "product-brief"
+        exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
         optional: true
         agent: "analyst"
-        command: "product-brief"
+        command: "/bmad:bmm:workflows:create-product-brief"
         included_by: "user_choice"
-        note: "Optional for brownfield enterprise"
-
-  - phase: 1
+        note: "Recommended for greenfield Method projects"
+  - phase: 2
     name: "Planning"
     required: true
     workflows:
       - id: "prd"
+        exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
         required: true
         agent: "pm"
-        command: "prd"
-        output: "Enterprise PRD with compliance requirements"
-        note: "Must address existing system constraints and migration strategy"
-
+        command: "/bmad:bmm:workflows:create-prd"
+        output: "Product Requirements Document with FRs and NFRs"
       - id: "create-ux-design"
-        recommended: true
+        conditional: "if_has_ui"
+        exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
         agent: "ux-designer"
-        command: "create-ux-design"
-        note: "Recommended - must integrate with existing UX patterns"
-
-  - phase: 2
+        command: "/bmad:bmm:workflows:create-ux-design"
+        note: "Determined after PRD - user/agent decides if needed"
+  - phase: 3
     name: "Solutioning"
     required: true
     workflows:
       - id: "create-architecture"
         required: true
+        exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
         agent: "architect"
-        command: "create-architecture"
-        output: "Integration architecture with enterprise considerations"
-        note: "Distills brownfield context + adds security/scalability/compliance design"
-
+        command: "/bmad:bmm:workflows:create-architecture"
+        output: "System architecture document"
+        note: "Complete system design for greenfield projects"
       - id: "create-epics-and-stories"
         required: true
+        exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
         agent: "pm"
-        command: "create-epics-and-stories"
+        command: "/bmad:bmm:workflows:create-epics-and-stories"
         note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
-
       - id: "test-design"
-        required: true
+        optional: true
+        workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-design/workflow.yaml"
         agent: "tea"
-        command: "test-design"
+        command: "/bmad:bmm:workflows:test-design"
         output: "System-level testability review"
-        note: "Enterprise requires testability validation - auto-detects system-level mode"
-
-      # - id: "create-security-architecture"
-      #   optional: true
-      #   agent: "architect"
-      #   command: "create-security-architecture"
-      #   output: "Security architecture for brownfield integration"
-      #   note: "Future workflow - optional extended enterprise workflow for threat model, auth integration, audit requirements"
-
-      # - id: "create-devops-strategy"
-      #   optional: true
-      #   agent: "architect"
-      #   command: "create-devops-strategy"
-      #   output: "DevOps strategy for brownfield deployment"
-      #   note: "Future workflow - optional extended enterprise workflow for CI/CD integration, deployment strategy, monitoring"
-
-      - id: "validate-architecture"
-        recommended: true
-        agent: "architect"
-        command: "validate-architecture"
-
+        note: "Testability assessment before gate check - auto-detects system-level mode"
       - id: "implementation-readiness"
         required: true
+        exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
         agent: "architect"
-        command: "implementation-readiness"
+        command: "/bmad:bmm:workflows:implementation-readiness"
         note: "Validates PRD + Architecture + Epics + UX (optional)"
-
-  - phase: 3
+  - phase: 4
     name: "Implementation"
     required: true
     workflows:
       - id: "sprint-planning"
         required: true
+        workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
         agent: "sm"
-        command: "sprint-planning"
-        note: "Enterprise brownfield requires careful phasing and feature flags"
+        command: "/bmad:bmm:workflows:sprint-planning"
+        note: "Creates sprint plan - subsequent work tracked there"