bmad-method 6.0.0-alpha.0 → 6.0.0-alpha.2

package/src/modules/bmm/workflows/testarch/trace/workflow.yaml

@@ -0,0 +1,68 @@
+# Test Architect workflow: trace (enhanced with gate decision)
+name: testarch-trace
+description: "Generate requirements-to-tests traceability matrix, analyze coverage, and make quality gate decision (PASS/CONCERNS/FAIL/WAIVED)"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/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
+
+# Workflow components
+installed_path: "{project-root}/bmad/bmm/workflows/testarch/trace"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+template: "{installed_path}/trace-template.md"
+
+# Variables and inputs
+variables:
+  # Directory paths
+  test_dir: "{project-root}/tests" # Root test directory
+  source_dir: "{project-root}/src" # Source code directory
+
+  # Workflow behavior
+  coverage_levels: "e2e,api,component,unit" # Which test levels to trace
+  gate_type: "story" # story | epic | release | hotfix - determines gate scope
+  decision_mode: "deterministic" # deterministic (rule-based) | manual (team decision)
+
+# Output configuration
+default_output_file: "{output_folder}/traceability-matrix.md"
+
+# Required tools
+required_tools:
+  - read_file # Read story, test files, BMad artifacts
+  - write_file # Create traceability matrix, gate YAML
+  - list_files # Discover test files
+  - search_repo # Find tests by test ID, describe blocks
+  - glob # Find test files matching patterns
+
+# Recommended inputs
+recommended_inputs:
+  - story: "Story markdown with acceptance criteria (required for BMad mode)"
+  - test_files: "Test suite for the feature (auto-discovered if not provided)"
+  - test_design: "Test design with risk/priority assessment (required for Phase 2 gate)"
+  - tech_spec: "Technical specification (optional)"
+  - existing_tests: "Current test suite for analysis"
+  - test_results: "CI/CD test execution results (required for Phase 2 gate)"
+  - nfr_assess: "Non-functional requirements validation (recommended for release gates)"
+  - code_coverage: "Code coverage report (optional)"
+
+tags:
+  - qa
+  - traceability
+  - test-architect
+  - coverage
+  - requirements
+  - gate
+  - decision
+  - release
+
+execution_hints:
+  interactive: false # Minimize prompts
+  autonomous: true # Proceed without user input unless blocked
+  iterative: true
+
+web_bundle: false

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

@@ -0,0 +1,241 @@
+# Workflow Status System
+
+The universal entry point for BMM workflows - answers "what should I do now?" for any agent.
+
+## Overview
+
+The workflow status system provides:
+
+- **Smart project initialization** - Detects existing work and infers project details
+- **Simple status tracking** - Key-value pairs for instant parsing
+- **Intelligent routing** - Suggests next actions based on current state
+- **Modular workflow paths** - Each project type/level has its own clean definition
+
+## Architecture
+
+### Core Components
+
+```
+workflow-status/
+├── workflow.yaml              # Main configuration
+├── instructions.md            # Status checker (99 lines)
+├── workflow-status-template.md # Clean key-value template
+├── project-levels.yaml        # Source of truth for scale definitions
+└── paths/                     # Modular workflow definitions
+    ├── greenfield-level-0.yaml through level-4.yaml
+    ├── brownfield-level-0.yaml through level-4.yaml
+    └── game-design.yaml
+```
+
+### Related Workflow
+
+```
+workflow-init/
+├── workflow.yaml              # Initialization configuration
+└── instructions.md            # Smart setup (182 lines)
+```
+
+## How It Works
+
+### For New Projects
+
+1. User runs `workflow-status`
+2. System finds no status file
+3. Directs to `workflow-init`
+4. Init workflow:
+   - Scans for existing work (PRDs, code, etc.)
+   - Infers project details from what it finds
+   - Asks minimal questions (name + description)
+   - Confirms understanding in one step
+   - Creates status file with workflow path
+
+### For Existing Projects
+
+1. User runs `workflow-status`
+2. System reads status file
+3. Shows current state and options:
+   - Continue in-progress work
+   - Next required step
+   - Available optional workflows
+4. User picks action
+
+## Status File Format
+
+Simple key-value pairs for instant parsing:
+
+```markdown
+PROJECT_NAME: MyProject
+PROJECT_TYPE: software
+PROJECT_LEVEL: 2
+FIELD_TYPE: greenfield
+CURRENT_PHASE: 2-Planning
+CURRENT_WORKFLOW: prd
+NEXT_ACTION: Continue PRD
+NEXT_COMMAND: prd
+NEXT_AGENT: pm
+```
+
+Any agent can instantly grep what they need:
+
+- Any: `grep 'NEXT_ACTION:' status.md`
+- Any: `grep 'CURRENT_PHASE:' status.md`
+- Any: `grep 'NEXT_COMMAND:' status.md`
+
+## Project Levels
+
+Source of truth: `/src/modules/bmm/README.md` lines 77-85
+
+- **Level 0**: Single atomic change (1 story)
+- **Level 1**: Small feature (1-10 stories)
+- **Level 2**: Medium project (5-15 stories)
+- **Level 3**: Complex system (12-40 stories)
+- **Level 4**: Enterprise scale (40+ stories)
+
+## Workflow Paths
+
+Each combination has its own file:
+
+- `greenfield-level-X.yaml` - New projects at each level
+- `brownfield-level-X.yaml` - Existing codebases at each level
+- `game-design.yaml` - Game projects (all levels)
+
+Benefits:
+
+- Load only what's needed (60 lines vs 750+)
+- Easy to maintain individual paths
+- Clear separation of concerns
+
+## Smart Detection
+
+The init workflow intelligently detects:
+
+**Project Type:**
+
+- Finds GDD → game
+- Otherwise → software
+
+**Project Level:**
+
+- Reads PRD epic/story counts
+- Analyzes scope descriptions
+- Makes educated guess
+
+**Field Type:**
+
+- Finds source code → brownfield
+- Only planning docs → greenfield
+- Checks git history age
+
+**Documentation Status:**
+
+- Finds index.md → was undocumented
+- Good README → documented
+- Missing docs → needs documentation
+
+## Usage Examples
+
+### Any Agent Checking Status
+
+```
+Agent: workflow-status
+Result: "Current: Phase 2 - Planning, Next: prd (pm agent)"
+```
+
+### New Project Setup
+
+```
+Agent: workflow-status
+System: "No status found. Run workflow-init"
+Agent: workflow-init
+System: "Tell me about your project"
+User: "Building a dashboard with user management"
+System: "Level 2 greenfield software project. Correct?"
+User: "Yes"
+System: "Status created! Next: pm agent, run prd"
+```
+
+### Smart Inference
+
+```
+System finds: prd-dashboard.md with 3 epics
+System finds: package.json, src/ directory
+System infers: Level 2 brownfield software
+User confirms or corrects
+```
+
+## Philosophy
+
+**Less Structure, More Intelligence**
+
+Instead of complex if/else logic:
+
+- Trust the LLM to analyze and infer
+- Use natural language for corrections
+- Keep menus simple and contextual
+- Let intelligence emerge from the model
+
+**Result:** A workflow system that feels like talking to a smart assistant, not filling out a form.
+
+## Implementation Details
+
+### workflow-init (6 Steps)
+
+1. **Scan for existing work** - Check for docs, code, git history
+2. **Confirm findings** - Show what was detected (if anything)
+3. **Gather info** - Name, description, confirm type/level/field
+4. **Load path file** - Select appropriate workflow definition
+5. **Generate workflow** - Build from path file
+6. **Create status file** - Save and show next step
+
+### workflow-status (4 Steps)
+
+1. **Check for status file** - Direct to init if missing
+2. **Parse status** - Extract key-value pairs
+3. **Display options** - Show current, required, optional
+4. **Handle selection** - Execute user's choice
+
+## Best Practices
+
+1. **Let the AI guess** - It's usually right, user corrects if needed
+2. **One conversation** - Get all info in Step 3 of init
+3. **Simple parsing** - Key-value pairs, not complex structures
+4. **Modular paths** - Each scenario in its own file
+5. **Trust intelligence** - LLM understands context better than rules
+
+## Integration
+
+Other workflows read the status to coordinate:
+
+- Any workflow can check CURRENT_PHASE
+- Workflows can verify prerequisites are complete
+- All agents can ask "what should I do?"
+
+**Phase 4 (Implementation):**
+
+- workflow-status only tracks sprint-planning completion
+- After sprint-planning, all story/epic tracking happens in the sprint plan output file
+- Phase 4 workflows do NOT read/write workflow-status (except sprint-planning for prerequisite verification)
+
+The status file is the single source of truth for Phases 1-3 and the hub that keeps all agents synchronized.
+
+## Benefits
+
+✅ **Smart Detection** - Infers from existing work instead of asking everything
+✅ **Minimal Questions** - Just name and description in most cases
+✅ **Clean Status** - Simple key-value pairs for instant parsing
+✅ **Modular Paths** - 60-line files instead of 750+ line monolith
+✅ **Natural Language** - "Tell me about your project" not "Pick 1-12"
+✅ **Intelligent Menus** - Shows only relevant options
+✅ **Fast Parsing** - Grep instead of complex logic
+✅ **Easy Maintenance** - Change one level without affecting others
+
+## Future Enhancements
+
+- Visual progress indicators
+- Time tracking and estimates
+- Multi-project support
+- Team synchronization
+
+---
+
+**This workflow is the front door to BMad Method. Start here to know what to do next.**

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

@@ -0,0 +1,297 @@
+# Workflow Init - Project Setup Instructions
+
+<critical>The workflow execution engine is governed by: {project-root}/bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: workflow-init/workflow.yaml</critical>
+<critical>Communicate in {communication_language} with {user_name}</critical>
+
+<workflow>
+
+<step n="1" goal="Quick scan and ask user about THEIR work">
+<output>Welcome to BMad Method, {user_name}!</output>
+
+<action>Quick scan for context (do NOT analyze in depth yet):</action>
+
+- Check for codebase: src/, lib/, package.json, .git, etc.
+- Check for BMM artifacts: PRD, epics, stories, tech-spec, architecture docs
+- Store what was found but do NOT infer project details yet
+
+<ask>What's your project called? {{#if project_name}}(Config shows: {{project_name}}){{/if}}</ask>
+<action>Set project_name</action>
+<template-output>project_name</template-output>
+
+<check if="found artifacts OR found codebase">
+<output>I found some existing work here. Let me understand what you're working on:</output>
+
+<check if="found artifacts">
+<output>
+**Planning Documents Found:**
+{{#each artifacts}}
+- {{artifact_name}} ({{artifact_type}}, {{story_count}} stories, modified {{date}})
+{{/each}}
+</output>
+</check>
+
+<check if="found codebase">
+<output>
+**Codebase Found:**
+- Source code in: {{source_dirs}}
+- Tech stack: {{detected_tech_stack}}
+{{#if git_history}}
+- Git history: {{commit_count}} commits, last commit {{last_commit_date}}
+{{/if}}
+</output>
+</check>
+
+<ask>Looking at what I found, are these:
+
+a) **Works in progress you're finishing** - continuing the work described in these documents
+b) **Documents from a previous effort** - you're starting something NEW and different now
+c) **The proposed work you're about to start** - these describe what you want to do
+d) **None of these** - let me explain what I'm actually working on
+
+Your choice [a/b/c/d]:</ask>
+
+<check if="choice == a">
+  <action>User is continuing old work - analyze artifacts to get details</action>
+  <action>Set continuing_old_work = true</action>
+  <action>Go to Step 2 (Analyze artifacts for details)</action>
+</check>
+
+<check if="choice == b">
+  <action>User is doing NEW work - old artifacts are just context</action>
+  <action>Set continuing_old_work = false</action>
+  <action>Go to Step 3 (Ask about NEW work)</action>
+</check>
+
+<check if="choice == c">
+  <action>Artifacts describe proposed work</action>
+  <action>Set continuing_old_work = true</action>
+  <action>Go to Step 2 (Analyze artifacts for details)</action>
+</check>
+
+<check if="choice == d">
+  <action>User will explain their situation</action>
+  <action>Go to Step 3 (Ask about their work)</action>
+</check>
+</check>
+
+<check if="NOT found artifacts AND NOT found codebase">
+  <output>I don't see any existing code or planning documents. Looks like we're starting fresh!</output>
+  <action>Go to Step 3 (Ask about their work)</action>
+</check>
+</step>
+
+<step n="2" goal="Analyze artifacts for continuing work" if="continuing_old_work == true">
+<action>Analyze found artifacts in detail:</action>
+<action>Extract project type from content (game vs software)</action>
+<action>Count stories/epics to estimate level:
+  - Level 0: 1 story
+  - Level 1: 1-10 stories
+  - Level 2: 5-15 stories
+  - Level 3: 12-40 stories
+  - Level 4: 40+ stories
+</action>
+<action>Detect field type from codebase presence (greenfield vs brownfield)</action>
+
+<output>Based on the artifacts you're continuing, I'm suggesting **Level {{project_level}}** because I found {{story_count}} stories across {{epic_count}} epics.
+
+Here's the complexity scale for reference:
+
+**{{field_type}} Project Levels:**
+
+- **Level 0** - Single atomic change (1 story) - bug fixes, typos, minor updates
+- **Level 1** - Small feature (1-10 stories) - simple additions, isolated features
+- **Level 2** - Medium feature set (5-15 stories) - dashboards, multiple related features
+- **Level 3** - Complex integration (12-40 stories) - platform features, major integrations
+- **Level 4** - Enterprise expansion (40+ stories) - multi-tenant, ecosystem changes
+
+**My suggestion:** Level {{project_level}} {{field_type}} {{project_type}} project
+</output>
+
+<ask>Does this match what you're working on? (y/n or tell me what's different)</ask>
+
+<check if="user confirms">
+  <action>Use analyzed values</action>
+  <action>Go to Step 4 (Load workflow path)</action>
+</check>
+
+<check if="user corrects">
+  <action>Update values based on user corrections</action>
+  <ask>Updated to: Level {{project_level}} {{field_type}} {{project_type}}. Correct? (y/n)</ask>
+  <action>Go to Step 4 (Load workflow path)</action>
+</check>
+
+<template-output>project_name</template-output>
+<template-output>project_type</template-output>
+<template-output>project_level</template-output>
+<template-output>field_type</template-output>
+</step>
+
+<step n="3" goal="Ask user about THEIR work">
+<ask>Tell me about what you're working on. What's the goal?</ask>
+
+<action>Analyze user's description using keyword detection:
+
+- Level 0 keywords: "fix", "bug", "typo", "small change", "update", "patch", "one file"
+- Level 1 keywords: "simple", "basic", "small feature", "add", "minor", "single feature"
+- Level 2 keywords: "dashboard", "several features", "admin panel", "medium", "feature set"
+- Level 3 keywords: "platform", "integration", "complex", "system", "architecture"
+- Level 4 keywords: "enterprise", "multi-tenant", "multiple products", "ecosystem", "phased"
+  </action>
+
+<action>Make initial determination:
+
+- project_type (game or software)
+- project_level (0-4) - tentative based on keywords
+- field_type (greenfield or brownfield)
+- confidence (high/medium/low) - based on clarity of description
+  </action>
+
+<check if="confidence == low OR description is ambiguous">
+  <output>Thanks! Let me ask a few clarifying questions to make sure I route you correctly:</output>
+
+<ask>1. Roughly how many distinct features or changes do you think this involves?
+
+- Just one thing (e.g., fix a bug, add one button, update one API)
+- A small feature (2-5 related changes)
+- Several features (5-15 related things)
+- A major addition (15-40 things to do)
+- A large initiative (40+ changes across many areas)
+  </ask>
+
+<action>Adjust project_level based on response</action>
+
+<ask>2. How much of the existing codebase will this touch?
+
+- Single file or small area
+- One module or component
+- Multiple modules (2-4 areas)
+- Many modules with integration needs
+- System-wide changes
+  </ask>
+
+<action>Validate and adjust project_level based on scope</action>
+
+  <check if="project_type unclear">
+    <ask>3. Is this a game or a software application?</ask>
+    <action>Set project_type based on response</action>
+  </check>
+</check>
+
+<check if="found codebase BUT field_type still unclear">
+  <ask>I see you have existing code here. Are you:
+
+1. **Adding to or modifying** the existing codebase (brownfield)
+2. **Starting fresh** - the existing code is just a scaffold/template (greenfield)
+3. **Something else** - let me clarify
+
+Your choice [1/2/3]:</ask>
+
+  <check if="choice == 1">
+    <action>Set field_type = "brownfield"</action>
+  </check>
+
+  <check if="choice == 2">
+    <action>Set field_type = "greenfield"</action>
+    <output>Got it - treating as greenfield despite the scaffold.</output>
+  </check>
+
+  <check if="choice == 3">
+    <ask>Please explain your situation:</ask>
+    <action>Analyze explanation and set field_type accordingly</action>
+  </check>
+</check>
+
+<action>Build reasoning for suggestion</action>
+<action>Store detected_indicators (keywords, scope indicators, complexity signals)</action>
+
+<output>Based on what you've described, I'm suggesting **Level {{project_level}}** because:
+
+{{reasoning}} (detected: {{detected_indicators}})
+
+Here's the complexity scale for reference:
+
+**{{field_type}} Project Levels:**
+
+- **Level 0** - Single atomic change (1 story) - bug fixes, typos, minor updates, single file changes
+- **Level 1** - Small feature (1-10 stories) - simple additions, isolated features, one module
+- **Level 2** - Medium feature set (5-15 stories) - dashboards, multiple related features, several modules
+- **Level 3** - Complex integration (12-40 stories) - platform features, major integrations, architectural changes
+- **Level 4** - Enterprise expansion (40+ stories) - multi-tenant, ecosystem changes, system-wide initiatives
+
+**My suggestion:** Level {{project_level}} {{field_type}} {{project_type}} project
+</output>
+
+<ask>Does this match what you're working on? (y/n or tell me what's different)</ask>
+
+<check if="user confirms">
+  <action>Use determined values</action>
+  <action>Go to Step 4 (Load workflow path)</action>
+</check>
+
+<check if="user corrects">
+  <action>Update values based on corrections</action>
+  <output>Updated to: Level {{project_level}} {{field_type}} {{project_type}}</output>
+  <ask>Does that look right now? (y/n)</ask>
+  <action>If yes, go to Step 4. If no, ask what needs adjustment and repeat.</action>
+</check>
+
+<template-output>project_name</template-output>
+<template-output>project_type</template-output>
+<template-output>project_level</template-output>
+<template-output>field_type</template-output>
+</step>
+
+<step n="4" goal="Load appropriate workflow path">
+<action>Determine path file based on selections:</action>
+
+<check if="project_type == game">
+  <action>Load {path_files}/game-design.yaml</action>
+  <action>Set workflow_path_file = "game-design.yaml"</action>
+</check>
+
+<check if="project_type == software">
+  <!-- field_type will be "greenfield" or "brownfield", project_level will be 0-4 -->
+  <action>Build filename: {field_type}-level-{project_level}.yaml</action>
+  <action>Load {path_files}/{field_type}-level-{project_level}.yaml</action>
+  <action>Set workflow_path_file = constructed filename</action>
+</check>
+
+<action>Parse workflow path file to extract phases and workflows</action>
+<template-output>workflow_path_file</template-output>
+</step>
+
+<step n="5" goal="Generate workflow summary">
+<action>Build workflow from loaded path file</action>
+<action>Display phases and workflows</action>
+<action>Set initial values for status file</action>
+
+<template-output>current_phase</template-output>
+<template-output>current_workflow</template-output>
+<template-output>current_agent</template-output>
+<template-output>next_action</template-output>
+<template-output>next_command</template-output>
+<template-output>next_agent</template-output>
+</step>
+
+<step n="6" goal="Create status file">
+<action>Initialize all status values</action>
+<template-output>start_date</template-output>
+<template-output>last_updated</template-output>
+<template-output>phase_1_complete</template-output>
+<template-output>phase_2_complete</template-output>
+<template-output>phase_3_complete</template-output>
+<template-output>phase_4_complete</template-output>
+
+<ask>Ready to create your workflow status file? (y/n)</ask>
+
+<check if="answer == y">
+  <action>Save status file to {output_folder}/bmm-workflow-status.md</action>
+  <output>✅ Status file created! Next up: {{next_agent}} agent, run `{{next_command}}`</output>
+  <check if="next_agent !== current_agent">
+    <output>It is strongly recommended to clear the context or start a new chat and load the next agent to execute the next command from that agents help menu, unless there is something else I can do for you first.</output>
+  </check>
+</check>
+</step>
+
+</workflow>

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

@@ -0,0 +1,28 @@
+# Workflow Init - Initial Project Setup
+name: workflow-init
+description: "Initialize a new BMM project by determining level, type, and creating workflow path"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+project_name: "{config_source}:project_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/bmm/workflows/workflow-status/init"
+instructions: "{installed_path}/instructions.md"
+template: "{project-root}/bmad/bmm/workflows/workflow-status/workflow-status-template.md"
+
+# Path data files
+path_files: "{project-root}/bmad/bmm/workflows/workflow-status/paths/"
+
+# Output configuration
+default_output_file: "{output_folder}/bmm-workflow-status.md"
+
+standalone: true
+web_bundle: false