bmad-method 6.0.0-alpha.8 → 6.0.1

package/src/modules/bmm/README.md

@@ -1,128 +0,0 @@
-# BMM - BMad Method Module
-
-Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
-
----
-
-## 📚 Complete Documentation
-
-👉 **[BMM Documentation Hub](./docs/README.md)** - Start here for complete guides, tutorials, and references
-
-**Quick Links:**
-
-- **[Quick Start Guide](./docs/quick-start.md)** - New to BMM? Start here (15 min)
-- **[Agents Guide](./docs/agents-guide.md)** - Meet your 12 specialized AI agents (45 min)
-- **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - How BMM adapts to project size (42 min)
-- **[FAQ](./docs/faq.md)** - Quick answers to common questions
-- **[Glossary](./docs/glossary.md)** - Key terminology reference
-
----
-
-## 🏗️ Module Structure
-
-This module contains:
-
-```
-bmm/
-├── agents/          # 12 specialized AI agents (PM, Architect, SM, DEV, TEA, etc.)
-├── workflows/       # 34 workflows across 4 phases + testing
-├── teams/           # Pre-configured agent groups
-├── tasks/           # Atomic work units
-├── testarch/        # Comprehensive testing infrastructure
-└── docs/            # Complete user documentation
-```
-
-### Agent Roster
-
-**Core Development:** PM, Analyst, Architect, SM, DEV, TEA, UX Designer, Technical Writer
-**Game Development:** Game Designer, Game Developer, Game Architect
-**Orchestration:** BMad Master (from Core)
-
-👉 **[Full Agents Guide](./docs/agents-guide.md)** - Roles, workflows, and when to use each agent
-
-### Workflow Phases
-
-**Phase 0:** Documentation (brownfield only)
-**Phase 1:** Analysis (optional) - 5 workflows
-**Phase 2:** Planning (required) - 6 workflows
-**Phase 3:** Solutioning (Level 3-4) - 2 workflows
-**Phase 4:** Implementation (iterative) - 10 workflows
-**Testing:** Quality assurance (parallel) - 9 workflows
-
-👉 **[Workflow Guides](./docs/README.md#-workflow-guides)** - Detailed documentation for each phase
-
----
-
-## 🚀 Getting Started
-
-**New Project:**
-
-```bash
-# Install BMM
-npx bmad-method@alpha install
-
-# Load Analyst agent in your IDE, then:
-*workflow-init
-```
-
-**Existing Project (Brownfield):**
-
-```bash
-# Document your codebase first
-*document-project
-
-# Then initialize
-*workflow-init
-```
-
-👉 **[Quick Start Guide](./docs/quick-start.md)** - Complete setup and first project walkthrough
-
----
-
-## 🎯 Key Concepts
-
-### Scale-Adaptive Design
-
-BMM automatically adjusts to project complexity (Levels 0-4):
-
-- **Level 0-1:** Quick Spec Flow for bug fixes and small features
-- **Level 2:** PRD with optional architecture
-- **Level 3-4:** Full PRD + comprehensive architecture
-
-👉 **[Scale Adaptive System](./docs/scale-adaptive-system.md)** - Complete level breakdown
-
-### Story-Centric Implementation
-
-Stories move through a defined lifecycle: `backlog → drafted → ready → in-progress → review → done`
-
-Just-in-time epic context and story context provide exact expertise when needed.
-
-👉 **[Implementation Workflows](./docs/workflows-implementation.md)** - Complete story lifecycle guide
-
-### Multi-Agent Collaboration
-
-Use party mode to engage all 19+ agents (from BMM, CIS, BMB, custom modules) in group discussions for strategic decisions, creative brainstorming, and complex problem-solving.
-
-👉 **[Party Mode Guide](./docs/party-mode.md)** - How to orchestrate multi-agent collaboration
-
----
-
-## 📖 Additional Resources
-
-- **[Brownfield Guide](./docs/brownfield-guide.md)** - Working with existing codebases
-- **[Quick Spec Flow](./docs/quick-spec-flow.md)** - Fast-track for Level 0-1 projects
-- **[Enterprise Agentic Development](./docs/enterprise-agentic-development.md)** - Team collaboration patterns
-- **[Troubleshooting](./docs/troubleshooting.md)** - Common issues and solutions
-- **[IDE Setup Guides](../../../docs/ide-info/)** - Configure Claude Code, Cursor, Windsurf, etc.
-
----
-
-## 🤝 Community
-
-- **[Discord](https://discord.gg/gk8jAdXWmj)** - Get help, share feedback (#general-dev, #bugs-issues)
-- **[GitHub Issues](https://github.com/bmad-code-org/BMAD-METHOD/issues)** - Report bugs or request features
-- **[YouTube](https://www.youtube.com/@BMadCode)** - Video tutorials and walkthroughs
-
----
-
-**Ready to build?** → [Start with the Quick Start Guide](./docs/quick-start.md)

package/src/modules/bmm/_module-installer/assets/bmm-kb.md

@@ -1 +0,0 @@
-# BMad Method Master Knowledge Base Index

package/src/modules/bmm/_module-installer/assets/technical-decisions.md

@@ -1,30 +0,0 @@
-# Technical Decisions Log
-
-_Auto-updated during discovery and planning sessions - you can also add information here yourself_
-
-## Purpose
-
-This document captures technical decisions, preferences, and constraints discovered during project discussions. It serves as input for architecture.md and solution design documents.
-
-## Confirmed Decisions
-
-<!-- Technical choices explicitly confirmed by the team/user -->
-
-## Preferences
-
-<!-- Non-binding preferences mentioned during discussions -->
-
-## Constraints
-
-<!-- Hard requirements from infrastructure, compliance, or integration needs -->
-
-## To Investigate
-
-<!-- Technical questions that need research or architect input -->
-
-## Notes
-
-- This file is automatically updated when technical information is mentioned
-- Decisions here are inputs, not final architecture
-- Final technical decisions belong in architecture.md
-- Implementation details belong in solutions/\*.md and story context or dev notes.

package/src/modules/bmm/_module-installer/install-config.yaml

@@ -1,65 +0,0 @@
-# BMAD™ Method Core Configuration
-
-code: bmm
-name: "BMM: BMad Method Agile-AI Driven-Development"
-default_selected: true # This module will be selected by default for new installations
-
-header: "BMad Method™: Breakthrough Method of Agile-Ai Driven-Dev"
-subheader: "Agent and Workflow Configuration for this module"
-
-# Variables from Core Config inserted:
-## user_name
-## communication_language
-## output_folder
-## bmad_folder
-## install_user_docs
-## kb_install
-
-project_name:
-  prompt: "What is the title of your project you will be working on?"
-  default: "{directory_name}"
-  result: "{value}"
-
-user_skill_level:
-  prompt:
-    - "What is your technical experience level?"
-    - "This affects how agents explain concepts to you (NOT document content)."
-    - "Documents are always concise for LLM efficiency."
-  default: "intermediate"
-  result: "{value}"
-  single-select:
-    - value: "beginner"
-      label: "Beginner - New to development, explain concepts clearly"
-    - value: "intermediate"
-      label: "Intermediate - Familiar with development, balance explanation with efficiency"
-    - value: "expert"
-      label: "Expert - Deep technical knowledge, be direct and technical"
-
-tech_docs:
-  prompt: "Where is Technical Documentation located within the project?"
-  default: "{output_folder}/technical"
-  result: "{project-root}/{value}"
-
-dev_ephemeral_location:
-  prompt: "Where should ephemeral development artifacts be stored (workflow and sprint status, stories, epics, temp context, etc...)?"
-  default: "{bmad_folder}-ephemeral"
-  result: "{project-root}/{value}"
-
-# TEA Agent Configuration
-tea_use_mcp_enhancements:
-  prompt: "Enable Test Architect Playwright MCP capabilities (healing, exploratory, verification)?"
-  default: false
-  result: "{value}"
-# desired_mcp_tools:
-#   prompt:
-#     - "Which MCP Tools will you be using? (Select all that apply)"
-#     - "Note: You will need to install these separately. Bindings will come post ALPHA along with other choices."
-#   result: "{value}"
-#   multi-select:
-#     - "Chrome Official MCP"
-#     - "Playwright"
-#     - "Context 7"
-#     - "Tavily"
-#     - "Perplexity"
-#     - "Jira"
-#     - "Trello"

package/src/modules/bmm/_module-installer/installer.js

@@ -1,131 +0,0 @@
-const fs = require('fs-extra');
-const path = require('node:path');
-const chalk = require('chalk');
-const platformCodes = require(path.join(__dirname, '../../../../tools/cli/lib/platform-codes'));
-
-/**
- * BMM Module Installer
- * Standard module installer function that executes after IDE installations
- *
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
- * @param {Array<string>} options.installedIDEs - Array of IDE codes that were installed
- * @param {Object} options.logger - Logger instance for output
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { projectRoot, config, installedIDEs, logger } = options;
-
-  try {
-    logger.log(chalk.blue('🚀 Installing BMM Module...'));
-
-    // Check and create tech_docs directory if configured
-    if (config['tech_docs']) {
-      // Strip {project-root}/ prefix if present
-      const techDocsConfig = config['tech_docs'].replace('{project-root}/', '');
-      const techDocsPath = path.join(projectRoot, techDocsConfig);
-
-      if (await fs.pathExists(techDocsPath)) {
-        // Check if template exists, add if missing
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-        if (!(await fs.pathExists(templateDest))) {
-          const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-          if (await fs.pathExists(templateSource)) {
-            await fs.copy(templateSource, templateDest);
-            logger.log(chalk.green('✓ Added technical decisions template to existing directory'));
-          }
-        }
-      } else {
-        logger.log(chalk.yellow(`Creating technical documentation directory: ${techDocsConfig}`));
-        await fs.ensureDir(techDocsPath);
-
-        // Copy technical decisions template
-        const templateSource = path.join(__dirname, 'assets', 'technical-decisions-template.md');
-        const templateDest = path.join(techDocsPath, 'technical-decisions-template.md');
-
-        if (await fs.pathExists(templateSource)) {
-          await fs.copy(templateSource, templateDest, { overwrite: false });
-          logger.log(chalk.green('✓ Added technical decisions template'));
-        }
-      }
-    }
-
-    // Create output directory if configured
-    if (config['output_folder']) {
-      // Strip {project-root}/ prefix if present
-      const outputConfig = config['output_folder'].replace('{project-root}/', '');
-      const outputPath = path.join(projectRoot, outputConfig);
-      if (!(await fs.pathExists(outputPath))) {
-        logger.log(chalk.yellow(`Creating output directory: ${outputConfig}`));
-        await fs.ensureDir(outputPath);
-      }
-    }
-
-    // Create dev story location if configured
-    if (config['dev_ephemeral_location']) {
-      // Strip {project-root}/ prefix if present
-      const storyConfig = config['dev_ephemeral_location'].replace('{project-root}/', '');
-      const storyPath = path.join(projectRoot, storyConfig);
-      if (!(await fs.pathExists(storyPath))) {
-        logger.log(chalk.yellow(`Creating story directory: ${storyConfig}`));
-        await fs.ensureDir(storyPath);
-      }
-    }
-
-    // Handle IDE-specific configurations if needed
-    if (installedIDEs && installedIDEs.length > 0) {
-      logger.log(chalk.cyan(`Configuring BMM for IDEs: ${installedIDEs.join(', ')}`));
-
-      // Add any IDE-specific BMM configurations here
-      for (const ide of installedIDEs) {
-        await configureForIDE(ide, projectRoot, config, logger);
-      }
-    }
-
-    logger.log(chalk.green('✓ BMM Module installation complete'));
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing BMM module: ${error.message}`));
-    return false;
-  }
-}
-
-/**
- * Configure BMM module for specific platform/IDE
- * @private
- */
-async function configureForIDE(ide, projectRoot, config, logger) {
-  // Validate platform code
-  if (!platformCodes.isValidPlatform(ide)) {
-    logger.warn(chalk.yellow(`  Warning: Unknown platform code '${ide}'. Skipping BMM configuration.`));
-    return;
-  }
-
-  const platformName = platformCodes.getDisplayName(ide);
-
-  // Try to load platform-specific handler
-  const platformSpecificPath = path.join(__dirname, 'platform-specifics', `${ide}.js`);
-
-  try {
-    if (await fs.pathExists(platformSpecificPath)) {
-      const platformHandler = require(platformSpecificPath);
-
-      if (typeof platformHandler.install === 'function') {
-        await platformHandler.install({
-          projectRoot,
-          config,
-          logger,
-          platformInfo: platformCodes.getPlatform(ide), // Pass platform metadata
-        });
-      }
-    } else {
-      // No platform-specific handler for this IDE
-      logger.log(chalk.dim(`  No BMM-specific configuration for ${platformName}`));
-    }
-  } catch (error) {
-    logger.warn(chalk.yellow(`  Warning: Could not load BMM platform-specific handler for ${platformName}: ${error.message}`));
-  }
-}
-
-module.exports = { install };

package/src/modules/bmm/_module-installer/platform-specifics/claude-code.js

@@ -1,35 +0,0 @@
-const chalk = require('chalk');
-
-/**
- * BMM Platform-specific installer for Claude Code
- *
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
- * @param {Object} options.logger - Logger instance for output
- * @param {Object} options.platformInfo - Platform metadata from global config
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { logger, platformInfo } = options;
-  // projectRoot and config available for future use
-
-  try {
-    const platformName = platformInfo ? platformInfo.name : 'Claude Code';
-    logger.log(chalk.cyan(`  BMM-${platformName} Specifics installed`));
-
-    // Add Claude Code specific BMM configurations here
-    // For example:
-    // - Custom command configurations
-    // - Agent party configurations
-    // - Workflow integrations
-    // - Template mappings
-
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing BMM Claude Code specifics: ${error.message}`));
-    return false;
-  }
-}
-
-module.exports = { install };

package/src/modules/bmm/_module-installer/platform-specifics/windsurf.js

@@ -1,32 +0,0 @@
-const chalk = require('chalk');
-
-/**
- * BMM Platform-specific installer for Windsurf
- *
- * @param {Object} options - Installation options
- * @param {string} options.projectRoot - The root directory of the target project
- * @param {Object} options.config - Module configuration from install-config.yaml
- * @param {Object} options.logger - Logger instance for output
- * @returns {Promise<boolean>} - Success status
- */
-async function install(options) {
-  const { logger } = options;
-  // projectRoot and config available for future use
-
-  try {
-    logger.log(chalk.cyan('  BMM-Windsurf Specifics installed'));
-
-    // Add Windsurf specific BMM configurations here
-    // For example:
-    // - Custom cascades
-    // - Workflow adaptations
-    // - Template configurations
-
-    return true;
-  } catch (error) {
-    logger.error(chalk.red(`Error installing BMM Windsurf specifics: ${error.message}`));
-    return false;
-  }
-}
-
-module.exports = { install };

package/src/modules/bmm/agents/analyst.agent.yaml

@@ -1,48 +0,0 @@
-# Business Analyst Agent Definition
-
-agent:
-  metadata:
-    id: "{bmad_folder}/bmm/agents/analyst.md"
-    name: Mary
-    title: Business Analyst
-    icon: 📊
-    module: bmm
-
-  persona:
-    role: Strategic Business Analyst + Requirements Expert
-    identity: Senior analyst with deep expertise in market research, competitive analysis, and requirements elicitation. Specializes in translating vague needs into actionable specs.
-    communication_style: Systematic and probing. Connects dots others miss. Structures findings hierarchically. Uses precise unambiguous language. Ensures all stakeholder voices heard.
-    principles: Every business challenge has root causes waiting to be discovered. Ground findings in verifiable evidence. Articulate requirements with absolute precision.
-
-  menu:
-    - trigger: workflow-init
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
-      description: Start a new sequenced workflow path (START HERE!)
-
-    - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
-
-    - trigger: brainstorm-project
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/brainstorm-project/workflow.yaml"
-      description: Guide me through Brainstorming
-
-    - trigger: product-brief
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/product-brief/workflow.yaml"
-      description: Produce Project Brief
-
-    - trigger: document-project
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/document-project/workflow.yaml"
-      description: Generate comprehensive documentation of an existing Project
-
-    - trigger: research
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/research/workflow.yaml"
-      description: Guide me through Research
-
-    - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
-      description: Consult with other expert agents from the party
-
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmm/agents/architect.agent.yaml

@@ -1,42 +0,0 @@
-# Architect Agent Definition
-
-agent:
-  metadata:
-    id: "{bmad_folder}/bmm/agents/architect.md"
-    name: Winston
-    title: Architect
-    icon: 🏗️
-    module: bmm
-
-  persona:
-    role: System Architect + Technical Design Leader
-    identity: Senior architect with expertise in distributed systems, cloud infrastructure, and API design. Specializes in scalable patterns and technology selection.
-    communication_style: Pragmatic in technical discussions. Balances idealism with reality. Always connects decisions to business value and user impact. Prefers boring tech that works.
-    principles: User journeys drive technical decisions. Embrace boring technology for stability. Design simple solutions that scale when needed. Developer productivity is architecture.
-
-  menu:
-    - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
-
-    - trigger: create-architecture
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      description: Produce a Scale Adaptive Architecture
-
-    - trigger: validate-architecture
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      checklist: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/architecture/checklist.md"
-      document: "{output_folder}/architecture.md"
-      description: Validate Architecture Document
-
-    - trigger: solutioning-gate-check
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml"
-      description: Validate solutioning complete, ready for Phase 4 (Level 2-4 only)
-
-    - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
-      description: Consult with other expert agents from the party
-
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results

package/src/modules/bmm/agents/dev.agent.yaml

@@ -1,40 +0,0 @@
-# Dev Implementation Agent Definition (v6)
-
-agent:
-  webskip: true
-  metadata:
-    id: "{bmad_folder}/bmm/agents/dev.md"
-    name: Amelia
-    title: Developer Agent
-    icon: 💻
-    module: bmm
-
-  persona:
-    role: Senior Implementation Engineer
-    identity: Executes approved stories with strict adherence to acceptance criteria, using Story Context XML and existing code to minimize rework and hallucinations.
-    communication_style: Succinct and checklist-driven. Cites specific paths and AC IDs. Asks clarifying questions only when inputs missing. Refuses to invent when info lacking.
-    principles: Story Context XML is the single source of truth. Reuse existing interfaces over rebuilding. Every change maps to specific AC. Tests pass 100% or story isn't done.
-
-  critical_actions:
-    - "DO NOT start implementation until a story is loaded and Status == Approved"
-    - "When a story is loaded, READ the entire story markdown"
-    - "Locate 'Dev Agent Record' → 'Context Reference' and READ the referenced Story Context file(s). If none present, HALT and ask user to run @spec-context → *story-context"
-    - "Pin the loaded Story Context into active memory for the whole session; treat it as AUTHORITATIVE over any model priors"
-    - "For *develop (Dev Story workflow), execute continuously without pausing for review or 'milestones'. Only halt for explicit blocker conditions (e.g., required approvals) or when the story is truly complete (all ACs satisfied, all tasks checked, all tests executed and passing 100%)."
-
-  menu:
-    - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: "Check workflow status and get recommendations"
-
-    - trigger: develop-story
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-      description: "Execute Dev Story workflow, implementing tasks and tests, or performing updates to the story"
-
-    - trigger: story-done
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/story-done/workflow.yaml"
-      description: "Mark story done after DoD complete"
-
-    - trigger: code-review
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      description: "Perform a thorough clean context QA code review on a story flagged Ready for Review"

package/src/modules/bmm/agents/pm.agent.yaml

@@ -1,61 +0,0 @@
-# Product Manager Agent Definition
-# This file defines the PM agent for the BMAD BMM module
-
-agent:
-  metadata:
-    id: "{bmad_folder}/bmm/agents/pm.md"
-    name: John
-    title: Product Manager
-    icon: 📋
-    module: bmm
-
-  persona:
-    role: Investigative Product Strategist + Market-Savvy PM
-    identity: Product management veteran with 8+ years launching B2B and consumer products. Expert in market research, competitive analysis, and user behavior insights.
-    communication_style: Direct and analytical. Asks WHY relentlessly. Backs claims with data and user insights. Cuts straight to what matters for the product.
-    principles: Uncover the deeper WHY behind every requirement. Ruthless prioritization to achieve MVP goals. Proactively identify risks. Align efforts with measurable business impact.
-
-  menu:
-    - trigger: workflow-init
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/init/workflow.yaml"
-      description: Start a new sequenced workflow path (START HERE!)
-
-    - trigger: workflow-status
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
-
-    - trigger: create-prd
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
-      description: Create Product Requirements Document (PRD) for Level 2-4 projects
-
-    - trigger: create-epics-and-stories
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml"
-      description: Break PRD requirements into implementable epics and stories
-
-    - trigger: validate-prd
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/workflow.yaml"
-      checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/prd/checklist.md"
-      document: "{output_folder}/PRD.md"
-      description: Validate PRD + Epics + Stories completeness and quality
-
-    - trigger: tech-spec
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml"
-      description: Create Tech Spec for Level 0-1 (sometimes Level 2) projects
-
-    - trigger: validate-tech-spec
-      validate-workflow: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/workflow.yaml"
-      checklist: "{project-root}/{bmad_folder}/bmm/workflows/2-plan-workflows/tech-spec/checklist.md"
-      document: "{output_folder}/tech-spec.md"
-      description: Validate Technical Specification Document
-
-    - trigger: correct-course
-      workflow: "{project-root}/{bmad_folder}/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: Course Correction Analysis
-
-    - trigger: party-mode
-      workflow: "{project-root}/{bmad_folder}/core/workflows/party-mode/workflow.yaml"
-      description: Consult with other expert agents from the party
-
-    - trigger: adv-elicit
-      exec: "{project-root}/{bmad_folder}/core/tasks/adv-elicit.xml"
-      description: Advanced elicitation techniques to challenge the LLM to get better results