bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.14

package/src/modules/bmm/workflows/4-implementation/sprint-status/instructions.md

@@ -0,0 +1,174 @@
+# Sprint Status - Multi-Mode Service
+
+<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: {project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-status/workflow.yaml</critical>
+<critical>Modes: interactive (default), validate, data</critical>
+<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES. Do NOT mention hours, days, weeks, or timelines.</critical>
+
+<workflow>
+
+<step n="0" goal="Determine execution mode">
+  <action>Set mode = {{mode}} if provided by caller; otherwise mode = "interactive"</action>
+
+  <check if="mode == data">
+    <action>Jump to Step 20</action>
+  </check>
+
+  <check if="mode == validate">
+    <action>Jump to Step 30</action>
+  </check>
+
+  <check if="mode == interactive">
+    <action>Continue to Step 1</action>
+  </check>
+</step>
+
+<step n="1" goal="Locate sprint status file">
+  <action>Try {sprint_status_file}</action>
+  <check if="file not found">
+    <output>❌ sprint-status.yaml not found.
+Run `/bmad:bmm:workflows:sprint-planning` to generate it, then rerun sprint-status.</output>
+    <action>Exit workflow</action>
+  </check>
+  <action>Continue to Step 2</action>
+</step>
+
+<step n="2" goal="Read and parse sprint-status.yaml">
+  <action>Read the FULL file: {sprint_status_file}</action>
+  <action>Parse fields: generated, project, project_key, tracking_system, story_location</action>
+  <action>Parse development_status map. Classify keys:</action>
+  - Epics: keys starting with "epic-" (and not ending with "-retrospective")
+  - Retrospectives: keys ending with "-retrospective"
+  - Stories: everything else (e.g., 1-2-login-form)
+  <action>Count story statuses: backlog, drafted, ready-for-dev, in-progress, review, done</action>
+  <action>Count epic statuses: backlog, contexted</action>
+  <action>Detect risks:</action>
+  - Stories in review but no reviewer assigned context → suggest `/bmad:bmm:workflows:code-review`
+  - Stories in in-progress with no ready-for-dev items behind them → keep focus on the active story
+  - All epics backlog/contexted but no stories drafted → prompt to run `/bmad:bmm:workflows:create-story`
+</step>
+
+<step n="3" goal="Select next action recommendation">
+  <action>Pick the next recommended workflow using priority:</action>
+  1. If any story status == in-progress → recommend `dev-story` for the first in-progress story
+  2. Else if any story status == review → recommend `code-review` for the first review story
+  3. Else if any story status == ready-for-dev → recommend `dev-story`
+  4. Else if any story status == drafted → recommend `story-ready`
+  5. Else if any story status == backlog → recommend `create-story`
+  6. Else if any epic status == backlog → recommend `epic-tech-context`
+  7. Else if retrospectives are optional → recommend `retrospective`
+  8. Else → All implementation items done; suggest `workflow-status` to plan next phase
+  <action>Store selected recommendation as: next_story_id, next_workflow_id, next_agent (SM/DEV as appropriate)</action>
+</step>
+
+<step n="4" goal="Display summary">
+  <output>
+## 📊 Sprint Status
+
+- Project: {{project}} ({{project_key}})
+- Tracking: {{tracking_system}}
+- Status file: {sprint_status_file}
+
+**Stories:** backlog {{count_backlog}}, drafted {{count_drafted}}, ready-for-dev {{count_ready}}, in-progress {{count_in_progress}}, review {{count_review}}, done {{count_done}}
+
+**Epics:** backlog {{epic_backlog}}, contexted {{epic_contexted}}
+
+**Next Recommendation:** /bmad:bmm:workflows:{{next_workflow_id}} ({{next_story_id}})
+
+{{#if risks}}
+**Risks:**
+{{#each risks}}
+
+- {{this}}
+  {{/each}}
+  {{/if}}
+
+{{#if by_epic}}
+**Per Epic:**
+{{#each by_epic}}
+
+- {{epic_id}}: context={{context_status}}, stories → backlog {{backlog}}, drafted {{drafted}}, ready {{ready_for_dev}}, in-progress {{in_progress}}, review {{review}}, done {{done}}
+  {{/each}}
+  {{/if}}
+  </output>
+  </step>
+
+<step n="5" goal="Offer actions">
+  <ask>Pick an option:
+1) Run recommended workflow now
+2) Show all stories grouped by status
+3) Show raw sprint-status.yaml
+4) Exit
+Choice:</ask>
+
+  <check if="choice == 1">
+    <output>Run `/bmad:bmm:workflows:{{next_workflow_id}}`.
+If the command targets a story, set `story_key={{next_story_id}}` when prompted.</output>
+  </check>
+
+  <check if="choice == 2">
+    <output>
+### Stories by Status
+- In Progress: {{stories_in_progress}}
+- Review: {{stories_in_review}}
+- Ready for Dev: {{stories_ready_for_dev}}
+- Drafted: {{stories_drafted}}
+- Backlog: {{stories_backlog}}
+- Done: {{stories_done}}
+    </output>
+  </check>
+
+  <check if="choice == 3">
+    <action>Display the full contents of {sprint_status_file}</action>
+  </check>
+
+  <check if="choice == 4">
+    <action>Exit workflow</action>
+  </check>
+</step>
+
+<!-- ========================= -->
+<!-- Data mode for other flows -->
+<!-- ========================= -->
+
+<step n="20" goal="Data mode output">
+  <action>Load and parse {sprint_status_file} same as Step 2</action>
+  <action>Compute recommendation same as Step 3</action>
+  <template-output>next_workflow_id = {{next_workflow_id}}</template-output>
+  <template-output>next_story_id = {{next_story_id}}</template-output>
+  <template-output>count_backlog = {{count_backlog}}</template-output>
+  <template-output>count_drafted = {{count_drafted}}</template-output>
+  <template-output>count_ready = {{count_ready}}</template-output>
+  <template-output>count_in_progress = {{count_in_progress}}</template-output>
+  <template-output>count_review = {{count_review}}</template-output>
+  <template-output>count_done = {{count_done}}</template-output>
+  <template-output>epic_backlog = {{epic_backlog}}</template-output>
+  <template-output>epic_contexted = {{epic_contexted}}</template-output>
+  <template-output>warnings = {{risks}}</template-output>
+  <action>Return to caller</action>
+</step>
+
+<!-- ========================= -->
+<!-- Validate mode -->
+<!-- ========================= -->
+
+<step n="30" goal="Validate sprint-status file">
+  <action>Check that {sprint_status_file} exists</action>
+  <check if="missing">
+    <template-output>is_valid = false</template-output>
+    <template-output>error = "sprint-status.yaml missing"</template-output>
+    <template-output>suggestion = "Run sprint-planning to create it"</template-output>
+    <action>Return</action>
+  </check>
+  <action>Read file and verify it has a development_status section with at least one entry</action>
+  <check if="validation fails">
+    <template-output>is_valid = false</template-output>
+    <template-output>error = "development_status missing or empty"</template-output>
+    <template-output>suggestion = "Re-run sprint-planning or repair the file manually"</template-output>
+    <action>Return</action>
+  </check>
+  <template-output>is_valid = true</template-output>
+  <template-output>message = "sprint-status.yaml present and parsable"</template-output>
+</step>
+
+</workflow>

package/src/modules/bmm/workflows/4-implementation/sprint-status/workflow.yaml

@@ -0,0 +1,35 @@
+# Sprint Status - Implementation Tracker
+name: sprint-status
+description: "Summarize sprint-status.yaml, surface risks, and route to the right implementation workflow."
+author: "BMad"
+
+# Critical variables from config
+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"
+document_output_language: "{config_source}:document_output_language"
+date: system-generated
+sprint_artifacts: "{config_source}:sprint_artifacts"
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/sprint-status"
+instructions: "{installed_path}/instructions.md"
+
+# Inputs
+variables:
+  sprint_status_file: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+  tracking_system: "file-system"
+
+# Smart input file references
+input_file_patterns:
+  sprint_status:
+    description: "Sprint status file generated by sprint-planning"
+    whole: "{sprint_artifacts}/sprint-status.yaml || {output_folder}/sprint-status.yaml"
+    load_strategy: "FULL_LOAD"
+
+# Standalone so IDE commands get generated
+standalone: true
+
+# No web bundle needed
+web_bundle: false

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

@@ -0,0 +1,115 @@
+# Create Tech-Spec - Spec Engineering for AI Development
+
+<workflow>
+
+<critical>Communicate in {communication_language}, tailored to {user_skill_level}</critical>
+<critical>Generate documents in {document_output_language}</critical>
+<critical>Conversational spec engineering - ask questions, investigate code, produce complete spec</critical>
+<critical>Spec must contain ALL context a fresh dev agent needs to implement it</critical>
+
+<checkpoint-handlers>
+  <on-select key="a">Load and execute {advanced_elicitation}, then return to current step</on-select>
+  <on-select key="p">Load and execute {party_mode_workflow}, then return to current step</on-select>
+  <on-select key="b">Load and execute {quick_dev_workflow} with the tech-spec file</on-select>
+</checkpoint-handlers>
+
+<step n="1" goal="Understand what the user wants to build">
+
+<action>Greet {user_name} and ask them to describe what they want to build or change.</action>
+
+<action>Ask clarifying questions: problem, who's affected, scope, constraints, existing code?</action>
+
+<action>Check for existing context in {output_folder} and {sprint_artifacts}</action>
+
+<checkpoint title="Problem Understanding">
+[a] Advanced Elicitation  [c] Continue  [p] Party Mode
+</checkpoint>
+
+</step>
+
+<step n="2" goal="Investigate existing code (if applicable)">
+
+<action>If brownfield: get file paths, read code, identify patterns/conventions/dependencies</action>
+
+<action>Document: tech stack, code patterns, files to modify, test patterns</action>
+
+<checkpoint title="Context Gathered">
+[a] Advanced Elicitation  [c] Continue  [p] Party Mode
+</checkpoint>
+
+</step>
+
+<step n="3" goal="Generate the technical specification">
+
+<action>Create tech-spec using this structure:
+
+```markdown
+# Tech-Spec: {title}
+
+**Created:** {date}
+**Status:** Ready for Development
+
+## Overview
+
+### Problem Statement
+
+### Solution
+
+### Scope (In/Out)
+
+## Context for Development
+
+### Codebase Patterns
+
+### Files to Reference
+
+### Technical Decisions
+
+## Implementation Plan
+
+### Tasks
+
+- [ ] Task 1: Description
+- [ ] Task 2: Description
+
+### Acceptance Criteria
+
+- [ ] AC 1: Given/When/Then
+- [ ] AC 2: ...
+
+## Additional Context
+
+### Dependencies
+
+### Testing Strategy
+
+### Notes
+```
+
+</action>
+
+<action>Save to {sprint_artifacts}/tech-spec-{slug}.md</action>
+
+</step>
+
+<step n="4" goal="Review and finalize">
+
+<action>Present spec to {user_name}, ask if it captures intent, make changes as needed</action>
+
+<output>**Tech-Spec Complete!**
+
+Saved to: {sprint_artifacts}/tech-spec-{slug}.md
+
+[a] Advanced Elicitation - refine further
+[b] Begin Development (not recommended - fresh context better)
+[d] Done - exit
+[p] Party Mode - get feedback
+
+**Recommended:** Run `dev-spec {sprint_artifacts}/tech-spec-{slug}.md` in fresh context.
+</output>
+
+<ask>Choice (a/b/d/p):</ask>
+
+</step>
+
+</workflow>

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

@@ -0,0 +1,26 @@
+# Quick-Flow: Create Tech-Spec
+name: create-tech-spec
+description: "Conversational spec engineering - ask questions, investigate code, produce implementation-ready tech-spec."
+author: "BMad"
+
+# Config
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+sprint_artifacts: "{config_source}:sprint_artifacts"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec"
+instructions: "{installed_path}/instructions.md"
+
+# Related workflows
+quick_dev_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
+party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+
+standalone: true
+web_bundle: false

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

@@ -0,0 +1,25 @@
+# Quick-Dev Checklist
+
+## Before Implementation
+
+- [ ] Context loaded (tech-spec or user guidance)
+- [ ] Files to modify identified
+- [ ] Patterns understood
+
+## Implementation
+
+- [ ] All tasks completed
+- [ ] Code follows existing patterns
+- [ ] Error handling appropriate
+
+## Testing
+
+- [ ] Tests written (where appropriate)
+- [ ] All tests passing
+- [ ] No regressions
+
+## Completion
+
+- [ ] Acceptance criteria satisfied
+- [ ] Tech-spec updated (if applicable)
+- [ ] Summary provided to user

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

@@ -0,0 +1,202 @@
+# Quick-Dev - Flexible Development Workflow
+
+<workflow>
+
+<critical>Communicate in {communication_language}, tailored to {user_skill_level}</critical>
+<critical>Execute continuously until COMPLETE - do not stop for milestones</critical>
+<critical>Flexible - handles tech-specs OR direct instructions</critical>
+<critical>ALWAYS respect {project_context} if it exists - it defines project standards</critical>
+
+<checkpoint-handlers>
+  <on-select key="a">Load and execute {advanced_elicitation}, then return</on-select>
+  <on-select key="p">Load and execute {party_mode_workflow}, then return</on-select>
+  <on-select key="t">Load and execute {create_tech_spec_workflow}</on-select>
+</checkpoint-handlers>
+
+<step n="1" goal="Load project context and determine execution mode">
+
+<action>Check if {project_context} exists. If yes, load it - this is your foundational reference for ALL implementation decisions (patterns, conventions, architecture).</action>
+
+<action>Parse user input:
+
+**Mode A: Tech-Spec** - e.g., `quick-dev tech-spec-auth.md`
+→ Load spec, extract tasks/context/AC, goto step 3
+
+**Mode B: Direct Instructions** - e.g., `refactor src/foo.ts...`
+→ Offer planning choice
+</action>
+
+<check if="Mode A">
+  <action>Load tech-spec, extract tasks/context/AC</action>
+  <goto>step_3</goto>
+</check>
+
+<check if="Mode B">
+
+  <!-- Escalation Threshold: Lightweight check - should we invoke scale-adaptive? -->
+
+<action>Evaluate escalation threshold against user input (minimal tokens, no file loading):
+
+**Triggers escalation** (if 2+ signals present):
+
+- Multiple components mentioned (e.g., dashboard + api + database)
+- System-level language (e.g., platform, integration, architecture)
+- Uncertainty about approach (e.g., "how should I", "best way to")
+- Multi-layer scope (e.g., UI + backend + data together)
+- Extended timeframe (e.g., "this week", "over the next few days")
+
+**Reduces signal:**
+
+- Simplicity markers (e.g., "just", "quickly", "fix", "bug", "typo", "simple", "basic", "minor")
+- Single file/component focus
+- Confident, specific request
+
+Use holistic judgment, not mechanical keyword matching.</action>
+
+  <!-- No Escalation: Simple request, offer existing choice -->
+  <check if="escalation threshold NOT triggered">
+    <ask>**[t] Plan first** - Create tech-spec then implement
+**[e] Execute directly** - Start now</ask>
+
+    <check if="t">
+      <action>Load and execute {create_tech_spec_workflow}</action>
+      <action>Continue to implementation after spec complete</action>
+    </check>
+
+    <check if="e">
+      <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
+      <goto>step_2</goto>
+    </check>
+
+  </check>
+
+  <!-- Escalation Triggered: Load scale-adaptive and evaluate level -->
+  <check if="escalation threshold triggered">
+    <action>Load {project_levels} and evaluate user input against detection_hints.keywords</action>
+    <action>Determine level (0-4) using scale-adaptive definitions</action>
+
+    <!-- Level 0: Scale-adaptive confirms simple, fall back to standard choice -->
+    <check if="level 0">
+      <ask>**[t] Plan first** - Create tech-spec then implement
+
+**[e] Execute directly** - Start now</ask>
+
+      <check if="t">
+        <action>Load and execute {create_tech_spec_workflow}</action>
+        <action>Continue to implementation after spec complete</action>
+      </check>
+
+      <check if="e">
+        <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
+        <goto>step_2</goto>
+      </check>
+    </check>
+
+    <check if="level 1 or 2 or couldn't determine level">
+      <ask>This looks like a focused feature with multiple components.
+
+**[t] Create tech-spec first** (recommended)
+**[w] Seems bigger than quick-dev** — see what BMad Method recommends (workflow-init)
+**[e] Execute directly**</ask>
+
+      <check if="t">
+        <action>Load and execute {create_tech_spec_workflow}</action>
+        <action>Continue to implementation after spec complete</action>
+      </check>
+
+      <check if="w">
+        <action>Load and execute {workflow_init}</action>
+        <action>EXIT quick-dev - user has been routed to BMad Method</action>
+      </check>
+
+      <check if="e">
+        <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
+        <goto>step_2</goto>
+      </check>
+    </check>
+
+    <!-- Level 3+: BMad Method territory, recommend workflow-init -->
+    <check if="level 3 or higher">
+      <ask>This sounds like platform/system work.
+
+**[w] Start BMad Method** (recommended) (workflow-init)
+**[t] Create tech-spec** (lighter planning)
+**[e] Execute directly** - feeling lucky</ask>
+
+      <check if="w">
+        <action>Load and execute {workflow_init}</action>
+        <action>EXIT quick-dev - user has been routed to BMad Method</action>
+      </check>
+
+      <check if="t">
+        <action>Load and execute {create_tech_spec_workflow}</action>
+        <action>Continue to implementation after spec complete</action>
+      </check>
+
+      <check if="e">
+        <ask>Any additional guidance before I begin? (patterns, files, constraints) Or "go" to start.</ask>
+        <goto>step_2</goto>
+      </check>
+    </check>
+
+  </check>
+
+</check>
+
+</step>
+
+<step n="2" goal="Quick context gathering (direct mode)">
+
+<action>Identify files to modify, find relevant patterns, note dependencies</action>
+
+<action>Create mental plan: tasks, acceptance criteria, files to touch</action>
+
+</step>
+
+<step n="3" goal="Execute implementation" id="step_3">
+
+<action>For each task:
+
+1. **Load Context** - read files from spec or relevant to change
+2. **Implement** - follow patterns, handle errors, follow conventions
+3. **Test** - write tests, run existing tests, verify AC
+4. **Mark Complete** - check off task [x], continue
+   </action>
+
+<action if="3 failures">HALT and request guidance</action>
+<action if="tests fail">Fix before continuing</action>
+
+<critical>Continue through ALL tasks without stopping</critical>
+
+</step>
+
+<step n="4" goal="Verify and complete">
+
+<action>Verify: all tasks [x], tests passing, AC satisfied, patterns followed</action>
+
+<check if="using tech-spec">
+  <action>Update tech-spec status to "Completed", mark all tasks [x]</action>
+</check>
+
+<output>**Implementation Complete!**
+
+**Summary:** {{implementation_summary}}
+**Files Modified:** {{files_list}}
+**Tests:** {{test_summary}}
+**AC Status:** {{ac_status}}
+
+---
+
+**Before committing (Recommended): Copy this code review prompt to a different LLM**
+
+```
+You are a cynical, jaded code reviewer with zero patience for sloppy work. These uncommitted changes were submitted by a clueless weasel and you expect to find problems. Find at least five issues to fix or improve in it. Number them. Be skeptical of everything.
+```
+
+</output>
+
+<action>You must explain what was implemented based on {user_skill_level}</action>
+
+</step>
+
+</workflow>

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

@@ -0,0 +1,33 @@
+# Quick-Flow: Quick-Dev
+name: quick-dev
+description: "Flexible development - execute tech-specs OR direct instructions with optional planning."
+author: "BMad"
+
+# Config
+config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+sprint_artifacts: "{config_source}:sprint_artifacts"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Project context
+project_context: "**/project-context.md"
+
+# Workflow components
+installed_path: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/quick-dev"
+instructions: "{installed_path}/instructions.md"
+checklist: "{installed_path}/checklist.md"
+
+# Related workflows
+create_tech_spec_workflow: "{project-root}/{bmad_folder}/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
+party_mode_exec: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.md"
+advanced_elicitation: "{project-root}/{bmad_folder}/core/tasks/advanced-elicitation.xml"
+
+# Routing resources (lazy-loaded)
+project_levels: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/project-levels.yaml"
+workflow_init: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
+
+standalone: true
+web_bundle: false

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

@@ -196,7 +196,7 @@ Your choice [1/2/3]:
 
 - Mode: {{workflow_mode}}
 - Scan Level: {{scan_level}}
-- Output: {output_folder}/bmm-index.md and related files
+- Output: {output_folder}/index.md and related files
 
 {{#if status_file_found}}
 **Status Updated:**

package/src/modules/bmm/workflows/document-project/workflows/deep-dive-instructions.md

@@ -20,7 +20,7 @@
 
 {{#if has_api_routes}}
 
-### API Routes ({{api_route_count}} endpoints found)
+## API Routes ({{api_route_count}} endpoints found)
 
 {{#each api_route_groups}}
 {{group_index}}. {{group_name}} - {{endpoint_count}} endpoints in `{{path}}`
@@ -29,7 +29,7 @@
 
 {{#if has_feature_modules}}
 
-### Feature Modules ({{feature_count}} features)
+## Feature Modules ({{feature_count}} features)
 
 {{#each feature_modules}}
 {{module_index}}. {{module_name}} - {{file_count}} files in `{{path}}`

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

@@ -0,0 +1,20 @@
+---
+project_name: '{{project_name}}'
+user_name: '{{user_name}}'
+date: '{{date}}'
+sections_completed: []
+---
+
+# Project Context for AI Agents
+
+_This file contains critical rules and patterns that AI agents must follow when implementing code in this project. Focus on unobvious details that agents might otherwise miss._
+
+---
+
+## Technology Stack & Versions
+
+_Documented after discovery phase_
+
+## Critical Implementation Rules
+
+_Documented after discovery phase_