chore: add BMAD agent workflows and configuration system

- Add comprehensive agent workflow definitions for 8 specialized roles (analyst, architect, developer, product manager, scrum master, technical writer, UX designer, QA engineer)
- Add 35+ workflow definitions covering analysis, planning, solutioning, and implementation phases
- Add BMAD configuration system with agent, task, tool, workflow, and file manifests
- Add BMM (Business Model Methodology) documentation including quick-start guides, architecture references, and workflow analysis
- Add test architecture knowledge base with 20+ testing patterns and best practices
- Add team configuration templates and party mode setup for collaborative development
- Establish foundation for enterprise agentic development framework with adaptive scaling capabilities
This commit is contained in:
mahdiarghyani
2025-11-30 14:36:05 +03:30
parent af8b45aadb
commit 1586bb7f80
355 changed files with 73215 additions and 306 deletions
@@ -0,0 +1,334 @@
# 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>
<critical>This workflow handles BOTH new projects AND legacy projects being migrated to BMad Method</critical>
<workflow>
<step n="1" goal="Scan for existing work">
<output>Welcome to BMad Method, {user_name}!</output>
<action>Perform comprehensive scan for existing work:
- BMM artifacts: PRD, tech-spec, epics, architecture, UX, brief, research, brainstorm
- Implementation: stories, sprint-status, workflow-status
- Codebase: source directories, package files, git repo
- Check both {output_folder} and {sprint_artifacts} locations
</action>
<action>Categorize into one of these states:
- CLEAN: No artifacts or code (or scaffold only)
- PLANNING: Has PRD/spec but no implementation
- ACTIVE: Has stories or sprint status
- LEGACY: Has code but no BMM artifacts
- UNCLEAR: Mixed state needs clarification
</action>
<ask>What's your project called? {{#if project_name}}(Config shows: {{project_name}}){{/if}}</ask>
<action>Store project_name</action>
<template-output>project_name</template-output>
</step>
<step n="2" goal="Choose setup path">
<check if="state == CLEAN">
<output>Perfect! Fresh start detected.</output>
<action>Continue to step 3</action>
</check>
<check if="state == ACTIVE AND workflow_status exists">
<output>✅ You already have workflow tracking at: {{workflow_status_path}}
To check progress: Load any BMM agent and run /bmad:bmm:workflows:workflow-status
Happy building! 🚀</output>
<action>Exit workflow (already initialized)</action>
</check>
<check if="state != CLEAN">
<output>Found existing work:
{{summary_of_findings}}</output>
<ask>How would you like to proceed?
a) **Continue** - Work with existing artifacts
b) **Archive & Start Fresh** - Move old work to archive
c) **Express Setup** - I know exactly what I need
d) **Guided Setup** - Walk me through options
Choice [a/b/c/d]:</ask>
<check if="choice == a">
<action>Set continuing_existing = true</action>
<action>Store found artifacts</action>
<action>Continue to step 7 (detect track from artifacts)</action>
</check>
<check if="choice == b">
<ask>Archive existing work? (y/n)</ask>
<action if="y">Move artifacts to {output_folder}/archive/</action>
<output>Ready for fresh start!</output>
<action>Continue to step 3</action>
</check>
<check if="choice == c">
<action>Jump to step 3 (express path)</action>
</check>
<check if="choice == d">
<action>Continue to step 4 (guided path)</action>
</check>
</check>
<check if="state == CLEAN">
<ask>Setup approach:
a) **Express** - I know what I need
b) **Guided** - Show me the options
Choice [a/b]:</ask>
<check if="choice == a">
<action>Continue to step 3 (express)</action>
</check>
<check if="choice == b">
<action>Continue to step 4 (guided)</action>
</check>
</check>
</step>
<step n="3" goal="Express setup path">
<ask>Is this for:
1) **New project** (greenfield)
2) **Existing codebase** (brownfield)
Choice [1/2]:</ask>
<action>Set field_type based on choice</action>
<ask>Planning approach:
1. **Quick Flow** - Minimal planning, fast to code
2. **BMad Method** - Full planning for complex projects
3. **Enterprise Method** - Extended planning with security/DevOps
Choice [1/2/3]:</ask>
<action>Map to selected_track: quick-flow/method/enterprise</action>
<template-output>field_type</template-output>
<template-output>selected_track</template-output>
<action>Jump to step 6 (discovery options)</action>
</step>
<step n="4" goal="Guided setup - understand project">
<ask>Tell me about what you're working on. What's the goal?</ask>
<action>Store user_description</action>
<action>Analyze for field type indicators:
- Brownfield: "existing", "current", "enhance", "modify"
- Greenfield: "new", "build", "create", "from scratch"
- If codebase exists, default to brownfield unless user indicates scaffold
</action>
<check if="field_type unclear AND codebase exists">
<ask>I see existing code. Are you:
1) **Modifying** existing codebase (brownfield)
2) **Starting fresh** - code is just scaffold (greenfield)
Choice [1/2]:</ask>
<action>Set field_type based on answer</action>
</check>
<action if="field_type not set">Set based on codebase presence</action>
<action>Check for game development keywords</action>
<check if="game_detected">
<output>🎮 **GAME DEVELOPMENT DETECTED**
For game development, install the BMGD module:
```bash
bmad install bmgd
```
Continue with software workflows? (y/n)</output>
<ask>Choice:</ask>
<action if="n">Exit workflow</action>
</check>
<template-output>user_description</template-output>
<template-output>field_type</template-output>
<action>Continue to step 5</action>
</step>
<step n="5" goal="Guided setup - select track">
<output>Based on your project, here are your planning options:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**1. Quick Flow** 🚀
- Minimal planning, straight to code
- Best for: Simple features, bug fixes
- Risk: Potential rework if complexity emerges
**2. BMad Method** 🎯 {{#if recommended}}(RECOMMENDED){{/if}}
- Full planning: PRD + UX + Architecture
- Best for: Products, platforms, complex features
- Benefit: AI agents have complete context for better results
**3. Enterprise Method** 🏢
- Extended: Method + Security + DevOps + Testing
- Best for: Enterprise, compliance, mission-critical
- Benefit: Comprehensive planning for complex systems
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{{#if brownfield}}
💡 Architecture creates focused solution design from your codebase, keeping AI agents on track.
{{/if}}</output>
<ask>Which approach fits best?
1. Quick Flow
2. BMad Method {{#if recommended}}(recommended){{/if}}
3. Enterprise Method
4. Help me decide
Choice [1/2/3/4]:</ask>
<check if="choice == 4">
<ask>What concerns you about choosing?</ask>
<action>Provide tailored guidance based on concerns</action>
<action>Loop back to choice</action>
</check>
<action>Map choice to selected_track</action>
<template-output>selected_track</template-output>
</step>
<step n="6" goal="Discovery workflows selection (unified)">
<action>Determine available discovery workflows based on:
- field_type (greenfield gets product-brief option)
- selected_track (quick-flow skips product-brief)
</action>
<check if="field_type == greenfield AND selected_track in [method, enterprise]">
<output>Optional discovery workflows can help clarify your vision:</output>
<ask>Select any you'd like to include:
1. 🧠 **Brainstorm** - Creative exploration and ideation
2. 🔍 **Research** - Technical/competitive analysis
3. 📋 **Product Brief** - Strategic product planning (recommended)
Enter numbers (e.g., "1,3" or "all" or "none"): </ask>
</check>
<check if="field_type == brownfield OR selected_track == quick-flow">
<output>Optional discovery workflows:</output>
<ask>Include any of these?
1. 🧠 **Brainstorm** - Creative exploration
2. 🔍 **Research** - Domain analysis
Enter numbers (e.g., "1,2" or "none"): </ask>
</check>
<action>Parse selections and set:
- brainstorm_requested
- research_requested
- product_brief_requested (if applicable)
</action>
<template-output>brainstorm_requested</template-output>
<template-output>research_requested</template-output>
<template-output>product_brief_requested</template-output>
<check if="brownfield AND selected_track != quick-flow">
<output>💡 **Note:** For brownfield projects, run document-project workflow first to analyze your codebase.</output>
</check>
</step>
<step n="7" goal="Detect track from artifacts" if="continuing_existing OR migrating_legacy">
<action>Analyze artifacts to detect track:
- Has PRD → BMad Method
- Has tech-spec only → Quick Flow
- Has Security/DevOps → Enterprise Method
</action>
<output>Detected: **{{detected_track}}** based on {{found_artifacts}}</output>
<ask>Correct? (y/n)</ask>
<ask if="n">Which track instead?
1. Quick Flow
2. BMad Method
3. Enterprise Method
Choice:</ask>
<action>Set selected_track</action>
<template-output>selected_track</template-output>
</step>
<step n="8" goal="Generate workflow path">
<action>Load path file: {path_files}/{{selected_track}}-{{field_type}}.yaml</action>
<action>Build workflow_items from path file</action>
<action>Scan for existing completed work and update statuses</action>
<action>Set generated date</action>
<template-output>generated</template-output>
<template-output>workflow_path_file</template-output>
<template-output>workflow_items</template-output>
</step>
<step n="9" goal="Create tracking file">
<output>Your BMad workflow path:
**Track:** {{selected_track}}
**Type:** {{field_type}}
**Project:** {{project_name}}
{{#if brownfield}}Prerequisites: document-project{{/if}}
{{#if has_discovery}}Discovery: {{list_selected_discovery}}{{/if}}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
{{workflow_path_summary}}
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━</output>
<ask>Create workflow tracking file? (y/n)</ask>
<check if="y">
<action>Generate YAML from template with all variables</action>
<action>Save to {output_folder}/bmm-workflow-status.yaml</action>
<action>Identify next workflow and agent</action>
<output>✅ **Created:** {output_folder}/bmm-workflow-status.yaml
**Next:** {{next_workflow_name}}
**Agent:** {{next_agent}}
**Command:** /bmad:bmm:workflows:{{next_workflow_id}}
{{#if next_agent not in [analyst, pm]}}
💡 Start new chat with **{{next_agent}}** agent first.
{{/if}}
To check progress: /bmad:bmm:workflows:workflow-status
Happy building! 🚀</output>
</check>
<check if="n">
<output>No problem! Run workflow-init again when ready.</output>
</check>
</step>
</workflow>
@@ -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"
sprint_artifacts: "{config_source}:sprint_artifacts"
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.yaml"
# Path data files
path_files: "{project-root}/.bmad/bmm/workflows/workflow-status/paths/"
# Output configuration
default_output_file: "{output_folder}/bmm-workflow-status.yaml"
standalone: true
@@ -0,0 +1,388 @@
# Workflow Status Check - Multi-Mode Service
<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/workflow-status/workflow.yaml</critical>
<critical>This workflow operates in multiple modes: interactive (default), validate, data, init-check, update</critical>
<critical>Other workflows can call this as a service to avoid duplicating status logic</critical>
<critical>⚠️ ABSOLUTELY NO TIME ESTIMATES - NEVER mention hours, days, weeks, months, or ANY time-based predictions. AI has fundamentally changed development speed - what once took teams weeks/months can now be done by one person in hours. DO NOT give ANY time estimates whatsoever.</critical>
<workflow>
<step n="0" goal="Determine execution mode">
<action>Check for {{mode}} parameter passed by calling workflow</action>
<action>Default mode = "interactive" if not specified</action>
<check if="mode == interactive">
<action>Continue to Step 1 for normal status check flow</action>
</check>
<check if="mode == validate">
<action>Jump to Step 10 for workflow validation service</action>
</check>
<check if="mode == data">
<action>Jump to Step 20 for data extraction service</action>
</check>
<check if="mode == init-check">
<action>Jump to Step 30 for simple init check</action>
</check>
<check if="mode == update">
<action>Jump to Step 40 for status update service</action>
</check>
</step>
<step n="1" goal="Check for status file">
<action>Search {output_folder}/ for file: bmm-workflow-status.yaml</action>
<check if="no status file found">
<output>No workflow status found. To get started:
Load analyst agent and run: `workflow-init`
This will guide you through project setup and create your workflow path.</output>
<action>Exit workflow</action>
</check>
<check if="status file found">
<action>Continue to step 2</action>
</check>
</step>
<step n="2" goal="Read and parse status">
<action>Read bmm-workflow-status.yaml</action>
<action>Parse YAML file and extract metadata from comments and fields:</action>
Parse these fields from YAML comments and metadata:
- project (from YAML field)
- project_type (from YAML field)
- project_level (from YAML field)
- field_type (from YAML field)
- workflow_path (from YAML field)
<action>Parse workflow_status section:</action>
- Extract all workflow entries with their statuses
- Identify completed workflows (status = file path)
- Identify pending workflows (status = required/optional/recommended/conditional)
- Identify skipped workflows (status = skipped)
<action>Determine current state:</action>
- Find first workflow with status != file path and != skipped
- This is the NEXT workflow to work on
- Look up agent and command from workflow path file
</step>
<step n="3" goal="Display current status and options">
<action>Load workflow path file based on workflow_path field</action>
<action>Identify current phase from next workflow to be done</action>
<action>Build list of completed, pending, and optional workflows</action>
<action>For each workflow, look up its agent from the path file</action>
<output>
## 📊 Current Status
**Project:** {{project}} (Level {{project_level}} {{project_type}})
**Path:** {{workflow_path}}
**Progress:**
{{#each phases}}
{{phase_name}}:
{{#each workflows_in_phase}}
- {{workflow_name}} ({{agent}}): {{status_display}}
{{/each}}
{{/each}}
## 🎯 Next Steps
**Next Workflow:** {{next_workflow_name}}
**Agent:** {{next_agent}}
**Command:** /bmad:bmm:workflows:{{next_workflow_id}}
{{#if optional_workflows_available}}
**Optional Workflows Available:**
{{#each optional_workflows}}
- {{workflow_name}} ({{agent}}) - {{status}}
{{/each}}
{{/if}}
</output>
</step>
<step n="4" goal="Offer actions">
<ask>What would you like to do?
1. **Start next workflow** - {{next_workflow_name}} ({{next_agent}})
{{#if optional_workflows_available}}
2. **Run optional workflow** - Choose from available options
{{/if}}
3. **View full status YAML** - See complete status file
4. **Update workflow status** - Mark a workflow as completed or skipped
5. **Exit** - Return to agent
Your choice:</ask>
<action>Handle user selection based on available options</action>
<check if="choice == 1">
<output>Ready to run {{next_workflow_name}}!
**Command:** /bmad:bmm:workflows:{{next_workflow_id}}
**Agent:** Load {{next_agent}} agent first
{{#if next_agent !== current_agent}}
Tip: Start a new chat and load the {{next_agent}} agent before running this workflow.
{{/if}}
</output>
</check>
<check if="choice == 2 AND optional_workflows_available">
<ask>Which optional workflow?
{{#each optional_workflows numbered}}
{{number}}. {{workflow_name}} ({{agent}})
{{/each}}
Your choice:</ask>
<action>Display selected workflow command and agent</action>
</check>
<check if="choice == 3">
<action>Display complete bmm-workflow-status.yaml file contents</action>
</check>
<check if="choice == 4">
<ask>What would you like to update?
1. Mark a workflow as **completed** (provide file path)
2. Mark a workflow as **skipped**
Your choice:</ask>
<check if="update_choice == 1">
<ask>Which workflow? (Enter workflow ID like 'prd' or 'create-architecture')</ask>
<ask>File path created? (e.g., docs/prd.md)</ask>
<critical>ONLY write the file path as the status value - no other text, notes, or metadata</critical>
<action>Update workflow_status in YAML file: {{workflow_id}}: {{file_path}}</action>
<action>Save updated YAML file preserving ALL structure and comments</action>
<output>✅ Updated {{workflow_id}} to completed: {{file_path}}</output>
</check>
<check if="update_choice == 2">
<ask>Which workflow to skip? (Enter workflow ID)</ask>
<action>Update workflow_status in YAML file: {{workflow_id}}: skipped</action>
<action>Save updated YAML file</action>
<output>✅ Marked {{workflow_id}} as skipped</output>
</check>
</check>
</step>
<!-- ============================================= -->
<!-- SERVICE MODES - Called by other workflows -->
<!-- ============================================= -->
<step n="10" goal="Validate mode - Check if calling workflow should proceed">
<action>Read {output_folder}/bmm-workflow-status.yaml if exists</action>
<check if="status file not found">
<template-output>status_exists = false</template-output>
<template-output>should_proceed = true</template-output>
<template-output>warning = "No status file found. Running without progress tracking."</template-output>
<template-output>suggestion = "Consider running workflow-init first for progress tracking"</template-output>
<action>Return to calling workflow</action>
</check>
<check if="status file found">
<action>Parse YAML file to extract project metadata and workflow_status</action>
<action>Load workflow path file from workflow_path field</action>
<action>Find first non-completed workflow in workflow_status (next workflow)</action>
<action>Check if {{calling_workflow}} matches next workflow or is in the workflow list</action>
<template-output>status_exists = true</template-output>
<template-output>project_level = {{project_level}}</template-output>
<template-output>project_type = {{project_type}}</template-output>
<template-output>field_type = {{field_type}}</template-output>
<template-output>next_workflow = {{next_workflow_id}}</template-output>
<check if="calling_workflow == next_workflow">
<template-output>should_proceed = true</template-output>
<template-output>warning = ""</template-output>
<template-output>suggestion = "Proceeding with planned next step"</template-output>
</check>
<check if="calling_workflow in workflow_status list">
<action>Check the status of calling_workflow in YAML</action>
<check if="status is file path">
<template-output>should_proceed = true</template-output>
<template-output>warning = "⚠️ Workflow already completed: {{calling_workflow}}"</template-output>
<template-output>suggestion = "This workflow was already completed. Re-running will overwrite: {{status}}"</template-output>
</check>
<check if="status is optional/recommended">
<template-output>should_proceed = true</template-output>
<template-output>warning = "Running optional workflow {{calling_workflow}}"</template-output>
<template-output>suggestion = "This is optional. Expected next: {{next_workflow}}"</template-output>
</check>
<check if="status is required but not next">
<template-output>should_proceed = true</template-output>
<template-output>warning = "⚠️ Out of sequence: Expected {{next_workflow}}, running {{calling_workflow}}"</template-output>
<template-output>suggestion = "Consider running {{next_workflow}} instead, or continue if intentional"</template-output>
</check>
</check>
<check if="calling_workflow NOT in workflow_status list">
<template-output>should_proceed = true</template-output>
<template-output>warning = "⚠️ Unknown workflow: {{calling_workflow}} not in workflow path"</template-output>
<template-output>suggestion = "This workflow is not part of the defined path for this project"</template-output>
</check>
<template-output>status_file_path = {{path to bmm-workflow-status.yaml}}</template-output>
</check>
<action>Return control to calling workflow with all template outputs</action>
</step>
<step n="20" goal="Data mode - Extract specific information">
<action>Read {output_folder}/bmm-workflow-status.yaml if exists</action>
<check if="status file not found">
<template-output>status_exists = false</template-output>
<template-output>error = "No status file to extract data from"</template-output>
<action>Return to calling workflow</action>
</check>
<check if="status file found">
<action>Parse YAML file completely</action>
<template-output>status_exists = true</template-output>
<check if="data_request == project_config">
<template-output>project_name = {{project}}</template-output>
<template-output>project_type = {{project_type}}</template-output>
<template-output>project_level = {{project_level}}</template-output>
<template-output>field_type = {{field_type}}</template-output>
<template-output>workflow_path = {{workflow_path}}</template-output>
</check>
<check if="data_request == workflow_status">
<action>Parse workflow_status section and return all workflow: status pairs</action>
<template-output>workflow_status = {{workflow_status_object}}</template-output>
<action>Calculate completion stats:</action>
<template-output>total_workflows = {{count all workflows}}</template-output>
<template-output>completed_workflows = {{count file path statuses}}</template-output>
<template-output>pending_workflows = {{count required/optional/etc}}</template-output>
<template-output>skipped_workflows = {{count skipped}}</template-output>
</check>
<check if="data_request == all">
<action>Return all parsed fields as template outputs</action>
<template-output>project = {{project}}</template-output>
<template-output>project_type = {{project_type}}</template-output>
<template-output>project_level = {{project_level}}</template-output>
<template-output>field_type = {{field_type}}</template-output>
<template-output>workflow_path = {{workflow_path}}</template-output>
<template-output>workflow_status = {{workflow_status_object}}</template-output>
<template-output>generated = {{generated}}</template-output>
</check>
<template-output>status_file_path = {{path to bmm-workflow-status.yaml}}</template-output>
</check>
<action>Return control to calling workflow with requested data</action>
</step>
<step n="30" goal="Init-check mode - Simple existence check">
<action>Check if {output_folder}/bmm-workflow-status.yaml exists</action>
<check if="exists">
<template-output>status_exists = true</template-output>
<template-output>suggestion = "Status file found. Ready to proceed."</template-output>
</check>
<check if="not exists">
<template-output>status_exists = false</template-output>
<template-output>suggestion = "No status file. Run workflow-init to create one (optional for progress tracking)"</template-output>
</check>
<action>Return immediately to calling workflow</action>
</step>
<step n="40" goal="Update mode - Centralized status file updates">
<action>Read {output_folder}/bmm-workflow-status.yaml</action>
<check if="status file not found">
<template-output>success = false</template-output>
<template-output>error = "No status file found. Cannot update."</template-output>
<action>Return to calling workflow</action>
</check>
<check if="status file found">
<action>Parse YAML file completely</action>
<action>Load workflow path file from workflow_path field</action>
<action>Check {{action}} parameter to determine update type</action>
<!-- ============================================= -->
<!-- ACTION: complete_workflow -->
<!-- ============================================= -->
<check if="action == complete_workflow">
<action>Get {{workflow_id}} parameter (required)</action>
<action>Get {{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}}
<action>Find {{workflow_id}} in loaded path YAML</action>
<action>Determine next workflow from path sequence</action>
<action>Find first workflow in workflow_status with status != file path and != skipped</action>
<action>Save updated YAML file preserving ALL structure and comments</action>
<template-output>success = true</template-output>
<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>
</check>
<!-- ============================================= -->
<!-- ACTION: skip_workflow -->
<!-- ============================================= -->
<check if="action == skip_workflow">
<action>Get {{workflow_id}} parameter (required)</action>
<action>Update workflow status in YAML:</action>
- In workflow_status section, update: {{workflow_id}}: skipped
<action>Save updated YAML file</action>
<template-output>success = true</template-output>
<template-output>skipped_workflow = {{workflow_id}}</template-output>
</check>
<!-- ============================================= -->
<!-- Unknown action -->
<!-- ============================================= -->
<check if="action not recognized">
<template-output>success = false</template-output>
<template-output>error = "Unknown action: {{action}}. Valid actions: complete_workflow, skip_workflow"</template-output>
</check>
</check>
<action>Return control to calling workflow with template outputs</action>
</step>
</workflow>
@@ -0,0 +1,126 @@
# BMad Enterprise Method - Brownfield
# Extended enterprise planning for complex brownfield with security/devops/test (30+ stories typically)
method_name: "BMad Enterprise Method"
track: "enterprise-bmad-method"
field_type: "brownfield"
description: "Enterprise-grade planning for complex brownfield additions with extended requirements"
phases:
- prerequisite: true
name: "Documentation"
conditional: "if_undocumented"
note: "NOT a phase - prerequisite for brownfield without docs (nearly mandatory for enterprise)"
workflows:
- id: "document-project"
required: true
agent: "analyst"
command: "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"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
recommended: true
agent: "analyst"
command: "research"
included_by: "user_choice"
note: "Highly recommended - compliance, integration, risk research"
- id: "product-brief"
optional: true
agent: "analyst"
command: "product-brief"
included_by: "user_choice"
note: "Optional for brownfield enterprise"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "prd"
required: true
agent: "pm"
command: "prd"
output: "Enterprise PRD with compliance requirements"
note: "Must address existing system constraints and migration strategy"
- id: "validate-prd"
recommended: true
agent: "pm"
command: "validate-prd"
- id: "create-design"
recommended: true
agent: "ux-designer"
command: "create-design"
note: "Recommended - must integrate with existing UX patterns"
- phase: 2
name: "Solutioning"
required: true
workflows:
- id: "create-architecture"
required: true
agent: "architect"
command: "create-architecture"
output: "Integration architecture with enterprise considerations"
note: "Distills brownfield context + adds security/scalability/compliance design"
- id: "create-epics-and-stories"
required: true
agent: "pm"
command: "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
agent: "tea"
command: "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"
- id: "implementation-readiness"
required: true
agent: "architect"
command: "implementation-readiness"
note: "Critical gate - validates all planning + Epics before touching production system"
- phase: 3
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Enterprise brownfield requires careful phasing and feature flags"
@@ -0,0 +1,114 @@
# BMad Enterprise Method - Greenfield
# Extended enterprise planning with security/devops/test for greenfield (30+ stories typically)
method_name: "Enterprise BMad Method"
track: "enterprise-bmad-method"
field_type: "greenfield"
description: "Complete enterprise-grade planning with security, devops, and test strategy"
phases:
- phase: 0
name: "Discovery (Required)"
required: true
note: "Analysis phase required for enterprise projects"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
recommended: true
agent: "analyst"
command: "research"
included_by: "user_choice"
note: "Highly recommended for enterprise - domain and compliance research"
- id: "product-brief"
recommended: true
agent: "analyst"
command: "product-brief"
included_by: "user_choice"
note: "Recommended for strategic alignment"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "prd"
required: true
agent: "pm"
command: "prd"
output: "Comprehensive Product Requirements Document"
note: "Enterprise-level requirements with compliance considerations"
- id: "validate-prd"
recommended: true
agent: "pm"
command: "validate-prd"
- id: "create-design"
recommended: true
agent: "ux-designer"
command: "create-design"
note: "Highly recommended for enterprise - design system and patterns"
- phase: 2
name: "Solutioning"
required: true
workflows:
- id: "create-architecture"
required: true
agent: "architect"
command: "create-architecture"
output: "Enterprise-grade system architecture"
note: "Includes scalability, multi-tenancy, integration architecture"
- id: "test-design"
required: true
agent: "tea"
command: "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 and threat model"
# note: "Future workflow - optional extended enterprise workflow for security design, auth, compliance"
# - id: "create-devops-strategy"
# optional: true
# agent: "architect"
# command: "create-devops-strategy"
# output: "DevOps pipeline and infrastructure plan"
# note: "Future workflow - optional extended enterprise workflow for CI/CD, deployment, monitoring"
- id: "validate-architecture"
recommended: true
agent: "architect"
command: "validate-architecture"
- id: "create-epics-and-stories"
required: true
agent: "pm"
command: "create-epics-and-stories"
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
- id: "implementation-readiness"
required: true
agent: "architect"
command: "implementation-readiness"
note: "Validates all planning artifacts + Epics + testability align before implementation"
- phase: 3
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Creates sprint plan - enterprise projects may require phased rollout"
@@ -0,0 +1,110 @@
# BMad Method - Brownfield
# Full product + architecture planning for complex brownfield additions (10-50+ stories typically)
method_name: "BMad Method"
track: "bmad-method"
field_type: "brownfield"
description: "Complete product and system design for complex brownfield work"
phases:
- prerequisite: true
name: "Documentation"
conditional: "if_undocumented"
note: "NOT a phase - prerequisite for brownfield without docs"
workflows:
- id: "document-project"
required: true
agent: "analyst"
command: "document-project"
output: "Comprehensive project documentation"
purpose: "Understand existing codebase before planning"
- phase: 0
name: "Discovery (Optional)"
optional: true
note: "User-selected during workflow-init"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
optional: true
agent: "analyst"
command: "research"
included_by: "user_choice"
- id: "product-brief"
optional: true
agent: "analyst"
command: "product-brief"
included_by: "user_choice"
note: "Optional for brownfield, less common than greenfield"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "prd"
required: true
agent: "pm"
command: "prd"
output: "PRD focused on new features/changes"
note: "Must consider existing system constraints"
- id: "validate-prd"
optional: true
agent: "pm"
command: "validate-prd"
- id: "create-design"
conditional: "if_has_ui"
agent: "ux-designer"
command: "create-design"
- phase: 2
name: "Solutioning"
required: true
workflows:
- id: "create-architecture"
recommended: true
agent: "architect"
command: "create-architecture"
output: "Integration architecture - solution design for THIS project"
note: "HIGHLY RECOMMENDED: Distills massive brownfield context into focused solution design. Prevents agent confusion."
- id: "create-epics-and-stories"
required: true
agent: "pm"
command: "create-epics-and-stories"
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
- id: "test-design"
recommended: true
agent: "tea"
command: "test-design"
output: "System-level testability review"
note: "Testability assessment before gate check - auto-detects system-level mode"
- id: "validate-architecture"
optional: true
agent: "architect"
command: "validate-architecture"
- id: "implementation-readiness"
required: true
agent: "architect"
command: "implementation-readiness"
note: "Validates PRD + UX + Architecture + Epics cohesion before implementation"
- phase: 3
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Creates sprint plan with stories"
@@ -0,0 +1,101 @@
# BMad Method - Greenfield
# Full product + architecture planning for greenfield projects (10-50+ stories typically)
method_name: "BMad Method"
track: "bmad-method"
field_type: "greenfield"
description: "Complete product and system design methodology for greenfield projects"
phases:
- phase: 0
name: "Discovery (Optional)"
optional: true
note: "User-selected during workflow-init"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
optional: true
agent: "analyst"
command: "research"
included_by: "user_choice"
note: "Can have multiple research workflows"
- id: "product-brief"
optional: true
agent: "analyst"
command: "product-brief"
included_by: "user_choice"
note: "Recommended for greenfield Method projects"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "prd"
required: true
agent: "pm"
command: "prd"
output: "Product Requirements Document with FRs and NFRs"
- id: "validate-prd"
optional: true
agent: "pm"
command: "validate-prd"
note: "Quality check for PRD completeness"
- id: "create-design"
conditional: "if_has_ui"
agent: "ux-designer"
command: "create-design"
note: "Determined after PRD - user/agent decides if needed"
- phase: 2
name: "Solutioning"
required: true
workflows:
- id: "create-architecture"
required: true
agent: "architect"
command: "create-architecture"
output: "System architecture document"
note: "Complete system design for greenfield projects"
- id: "create-epics-and-stories"
required: true
agent: "pm"
command: "create-epics-and-stories"
note: "Required: Break down PRD into implementable epics and stories with full context (PRD + UX + Architecture)"
- id: "test-design"
recommended: true
agent: "tea"
command: "test-design"
output: "System-level testability review"
note: "Testability assessment before gate check - auto-detects system-level mode"
- id: "validate-architecture"
optional: true
agent: "architect"
command: "validate-architecture"
note: "Quality check for architecture completeness"
- id: "implementation-readiness"
required: true
agent: "architect"
command: "implementation-readiness"
note: "Validates PRD + UX + Architecture + Epics + Testability cohesion before implementation"
- phase: 3
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Creates sprint plan - subsequent work tracked there"
@@ -0,0 +1,58 @@
# BMad Quick Flow - Brownfield
# Fast implementation path for existing codebases (1-15 stories typically)
method_name: "BMad Quick Flow"
track: "quick-flow"
field_type: "brownfield"
description: "Fast tech-spec based implementation for brownfield projects"
phases:
- prerequisite: true
name: "Documentation"
conditional: "if_undocumented"
note: "NOT a phase - prerequisite for brownfield without docs"
workflows:
- id: "document-project"
required: true
agent: "analyst"
command: "document-project"
output: "Comprehensive project documentation"
purpose: "Understand existing codebase before planning"
- phase: 0
name: "Discovery (Optional)"
optional: true
note: "User-selected during workflow-init"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
optional: true
agent: "analyst"
command: "research"
included_by: "user_choice"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "tech-spec"
required: true
agent: "pm"
command: "tech-spec"
output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
note: "Integrates with existing codebase patterns from document-project"
- phase: 2
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Creates sprint plan with all stories"
@@ -0,0 +1,47 @@
# BMad Quick Flow - Greenfield
# Fast implementation path with tech-spec planning (1-15 stories typically)
method_name: "BMad Quick Flow"
track: "quick-flow"
field_type: "greenfield"
description: "Fast tech-spec based implementation for greenfield projects"
phases:
- phase: 0
name: "Discovery (Optional)"
optional: true
note: "User-selected during workflow-init"
workflows:
- id: "brainstorm-project"
optional: true
agent: "analyst"
command: "brainstorm-project"
included_by: "user_choice"
- id: "research"
optional: true
agent: "analyst"
command: "research"
included_by: "user_choice"
note: "Can have multiple research workflows"
- phase: 1
name: "Planning"
required: true
workflows:
- id: "tech-spec"
required: true
agent: "pm"
command: "tech-spec"
output: "Technical Specification with stories (auto-detects epic if 2+ stories)"
note: "Quick Spec Flow - implementation-focused planning"
- phase: 2
name: "Implementation"
required: true
workflows:
- id: "sprint-planning"
required: true
agent: "sm"
command: "sprint-planning"
note: "Creates sprint plan with all stories - subsequent work tracked in sprint plan output, not workflow-status"
@@ -0,0 +1,59 @@
# BMM Project Scale Levels - Source of Truth
# Reference: /.bmad/bmm/README.md lines 77-85
levels:
0:
name: "Level 0"
title: "Single Atomic Change"
stories: "1 story"
description: "Bug fix, tiny feature, one small change"
documentation: "Minimal - tech spec only"
architecture: false
1:
name: "Level 1"
title: "Small Feature"
stories: "1-10 stories"
description: "Small coherent feature, minimal documentation"
documentation: "Tech spec"
architecture: false
2:
name: "Level 2"
title: "Medium Project"
stories: "5-15 stories"
description: "Multiple features, focused PRD"
documentation: "PRD + optional tech spec"
architecture: false
3:
name: "Level 3"
title: "Complex System"
stories: "12-40 stories"
description: "Subsystems, integrations, full architecture"
documentation: "PRD + architecture + JIT tech specs"
architecture: true
4:
name: "Level 4"
title: "Enterprise Scale"
stories: "40+ stories"
description: "Multiple products, enterprise architecture"
documentation: "PRD + architecture + JIT tech specs"
architecture: true
# Quick detection hints for workflow-init
detection_hints:
keywords:
level_0: ["fix", "bug", "typo", "small change", "quick update", "patch"]
level_1: ["simple", "basic", "small feature", "add", "minor"]
level_2: ["dashboard", "several features", "admin panel", "medium"]
level_3: ["platform", "integration", "complex", "system", "architecture"]
level_4: ["enterprise", "multi-tenant", "multiple products", "ecosystem", "scale"]
story_counts:
level_0: [1, 1]
level_1: [1, 10]
level_2: [5, 15]
level_3: [12, 40]
level_4: [40, 999]
@@ -0,0 +1,24 @@
# Workflow Status Template
# This tracks progress through BMM methodology Analysis, Planning, and Solutioning phases.
# Implementation phase is tracked separately in sprint-status.yaml
# STATUS DEFINITIONS:
# ==================
# Initial Status (before completion):
# - required: Must be completed to progress
# - optional: Can be completed but not required
# - recommended: Strongly suggested but not required
# - conditional: Required only if certain conditions met (e.g., if_has_ui)
#
# Completion Status:
# - {file-path}: File created/found (e.g., "docs/product-brief.md")
# - skipped: Optional/conditional workflow that was skipped
generated: "{{generated}}"
project: "{{project_name}}"
project_type: "{{project_type}}"
selected_track: "{{selected_track}}"
field_type: "{{field_type}}"
workflow_path: "{{workflow_path_file}}"
workflow_status: "{{workflow_items}}"
@@ -0,0 +1,28 @@
# Workflow Status - Master Router and Status Tracker
name: workflow-status
description: 'Lightweight status checker - answers "what should I do now?" for any agent. Reads YAML status file for workflow tracking. Use workflow-init for new projects.'
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"
user_skill_level: "{config_source}:user_skill_level"
date: system-generated
# Workflow components
installed_path: "{project-root}/.bmad/bmm/workflows/workflow-status"
instructions: "{installed_path}/instructions.md"
# Template for status file creation (used by workflow-init)
template: "{installed_path}/workflow-status-template.yaml"
# Path definitions for project types
path_files: "{installed_path}/paths/"
# Output configuration - reads existing status
default_output_file: "{output_folder}/bmm-workflow-status.yaml"
standalone: true