feat: add documentation website with Docusaurus build pipeline (#1177)

* feat: add documentation website with Docusaurus build pipeline

* feat(docs): add AI discovery meta tags for llms.txt files

- Add global headTags with ai-terms, llms, llms-full meta tags
- Update landing page link to clarify AI context purpose

* fix(docs): restore accidentally deleted faq.md and glossary.md

Files were removed in 12dd97fe during path restructuring.

* fix(docs): update broken project-readme links to GitHub URL

* feat(schema): add compound trigger format validation

.github/workflows/docs.yaml

@@ -0,0 +1,72 @@
+name: Deploy Documentation
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - "docs/**"
+      - "src/modules/*/docs/**"
+      - "website/**"
+      - "tools/build-docs.js"
+      - ".github/workflows/docs.yaml"
+  workflow_dispatch:
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: false
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: "npm"
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Determine site URL
+        id: site-url
+        run: |
+          if [ "${{ github.repository }}" = "bmad-code-org/BMAD-METHOD" ]; then
+            echo "url=https://bmad-code-org.github.io/BMAD-METHOD" >> $GITHUB_OUTPUT
+          else
+            OWNER="${{ github.repository_owner }}"
+            REPO="${{ github.event.repository.name }}"
+            echo "url=https://${OWNER}.github.io/${REPO}" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Build documentation
+        env:
+          SITE_URL: ${{ steps.site-url.outputs.url }}
+        run: npm run docs:build
+
+      - name: Upload artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: build/site
+
+  deploy:
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    needs: build
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4

.gitignore

@@ -74,4 +74,8 @@ _bmad
 .kiro/
 .roo
 
-bmad-custom-src/
+bmad-custom-src/
+
+# Docusaurus / Documentation Build
+.docusaurus/
+build/

CONTRIBUTING.md

@@ -236,10 +236,8 @@ Each commit should represent one logical change:
 3. **Don't paste code in issues** - create a proper PR instead
 4. **Don't submit your whole project** - contribute specific improvements
 
-## Code Style
+## Prompt & Agent Guidelines
 
-- Follow the existing code style and conventions
-- Write clear comments for complex logic
 - Keep dev agents lean - they need context for coding, not documentation
 - Web/planning agents can be larger with more complex tasks
 - Everything is natural language (markdown) - no code in core framework

README.md

@@ -26,8 +26,8 @@ The completely revamped **BMAD V6 installer** now includes built-in support for
 
 - [**Custom Content Overview**](./docs/custom-content.md) - Discover all supported content types
 - [**Installation Guide**](./docs/custom-content-installation.md) - Learn to create and install custom content
-- [**Detail Content Docs**](./src/modules/bmb/docs/README.md) - Reference details for agents, modules, workflows and the bmad builder
-- [**2 Very simple Custom Modules of questionable quality**](./docs/sample-custom-modules/README.md) - if you want to download and try to install a custom shared module, get an idea of how to bundle and share your own, or create your own personal agents, workflows and modules.
+- [**Detail Content Docs**](./src/modules/bmb/docs/index.md) - Reference details for agents, modules, workflows and the bmad builder
+- [**2 Very simple Custom Modules of questionable quality**](./samples/sample-custom-modules/README.md) - if you want to download and try to install a custom shared module, get an idea of how to bundle and share your own, or create your own personal agents, workflows and modules.
 
 </div>
 
@@ -142,18 +142,17 @@ Each agent brings deep expertise and can be customized to match your team's styl
   - 12 specialized agents
   - 34 workflows across 4 phases
   - Scale-adaptive planning
-  - [→ Documentation Hub](./src/modules/bmm/docs/README.md)
+  - [→ Documentation Hub](./src/modules/bmm/docs/index.md)
 
 - **BMad Builder (BMB)** - Create custom agents and workflows
   - Build anything from simple agents to complex modules
   - Create domain-specific solutions (legal, medical, finance, education)
-  - [→ Builder Guide](src/modules/bmb/docs/README.md) marketplace
-  - [→ Builder Guide](./src/modules/bmb/README.md)
+  - [→ Builder Guide](./src/modules/bmb/docs/index.md)
 
 - **Creative Intelligence Suite (CIS)** - Innovation & problem-solving
   - Brainstorming, design thinking, storytelling
   - 5 creative facilitation workflows
-  - [→ Creative Workflows](src/modules/cis/docs/README.md)
+  - [→ Creative Workflows](./src/modules/cis/docs/index.md)
 
 ### Key Features
 
@@ -168,7 +167,7 @@ Each agent brings deep expertise and can be customized to match your team's styl
 ### Quick Links
 
 - **[Quick Start Guide](./src/modules/bmm/docs/quick-start.md)** - 15-minute introduction
-- **[Complete BMM Documentation](./src/modules/bmm/docs/README.md)** - All guides and references
+- **[Complete BMM Documentation](./src/modules/bmm/docs/index.md)** - All guides and references
 - **[Agent Customization](./docs/agent-customization-guide.md)** - Personalize your agents
 - **[All Documentation](./docs/index.md)** - Complete documentation index
 

docs/agent-customization-guide.md

@@ -203,6 +203,6 @@ memories:
 
 ## Next Steps
 
-- **[BMM Agents Guide](../src/modules/bmm/docs/agents-guide.md)** - Learn about the BMad Method agents
-- **[BMB Create Agent Workflow](../src/modules/bmb/workflows/create-agent/README.md)** - Build completely custom agents
-- **[BMM Complete Documentation](../src/modules/bmm/docs/README.md)** - Full BMad Method reference
+- **[BMM Agents Guide](./modules/bmm/agents-guide)** - Learn about the BMad Method agents
+- **[BMB Create Agent Workflow](./modules/bmb/agents/index)** - Build completely custom agents
+- **[BMM Complete Documentation](./modules/bmm/index)** - Full BMad Method reference

docs/custom-content-installation.md

@@ -4,7 +4,7 @@ This guide explains how to create and install custom BMAD content including agen
 
 For detailed information about the different types of custom content available, see [Custom Content](./custom-content.md).
 
-If you download either of the folders within the [Sample Custom Modules](./sample-custom-modules/readme.md) folder
+You can find example custom modules in the `samples/sample-custom-modules/` folder of the repository. Download either of the sample folders to try them out.
 
 ## Content Types Overview
 

docs/document-sharding-guide.md

@@ -441,8 +441,8 @@ input_file_patterns:
 ## Related Documentation
 
 - [shard-doc Tool](../src/core/tools/shard-doc.xml) - Tool implementation
-- [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Workflow overview
-- [Workflow Creation Guide](../src/modules/bmb/workflows/create-workflow/workflow-creation-guide.md) - Custom workflow patterns
+- [BMM Workflows Guide](./modules/bmm/index.md#-workflow-guides) - Workflow overview
+- [Workflow Creation Guide](./modules/bmb/workflows/index) - Custom workflow patterns
 
 ---
 

docs/getting-started/installation.md

@@ -0,0 +1,76 @@
+# Installation
+
+Get BMAD Method running in your project in under 2 minutes.
+
+## Quick Install
+
+```bash
+npx bmad-method@alpha install
+```
+
+This interactive installer will:
+
+1. Detect your IDE (Claude Code, Cursor, VS Code, etc.)
+2. Let you choose which modules to install
+3. Configure agents and workflows for your project
+
+## Requirements
+
+- **Node.js** 18+ (for the installer)
+- **Git** (recommended for version control)
+- An **AI-powered IDE** or access to Claude/ChatGPT/Gemini
+
+## Module Options
+
+During installation, you'll choose which modules to install:
+
+| Module   | Description      | Best For                                 |
+| -------- | ---------------- | ---------------------------------------- |
+| **BMM**  | BMAD Method Core | Software development projects            |
+| **BMGD** | Game Development | Game projects with specialized workflows |
+| **BMB**  | Builder          | Creating custom agents and workflows     |
+
+## Post-Installation
+
+After installation, your project will have:
+
+```
+your-project/
+├── _bmad/              # BMAD configuration and agents
+│   ├── bmm/            # Method module (if installed)
+│   ├── bmgd/           # Game dev module (if installed)
+│   └── config.yaml     # Your project configuration
+├── .claude/            # IDE-specific setup (varies by IDE)
+└── ... your code
+```
+
+## Next Steps
+
+1. **Read the [Quick Start Guide](../modules/bmm/quick-start.md)** to build your first feature
+2. **Check your [IDE Guide](../ide-info/index.md)** for IDE-specific tips
+3. **Explore [Workflows](../modules/bmm/workflows-planning.md)** to understand the methodology
+
+## Alternative: Web Bundles
+
+Don't want to install? Use BMAD agents directly in:
+
+- **Claude Projects** - Upload the web bundle
+- **ChatGPT** - Use custom GPT bundles
+- **Gemini** - Import agent prompts
+
+See the [Web Bundles Guide](../web-bundles-gemini-gpt-guide.md) for details.
+
+## Troubleshooting
+
+### Common Issues
+
+**"Command not found: npx"**
+: Install Node.js 18+ from [nodejs.org](https://nodejs.org)
+
+**"Permission denied"**
+: Run with appropriate permissions or check your npm configuration
+
+**IDE not detected**
+: The installer will prompt you to select your IDE manually
+
+For more help, see [Troubleshooting](../modules/bmm/troubleshooting.md) or join our [Discord](https://discord.gg/bmad).

docs/ide-info/index.md

@@ -0,0 +1,24 @@
+# IDE Guides
+
+BMAD Method works with any AI-powered development environment. Choose your IDE below for specific setup instructions and tips.
+
+## All Supported IDEs
+
+| IDE                                 | Type              | BMAD Support          |
+| ----------------------------------- | ----------------- | --------------------- |
+| [Claude Code](claude-code.md)       | CLI/Terminal      | Native slash commands |
+| [Cursor](cursor.md)                 | Desktop Editor    | Full agent support    |
+| [VS Code / Windsurf](windsurf.md)   | Desktop Editor    | Extension-based       |
+| [Cline](cline.md)                   | VS Code Extension | Full support          |
+| [GitHub Copilot](github-copilot.md) | Extension         | Workspace agents      |
+| [Augment](auggie.md)                | Extension         | Agent loading         |
+| [Codex](codex.md)                   | CLI               | Prompt injection      |
+| [Gemini](gemini.md)                 | Web/API           | Web bundles           |
+| [Roo](roo.md)                       | VS Code Extension | Mode support          |
+| [Kilo](kilo.md)                     | Extension         | Basic support         |
+| [OpenCode](opencode.md)             | Open Source       | Full support          |
+| [Qwen](qwen.md)                     | Web/API           | Web bundles           |
+| [Trae](trae.md)                     | Extension         | Basic support         |
+| [Crush](crush.md)                   | Desktop           | Agent support         |
+| [iFlow](iflow.md)                   | Extension         | Prompt loading        |
+| [Rovo Dev](rovo-dev.md)             | Atlassian         | Integration           |

docs/ide-info/rovo-dev.md

@@ -1,388 +1,22 @@
-# Rovo Dev IDE Integration
+# BMAD Method - Rovo Dev Instructions
 
-This document describes how BMAD-METHOD integrates with [Atlassian Rovo Dev](https://www.atlassian.com/rovo-dev), an AI-powered software development assistant.
+## Activating Agents
 
-## Overview
+BMAD agents are installed as subagents in `.rovodev/subagents/`.
 
-Rovo Dev is designed to integrate deeply with developer workflows and organizational knowledge bases. When you install BMAD-METHOD in a Rovo Dev project, it automatically installs BMAD agents, workflows, tasks, and tools just like it does for other IDEs (Cursor, VS Code, etc.).
+### How to Use
 
-BMAD-METHOD provides:
+1. **Open Project**: Subagents auto-load when project opens
+2. **Invoke Agent**: Type `@` and select agent (e.g., `@bmad-bmm-dev`, `@bmad-bmm-architect`)
+3. **Reference Files**: Check `.rovodev/workflows/` and `.rovodev/references/`
 
-- **Agents**: Specialized subagents for various development tasks
-- **Workflows**: Multi-step workflow guides and coordinators
-- **Tasks & Tools**: Reference documentation for BMAD tasks and tools
+### Directory Structure
 
-### What are Rovo Dev Subagents?
+- `.rovodev/subagents/` - BMAD agents
+- `.rovodev/workflows/` - Workflow guides
+- `.rovodev/references/` - Tasks and tools
 
-Subagents are specialized agents that Rovo Dev can delegate tasks to. They are defined as Markdown files with YAML frontmatter stored in the `.rovodev/subagents/` directory. Rovo Dev automatically discovers these files and makes them available through the `@subagent-name` syntax.
+### Notes
 
-## Installation and Setup
-
-### Automatic Installation
-
-When you run the BMAD-METHOD installer and select Rovo Dev as your IDE:
-
-```bash
-bmad install
-```
-
-The installer will:
-
-1. Create a `.rovodev/subagents/` directory in your project (if it doesn't exist)
-2. Convert BMAD agents into Rovo Dev subagent format
-3. Write subagent files with the naming pattern: `bmad-<module>-<agent-name>.md`
-
-### File Structure
-
-After installation, your project will have:
-
-```
-project-root/
-├── .rovodev/
-│   ├── subagents/
-│   │   ├── bmad-core-code-reviewer.md
-│   │   ├── bmad-bmm-pm.md
-│   │   ├── bmad-bmm-dev.md
-│   │   └── ... (more agents from selected modules)
-│   ├── workflows/
-│   │   ├── bmad-brainstorming.md
-│   │   ├── bmad-prd-creation.md
-│   │   └── ... (workflow guides)
-│   ├── references/
-│   │   ├── bmad-task-core-code-review.md
-│   │   ├── bmad-tool-core-analysis.md
-│   │   └── ... (task/tool references)
-│   ├── config.yml          (Rovo Dev configuration)
-│   ├── prompts.yml         (Optional: reusable prompts)
-│   └── ...
-├── _bmad/                  (BMAD installation directory)
-└── ...
-```
-
-**Directory Structure Explanation:**
-
-- **subagents/**: Agents discovered and used by Rovo Dev with `@agent-name` syntax
-- **workflows/**: Multi-step workflow guides and instructions
-- **references/**: Documentation for available tasks and tools in BMAD
-
-## Subagent File Format
-
-BMAD agents are converted to Rovo Dev subagent format, which uses Markdown with YAML frontmatter:
-
-### Basic Structure
-
-```markdown
----
-name: bmad-module-agent-name
-description: One sentence description of what this agent does
-tools:
-  - bash
-  - open_files
-  - grep
-  - expand_code_chunks
-model: anthropic.claude-3-5-sonnet-20241022-v2:0 # Optional
-load_memory: true # Optional
----
-
-You are a specialized agent for [specific task].
-
-## Your Role
-
-Describe the agent's role and responsibilities...
-
-## Key Instructions
-
-1. First instruction
-2. Second instruction
-3. Third instruction
-
-## When to Use This Agent
-
-Explain when and how to use this agent...
-```
-
-### YAML Frontmatter Fields
-
-| Field         | Type    | Required | Description                                                                                                                           |
-| ------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| `name`        | string  | Yes      | Unique identifier for the subagent (kebab-case, no spaces)                                                                            |
-| `description` | string  | Yes      | One-line description of the subagent's purpose                                                                                        |
-| `tools`       | array   | No       | List of tools the subagent can use. If not specified, uses parent agent's tools                                                       |
-| `model`       | string  | No       | Specific LLM model for this subagent (e.g., `anthropic.claude-3-5-sonnet-20241022-v2:0`). If not specified, uses parent agent's model |
-| `load_memory` | boolean | No       | Whether to load default memory files (AGENTS.md, AGENTS.local.md). Defaults to `true`                                                 |
-
-### System Prompt
-
-The content after the closing `---` is the subagent's system prompt. This defines:
-
-- The agent's persona and role
-- Its capabilities and constraints
-- Step-by-step instructions for task execution
-- Examples of expected behavior
-
-## Using BMAD Components in Rovo Dev
-
-### Invoking a Subagent (Agent)
-
-In Rovo Dev, you can invoke a BMAD agent as a subagent using the `@` syntax:
-
-```
-@bmad-core-code-reviewer Please review this PR for potential issues
-@bmad-bmm-pm Help plan this feature release
-@bmad-bmm-dev Implement this feature
-```
-
-### Accessing Workflows
-
-Workflow guides are available in `.rovodev/workflows/` directory:
-
-```
-@bmad-core-code-reviewer Use the brainstorming workflow from .rovodev/workflows/bmad-brainstorming.md
-```
-
-Workflow files contain step-by-step instructions and can be referenced or copied into Rovo Dev for collaborative workflow execution.
-
-### Accessing Tasks and Tools
-
-Task and tool documentation is available in `.rovodev/references/` directory. These provide:
-
-- Task execution instructions
-- Tool capabilities and usage
-- Integration examples
-- Parameter documentation
-
-### Example Usage Scenarios
-
-#### Code Review
-
-```
-@bmad-core-code-reviewer Review the changes in src/components/Button.tsx
-for best practices, performance, and potential bugs
-```
-
-#### Documentation
-
-```
-@bmad-core-documentation-writer Generate API documentation for the new
-user authentication module
-```
-
-#### Feature Design
-
-```
-@bmad-module-feature-designer Design a solution for implementing
-dark mode support across the application
-```
-
-## Customizing BMAD Subagents
-
-You can customize BMAD subagents after installation by editing their files directly in `.rovodev/subagents/`.
-
-### Example: Adding Tool Restrictions
-
-By default, BMAD subagents inherit tools from the parent Rovo Dev agent. You can restrict which tools a specific subagent can use:
-
-```yaml
----
-name: bmad-core-code-reviewer
-description: Reviews code and suggests improvements
-tools:
-  - open_files
-  - expand_code_chunks
-  - grep
----
-```
-
-### Example: Using a Specific Model
-
-Some agents might benefit from using a different model. You can specify this:
-
-```yaml
----
-name: bmad-core-documentation-writer
-description: Writes clear and comprehensive documentation
-model: anthropic.claude-3-5-sonnet-20241022-v2:0
----
-```
-
-### Example: Enhancing the System Prompt
-
-You can add additional context to a subagent's system prompt:
-
-```markdown
----
-name: bmad-core-code-reviewer
-description: Reviews code and suggests improvements
----
-
-You are a specialized code review agent for our project.
-
-## Project Context
-
-Our codebase uses:
-
-- React 18 for frontend
-- Node.js 18+ for backend
-- TypeScript for type safety
-- Jest for testing
-
-## Review Checklist
-
-1. Type safety and TypeScript correctness
-2. React best practices and hooks usage
-3. Performance considerations
-4. Test coverage
-5. Documentation and comments
-
-...rest of original system prompt...
-```
-
-## Memory and Context
-
-By default, BMAD subagents have `load_memory: true`, which means they will load memory files from your project:
-
-- **Project-level**: `.rovodev/AGENTS.md` and `.rovodev/.agent.md`
-- **User-level**: `~/.rovodev/AGENTS.md` (global memory across all projects)
-
-These files can contain:
-
-- Project guidelines and conventions
-- Common patterns and best practices
-- Recent decisions and context
-- Custom instructions for all agents
-
-### Creating Project Memory
-
-Create `.rovodev/AGENTS.md` in your project:
-
-```markdown
-# Project Guidelines
-
-## Code Style
-
-- Use 2-space indentation
-- Use camelCase for variables
-- Use PascalCase for classes
-
-## Architecture
-
-- Follow modular component structure
-- Use dependency injection for services
-- Implement proper error handling
-
-## Testing Requirements
-
-- Minimum 80% code coverage
-- Write tests before implementation
-- Use descriptive test names
-```
-
-## Troubleshooting
-
-### Subagents Not Appearing in Rovo Dev
-
-1. **Verify files exist**: Check that `.rovodev/subagents/bmad-*.md` files are present
-2. **Check Rovo Dev is reloaded**: Rovo Dev may cache agent definitions. Restart Rovo Dev or reload the project
-3. **Verify file format**: Ensure files have proper YAML frontmatter (between `---` markers)
-4. **Check file permissions**: Ensure files are readable by Rovo Dev
-
-### Agent Name Conflicts
-
-If you have custom subagents with the same names as BMAD agents, Rovo Dev will load both but may show a warning. Use unique prefixes for custom subagents to avoid conflicts.
-
-### Tools Not Available
-
-If a subagent's tools aren't working:
-
-1. Verify the tool names match Rovo Dev's available tools
-2. Check that the parent Rovo Dev agent has access to those tools
-3. Ensure tool permissions are properly configured in `.rovodev/config.yml`
-
-## Advanced: Tool Configuration
-
-Rovo Dev agents have access to a set of tools for various tasks. Common tools available include:
-
-- `bash`: Execute shell commands
-- `open_files`: View file contents
-- `grep`: Search across files
-- `expand_code_chunks`: View specific code sections
-- `find_and_replace_code`: Modify files
-- `create_file`: Create new files
-- `delete_file`: Delete files
-- `move_file`: Rename or move files
-
-### MCP Servers
-
-Rovo Dev can also connect to Model Context Protocol (MCP) servers, which provide additional tools and data sources:
-
-- **Atlassian Integration**: Access to Jira, Confluence, and Bitbucket
-- **Code Analysis**: Custom code analysis and metrics
-- **External Services**: APIs and third-party integrations
-
-Configure MCP servers in `~/.rovodev/mcp.json` or `.rovodev/mcp.json`.
-
-## Integration with Other IDE Handlers
-
-BMAD-METHOD supports multiple IDEs simultaneously. You can have both Rovo Dev and other IDE configurations (Cursor, VS Code, etc.) in the same project. Each IDE will have its own artifacts installed in separate directories.
-
-For example:
-
-- Rovo Dev agents: `.rovodev/subagents/bmad-*.md`
-- Cursor rules: `.cursor/rules/bmad/`
-- Claude Code: `.claude/rules/bmad/`
-
-## Performance Considerations
-
-- BMAD subagent files are typically small (1-5 KB each)
-- Rovo Dev lazy-loads subagents, so having many subagents doesn't impact startup time
-- System prompts are cached by Rovo Dev after first load
-
-## Best Practices
-
-1. **Keep System Prompts Concise**: Shorter, well-structured prompts are more effective
-2. **Use Project Memory**: Leverage `.rovodev/AGENTS.md` for shared context
-3. **Customize Tool Restrictions**: Give subagents only the tools they need
-4. **Test Subagent Invocations**: Verify each subagent works as expected for your project
-5. **Version Control**: Commit `.rovodev/subagents/` to version control for team consistency
-6. **Document Custom Subagents**: Add comments explaining the purpose of customized subagents
-
-## Related Documentation
-
-- [Rovo Dev Official Documentation](https://www.atlassian.com/rovo-dev)
-- [BMAD-METHOD Installation Guide](./installation.md)
-- [IDE Handler Architecture](./ide-handlers.md)
-- [Rovo Dev Configuration Reference](https://www.atlassian.com/rovo-dev/configuration)
-
-## Examples
-
-### Example 1: Code Review Workflow
-
-```
-User: @bmad-core-code-reviewer Review src/auth/login.ts for security issues
-Rovo Dev → Subagent: Opens file, analyzes code, suggests improvements
-Subagent output: Security vulnerabilities found, recommendations provided
-```
-
-### Example 2: Documentation Generation
-
-```
-User: @bmad-core-documentation-writer Generate API docs for the new payment module
-Rovo Dev → Subagent: Analyzes code structure, generates documentation
-Subagent output: Markdown documentation with examples and API reference
-```
-
-### Example 3: Architecture Design
-
-```
-User: @bmad-module-feature-designer Design a caching strategy for the database layer
-Rovo Dev → Subagent: Reviews current architecture, proposes design
-Subagent output: Detailed architecture proposal with implementation plan
-```
-
-## Support
-
-For issues or questions about:
-
-- **Rovo Dev**: See [Atlassian Rovo Dev Documentation](https://www.atlassian.com/rovo-dev)
-- **BMAD-METHOD**: See [BMAD-METHOD README](../README.md)
-- **IDE Integration**: See [IDE Handler Guide](./ide-handlers.md)
+- Agents are automatically discovered by Rovo Dev
+- Subagents use YAML frontmatter for configuration

docs/index.md

@@ -8,11 +8,11 @@ Complete map of all BMad Method v6 documentation with recommended reading paths.
 
 **New users:** Start with one of these based on your situation:
 
-| Your Situation         | Start Here                                                      | Then Read                                                     |
-| ---------------------- | --------------------------------------------------------------- | ------------------------------------------------------------- |
-| **Brand new to BMad**  | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)     | [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) |
-| **Upgrading from v4**  | [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)                 | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)   |
-| **Brownfield project** | [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) | [Quick Start Guide](../src/modules/bmm/docs/quick-start.md)   |
+| Your Situation         | Start Here                                         | Then Read                                                   |
+| ---------------------- | -------------------------------------------------- | ----------------------------------------------------------- |
+| **Brand new to BMad**  | [Quick Start Guide](./modules/bmm/quick-start)     | [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) |
+| **Upgrading from v4**  | [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)    | [Quick Start Guide](./modules/bmm/quick-start)              |
+| **Brownfield project** | [Brownfield Guide](./modules/bmm/brownfield-guide) | [Quick Start Guide](./modules/bmm/quick-start)              |
 
 ---
 
@@ -20,16 +20,14 @@ Complete map of all BMad Method v6 documentation with recommended reading paths.
 
 ### Project-Level Docs (Root)
 
-- **[README.md](../README.md)** - Main project overview, feature summary, and module introductions
-- **[CONTRIBUTING.md](../CONTRIBUTING.md)** - How to contribute, pull request guidelines, code style
-- **[CHANGELOG.md](../CHANGELOG.md)** - Version history and breaking changes
-- **[CLAUDE.md](../CLAUDE.md)** - Claude Code specific guidelines for this project
+- **[README.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md)** - Main project overview, feature summary, and module introductions
+- **[CONTRIBUTING.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CONTRIBUTING.md)** - How to contribute, pull request guidelines, code style
+- **[CHANGELOG.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CHANGELOG.md)** - Version history and breaking changes
 
 ### Installation & Setup
 
 - **[v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md)** - Migration path for v4 users
 - **[Document Sharding Guide](./document-sharding-guide.md)** - Split large documents for 90%+ token savings
-- **[Web Bundles](./USING_WEB_BUNDLES.md)** - Use BMAD agents in Claude Projects, ChatGPT, or Gemini without installation
 - **[Bundle Distribution Setup](./BUNDLE_DISTRIBUTION_SETUP.md)** - Maintainer guide for bundle auto-publishing
 
 ---
@@ -40,27 +38,27 @@ Complete map of all BMad Method v6 documentation with recommended reading paths.
 
 The flagship module for agile AI-driven development.
 
-- **[BMM Module README](../src/modules/bmm/README.md)** - Module overview, agents, and complete documentation index
-- **[BMM Documentation](../src/modules/bmm/docs/)** - All BMM-specific guides and references:
-  - [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Step-by-step guide to building your first project
-  - [Quick Spec Flow](../src/modules/bmm/docs/quick-spec-flow.md) - Rapid Level 0-1 development
-  - [Scale Adaptive System](../src/modules/bmm/docs/scale-adaptive-system.md) - Understanding the 5-level system
-  - [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) - Working with existing codebases
-- **[BMM Workflows Guide](../src/modules/bmm/workflows/README.md)** - **ESSENTIAL READING**
-- **[Test Architect Guide](../src/modules/bmm/testarch/README.md)** - Testing strategy and quality assurance
+- **[BMM Module README](./modules/bmm/)** - Module overview, agents, and complete documentation index
+- **[BMM Documentation](./modules/bmm/)** - All BMM-specific guides and references:
+  - [Quick Start Guide](./modules/bmm/quick-start) - Step-by-step guide to building your first project
+  - [Quick Spec Flow](./modules/bmm/quick-spec-flow) - Rapid Level 0-1 development
+  - [Scale Adaptive System](./modules/bmm/scale-adaptive-system) - Understanding the 5-level system
+  - [Brownfield Guide](./modules/bmm/brownfield-guide) - Working with existing codebases
+- **[BMM Workflows Guide](./modules/bmm/index#-workflow-guides)** - **ESSENTIAL READING**
+- **[Test Architect Guide](./modules/bmm/test-architecture)** - Testing strategy and quality assurance
 
 ### BMad Builder (BMB) - Create Custom Solutions
 
 Build your own agents, workflows, and modules.
 
-- **[BMB Module README](../src/modules/bmb/docs/README.md)** - Module overview and capabilities
-- **[Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md)** - Design custom agents
+- **[BMB Module Overview](./modules/bmb/index)** - Module overview and capabilities
+- **[Agent Creation Guide](./modules/bmb/agents/index)** - Design custom agents
 
 ### Creative Intelligence Suite (CIS) - Innovation & Creativity
 
 AI-powered creative thinking and brainstorming.
 
-- **[CIS Module README](../src/modules/cis/docs/README.md)** - Module overview and workflows
+- **[CIS Module README](./modules/cis/)** - Module overview and workflows
 
 ---
 
@@ -101,52 +99,45 @@ Instructions for loading agents and running workflows in your development enviro
 - **[Custom Content Installation](./custom-content-installation.md)** - Install and personalize agents, workflows and modules with the default bmad-method installer!
 - [Agent Customization Guide](./agent-customization-guide.md) - Customize agent behavior and responses
 
-### Installation & Bundling
-
-- [IDE Injections Reference](./installers-bundlers/ide-injections.md) - How agents are installed to IDEs
-- [Installers & Platforms Reference](./installers-bundlers/installers-modules-platforms-reference.md) - CLI tool and platform support
-- [Web Bundler Usage](./installers-bundlers/web-bundler-usage.md) - Creating web-compatible bundles
-
 ---
 
 ## 🎓 Recommended Reading Paths
 
 ### Path 1: Brand New to BMad (Software Project)
 
-1. [README.md](../README.md) - Understand the vision
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Get hands-on
-3. [BMM Module README](../src/modules/bmm/README.md) - Understand agents
-4. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Master the methodology
+1. [README.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) - Understand the vision
+2. [Quick Start Guide](./modules/bmm/quick-start) - Get hands-on
+3. [BMM Module README](./modules/bmm/) - Understand agents
+4. [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) - Master the methodology
 5. [Your IDE guide](./ide-info/) - Optimize your workflow
 
 ### Path 2: Game Development Project
 
-1. [README.md](../README.md) - Understand the vision
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Get hands-on
-3. [BMM Module README](../src/modules/bmm/README.md) - Game agents are included
-4. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Game workflows
+1. [README.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/README.md) - Understand the vision
+2. [Quick Start Guide](./modules/bmm/quick-start) - Get hands-on
+3. [BMM Module README](./modules/bmm/) - Game agents are included
+4. [BMGD Workflows Guide](./modules/bmgd/workflows-guide) - Game-specific workflows
 5. [Your IDE guide](./ide-info/) - Optimize your workflow
 
 ### Path 3: Upgrading from v4
 
 1. [v4 to v6 Upgrade Guide](./v4-to-v6-upgrade.md) - Understand what changed
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Reorient yourself
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Learn new v6 workflows
+2. [Quick Start Guide](./modules/bmm/quick-start) - Reorient yourself
+3. [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) - Learn new v6 workflows
 
 ### Path 4: Working with Existing Codebase (Brownfield)
 
-1. [Brownfield Guide](../src/modules/bmm/docs/brownfield-guide.md) - Approach for legacy code
-2. [Quick Start Guide](../src/modules/bmm/docs/quick-start.md) - Follow the process
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Master the methodology
+1. [Brownfield Guide](./modules/bmm/brownfield-guide) - Approach for legacy code
+2. [Quick Start Guide](./modules/bmm/quick-start) - Follow the process
+3. [BMM Workflows Guide](./modules/bmm/index#-workflow-guides) - Master the methodology
 
 ### Path 5: Building Custom Solutions
 
-1. [BMB Module README](../src/modules/bmb/docs/README.md) - Understand capabilities
-2. [Agent Creation Guide](../src/modules/bmb/workflows/create-agent/README.md) - Create agents
-3. [BMM Workflows Guide](../src/modules/bmm/workflows/README.md) - Understand workflow structure
+1. [BMB Module Overview](./modules/bmb/index) - Understand capabilities
+2. [Agent Creation Guide](./modules/bmb/agents/index) - Create agents
+3. [BMB Workflows Guide](./modules/bmb/workflows/) - Understand workflow structure
 
 ### Path 6: Contributing to BMad
 
-1. [CONTRIBUTING.md](../CONTRIBUTING.md) - Contribution guidelines
+1. [CONTRIBUTING.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/CONTRIBUTING.md) - Contribution guidelines
 2. Relevant module README - Understand the area you're contributing to
-3. [Code Style section in CONTRIBUTING.md](../CONTRIBUTING.md#code-style) - Follow standards

eslint.config.mjs

@@ -18,6 +18,10 @@ export default [
       'test/fixtures/**/*.yaml',
       '_bmad/**',
       '_bmad*/**',
+      // Docusaurus build artifacts
+      '.docusaurus/**',
+      'build/**',
+      'website/**',
       // Gitignored patterns
       'z*/**', // z-samples, z1, z2, etc.
       '.claude/**',
@@ -77,9 +81,9 @@ export default [
     },
   },
 
-  // CLI/CommonJS scripts under tools/** and test/**
+  // CLI scripts under tools/** and test/**
   {
-    files: ['tools/**/*.js', 'test/**/*.js'],
+    files: ['tools/**/*.js', 'tools/**/*.mjs', 'test/**/*.js'],
     rules: {
       // Allow CommonJS patterns for Node CLI scripts
       'unicorn/prefer-module': 'off',
@@ -106,6 +110,7 @@ export default [
       'no-useless-catch': 'off',
       'unicorn/prefer-number-properties': 'off',
       'no-unreachable': 'off',
+      'unicorn/text-encoding-identifier-case': 'off',
     },
   },
 

package.json

@@ -26,6 +26,9 @@
   "scripts": {
     "bmad:install": "node tools/cli/bmad-cli.js install",
     "bundle": "node tools/cli/bundlers/bundle-web.js all",
+    "docs:build": "node tools/build-docs.js",
+    "docs:dev": "npm run docs:build && npm run docs:serve",
+    "docs:serve": "docusaurus start --config website/docusaurus.config.js --host localhost",
     "flatten": "node tools/flattener/main.js",
     "format:check": "prettier --check \"**/*.{js,cjs,mjs,json,yaml}\"",
     "format:fix": "prettier --write \"**/*.{js,cjs,mjs,json,yaml}\"",
@@ -72,7 +75,7 @@
     "fs-extra": "^11.3.0",
     "glob": "^11.0.3",
     "ignore": "^7.0.5",
-    "inquirer": "^9.3.8",
+    "inquirer": "^8.2.6",
     "js-yaml": "^4.1.0",
     "ora": "^5.4.1",
     "semver": "^7.6.3",
@@ -81,7 +84,10 @@
     "yaml": "^2.7.0"
   },
   "devDependencies": {
+    "@docusaurus/core": "^3.6.0",
+    "@docusaurus/preset-classic": "^3.6.0",
     "@eslint/js": "^9.33.0",
+    "archiver": "^7.0.1",
     "c8": "^10.1.3",
     "eslint": "^9.33.0",
     "eslint-config-prettier": "^10.1.8",
@@ -94,6 +100,9 @@
     "markdownlint-cli2": "^0.19.1",
     "prettier": "^3.5.3",
     "prettier-plugin-packagejson": "^2.5.19",
+    "prism-react-renderer": "^2.4.1",
+    "react": "^18.3.1",
+    "react-dom": "^18.3.1",
     "yaml-eslint-parser": "^1.2.3",
     "yaml-lint": "^1.7.0",
     "zod": "^4.1.12"

samples/sample-custom-modules/README.md

@@ -4,7 +4,7 @@ These are quickly put together examples of both a stand alone somewhat cohesive
 
 To try these out, download either or both folders to your local machine, and run the normal bmad installer, and when asked about custom local content, say yes, and give the path to one of these two folders. You can even install both with other regular modules to the same project.
 
-Note - a project is just a folder with .bmad in the folder - this can be a software project, but it can also be any type of folder on your local computer - such as a markdown notebook, a folder of other files, or just a folder you maintain with useful agents prompts and utilities for any purpose.
+Note - a project is just a folder with \_bmad in the folder - this can be a software project, but it can also be any type of folder on your local computer - such as a markdown notebook, a folder of other files, or just a folder you maintain with useful agents prompts and utilities for any purpose.
 
 Please remember - these are not optimal or very good examples in their utility or quality control - but they do demonstrate the basics of creating custom content and modules to be able to install for yourself or share with others. This is the groundwork for making very complex modules also such as the full bmad method.
 

samples/sample-custom-modules/sample-unitary-module/agents/toolsmith/toolsmith-sidecar/knowledge/installers.md

@@ -49,7 +49,8 @@
 - @/tools/cli/lib/xml-handler.js - XML processing
 - @/tools/cli/lib/yaml-format.js - YAML formatting
 - @/tools/cli/lib/file-ops.js - File operations
-- @/tools/cli/lib/agent/yaml-xml-builder.js - Agent YAML to XML compilation
+- @/tools/cli/lib/agent/compiler.js - Agent YAML to XML compilation
+- @/tools/cli/lib/agent/installer.js - Agent installation
 - @/tools/cli/lib/agent/template-engine.js - Template processing
 
 ## IDE Handler Registry (16 IDEs)

src/core/agents/bmad-master.agent.yaml

@@ -21,18 +21,14 @@ agent:
     - "ALWAYS communicate in {communication_language}"
 
   menu:
-    - trigger: "CH or fuzzy match on chat"
-      action: "agent responds as expert based on its persona to converse"
-      description: "[CH] Chat with the BMad Master"
-
-    - trigger: "LT or list-tasks or fuzzy match on list tasks"
+    - trigger: "list-tasks"
       action: "list all tasks from {project-root}/_bmad/_config/task-manifest.csv"
-      description: "[LT] List Available Tasks"
+      description: "List Available Tasks"
 
-    - trigger: "LW or list-workflows or fuzzy match on list workflows"
+    - trigger: "list-workflows"
       action: "list all workflows from {project-root}/_bmad/_config/workflow-manifest.csv"
-      description: "[LW] List Workflows"
+      description: "List Workflows"
 
-    - trigger: "PS or party-mode or fuzzy match on party mode"
+    - trigger: "party-mode"
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Group chat with all agents"
+      description: "Group chat with all agents"

src/modules/bmb/README.md

@@ -0,0 +1,25 @@
+# BMB - BMad Builder Module
+
+Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.
+
+## Overview
+
+BMB provides a complete toolkit for extending BMad Method with disciplined, systematic approaches to agent and workflow development while maintaining framework consistency and power.
+
+**1 Master Builder Agent** | **5 Creation Workflows** | **3 Agent Architectures**
+
+## Documentation
+
+For complete documentation, architecture guides, and reference materials:
+
+**[→ BMB Documentation](./docs/index.md)**
+
+## Quick Links
+
+- [Agent Creation Guide](./docs/agents/index.md) - Build custom agents
+- [Workflow Architecture](./docs/workflows/index.md) - Design workflows
+- [Reference Examples](./reference/) - Working examples and templates
+
+---
+
+Part of [BMad Method](https://github.com/bmadcode/bmad-method) v6.0

src/modules/bmb/agents/agent-builder.agent.yaml

@@ -1,36 +0,0 @@
-# Agent Building Expert Agent Definition
-# Specialized in creating, editing, and validating BMAD agents with best practices
-
-agent:
-  webskip: true
-  metadata:
-    id: "_bmad/bmb/agents/agent-building-expert.md"
-    name: Bond
-    title: Agent Building Expert
-    icon: 🤖
-    module: bmb
-
-  persona:
-    role: Agent Architecture Specialist + BMAD Compliance Expert
-    identity: Master agent architect with deep expertise in agent design patterns, persona development, and BMAD Core compliance. Specializes in creating robust, maintainable agents that follow best practices.
-    communication_style: "Precise and technical, like a senior software architect reviewing code. Focuses on structure, compliance, and long-term maintainability. Uses agent-specific terminology and framework references."
-    principles: |
-      - Every agent must follow BMAD Core standards and best practices
-      - Personas drive agent behavior - make them specific and authentic
-      - Menu structure must be consistent across all agents
-      - Validate compliance before finalizing any agent
-      - Load resources at runtime, never pre-load
-      - Focus on practical implementation and real-world usage
-
-  discussion: true
-  conversational_knowledge:
-    - agents: "{project-root}/_bmad/bmb/docs/agents/kb.csv"
-
-  menu:
-    - trigger: CA or create-agent or fuzzy match on create agent
-      exec: "{project-root}/_bmad/bmb/workflows/create-agent/workflow.md"
-      description: "[CA] Create a new BMAD agent with best practices and compliance"
-
-    - trigger: EA or edit-agent or fuzzy match on edit agent
-      exec: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.md"
-      description: "[EA] Edit existing BMAD agents while maintaining compliance"

src/modules/bmb/agents/bmad-builder.agent.yaml

@@ -0,0 +1,94 @@
+# BMad Builder Agent Definition
+# Master BMad Module Agent Team and Workflow Builder and Maintainer
+
+agent:
+  webskip: true
+  metadata:
+    id: "_bmad/bmb/agents/bmad-builder.md"
+    name: BMad Builder
+    title: BMad Builder
+    icon: 🧙
+    module: bmb
+
+  persona:
+    role: Generalist Builder and BMAD System Maintainer
+    identity: A hands-on builder who gets things done efficiently and maintains the entire BMAD ecosystem
+    communication_style: Direct, action-oriented, and encouraging with a can-do attitude
+    principles:
+      - Execute resources directly without hesitation
+      - Load resources at runtime never pre-load
+      - Always present numbered lists for clear choices
+      - Focus on practical implementation and results
+      - Maintain system-wide coherence and standards
+      - Balance speed with quality and compliance
+
+  discussion: true
+  conversational_knowledge:
+    - agents: "{project-root}/_bmad/bmb/docs/agents/kb.csv"
+    - workflows: "{project-root}/_bmad/bmb/docs/workflows/kb.csv"
+    - modules: "{project-root}/_bmad/bmb/docs/modules/kb.csv"
+
+  menu:
+    - multi: "[CA] Create, [EA] Edit, or [VA] Validate with Compliance CheckBMAD agents with best practices"
+      triggers:
+        - create-agent:
+            - input: CA or fuzzy match create agent
+            - route: "{project-root}/_bmad/bmb/workflows/create-agent/workflow.md"
+            - data: null
+            - type: exec
+        - edit-agent:
+            - input: EA or fuzzy match edit agent
+            - route: "{project-root}/_bmad/bmb/workflows/edit-agent/workflow.md"
+            - data: null
+            - type: exec
+        - run-agent-compliance-check:
+            - input: VA or fuzzy match validate agent
+            - route: "{project-root}/_bmad/bmb/workflows/agent-compliance-check/workflow.md"
+            - data: null
+            - type: exec
+
+    - multi: "[CW] Create, [EW] Edit, or [VW] Validate with Compliance CheckBMAD workflows with best practices"
+      triggers:
+        - create-workflow:
+            - input: CW or fuzzy match create workflow
+            - route: "{project-root}/_bmad/bmb/workflows/create-workflow/workflow.md"
+            - data: null
+            - type: exec
+        - edit-workflow:
+            - input: EW or fuzzy match edit workflow
+            - route: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.md"
+            - data: null
+            - type: exec
+        - run-workflow-compliance-check:
+            - input: VW or fuzzy match validate workflow
+            - route: "{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md"
+            - data: null
+            - type: exec
+
+    - multi: "[BM] Brainstorm, [PBM] Product Brief, [CM] Create, [EM] Edit or [VM] Validate with Compliance Check BMAD modules with best practices"
+      triggers:
+        - brainstorm-module:
+            - input: BM or fuzzy match brainstorm module
+            - route: "{project-root}/_bmad/bmb/workflows/brainstorm-module/workflow.md"
+            - data: null
+            - type: exec
+        - product-brief-module:
+            - input: PBM or fuzzy match product brief module
+            - route: "{project-root}/_bmad/bmb/workflows/product-brief-module/workflow.md"
+            - data: null
+            - type: exec
+        - create-module:
+            - input: CM or fuzzy match create module
+            - route: "{project-root}/_bmad/bmb/workflows/create-module/workflow.md"
+            - data: null
+            - type: exec
+        - edit-module:
+            - input: EM or fuzzy match edit module
+            - route: "{project-root}/_bmad/bmb/workflows/edit-module/workflow.md"
+            - data: null
+            - type: exec
+        - run-module-compliance-check:
+            - input: VM or fuzzy match validate module
+            - route: "{project-root}/_bmad/bmb/workflows/module-compliance-check/workflow.md"
+            - data: null
+            - type: exec

src/modules/bmb/agents/module-builder.agent.yaml

@@ -1,48 +0,0 @@
-# Module Creation Master Agent Definition
-# Specialized in creating, editing, and validating complete BMAD modules with best practices
-
-agent:
-  webskip: true
-  metadata:
-    id: "_bmad/bmb/agents/module-creation-master.md"
-    name: Morgan
-    title: Module Creation Master
-    icon: 🏗️
-    module: bmb
-
-  persona:
-    role: Module Architecture Specialist + Full-Stack Systems Designer
-    identity: Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.
-    communication_style: "Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability."
-    principles: |
-      - Modules must be self-contained yet integrate seamlessly
-      - Every module should solve specific business problems effectively
-      - Documentation and examples are as important as code
-      - Plan for growth and evolution from day one
-      - Balance innovation with proven patterns
-      - Consider the entire module lifecycle from creation to maintenance
-
-  discussion: true
-  conversational_knowledge:
-    - modules: "{project-root}/_bmad/bmb/docs/modules/kb.csv"
-
-  menu:
-    - trigger: BM or brainstorm-module or fuzzy match on brainstorm module
-      exec: "{project-root}/_bmad/bmb/workflows/brainstorm-module/workflow.md"
-      description: "[BM] Brainstorm and conceptualize new BMAD modules"
-
-    - trigger: PB or product-brief or fuzzy match on product brief module
-      exec: "{project-root}/_bmad/bmb/workflows/product-brief-module/workflow.md"
-      description: "[PB] Create product brief for BMAD module development"
-
-    - trigger: CM or create-module or fuzzy match on create module
-      exec: "{project-root}/_bmad/bmb/workflows/create-module/workflow.md"
-      description: "[CM] Create a complete BMAD module with agents, workflows, and infrastructure"
-
-    - trigger: EM or edit-module or fuzzy match on edit module
-      exec: "{project-root}/_bmad/bmb/workflows/edit-module/workflow.md"
-      description: "[EM] Edit existing BMAD modules while maintaining coherence"
-
-    - trigger: VM or validate-module or fuzzy match on validate module
-      exec: "{project-root}/_bmad/bmb/workflows/module-compliance-check/workflow.md"
-      description: "[VM] Run compliance check on BMAD modules against best practices"

src/modules/bmb/agents/workflow-builder.agent.yaml

@@ -1,40 +0,0 @@
-# Workflow Building Master Agent Definition
-# Specialized in creating, editing, and validating BMAD workflows with best practices
-
-agent:
-  webskip: true
-  metadata:
-    id: "_bmad/bmb/agents/workflow-building-master.md"
-    name: Wendy
-    title: Workflow Building Master
-    icon: 🔄
-    module: bmb
-
-  persona:
-    role: Workflow Architecture Specialist + Process Design Expert
-    identity: Master workflow architect with expertise in process design, state management, and workflow optimization. Specializes in creating efficient, scalable workflows that integrate seamlessly with BMAD systems.
-    communication_style: "Methodical and process-oriented, like a systems engineer. Focuses on flow, efficiency, and error handling. Uses workflow-specific terminology and thinks in terms of states, transitions, and data flow."
-    principles: |
-      - Workflows must be efficient, reliable, and maintainable
-      - Every workflow should have clear entry and exit points
-      - Error handling and edge cases are critical for robust workflows
-      - Workflow documentation must be comprehensive and clear
-      - Test workflows thoroughly before deployment
-      - Optimize for both performance and user experience
-
-  discussion: true
-  conversational_knowledge:
-    - workflows: "{project-root}/_bmad/bmb/docs/workflows/kb.csv"
-
-  menu:
-    - trigger: CW or create-workflow or fuzzy match on create workflow
-      exec: "{project-root}/_bmad/bmb/workflows/create-workflow/workflow.md"
-      description: "[CW] Create a new BMAD workflow with proper structure and best practices"
-
-    # - trigger: EW or edit-workflow or fuzzy match on edit workflow
-    #   exec: "{project-root}/_bmad/bmb/workflows/edit-workflow/workflow.md"
-    #   description: "[EW] Edit existing BMAD workflows while maintaining integrity"
-
-    # - trigger: VW or validate-workflow or fuzzy match on validate workflow
-    #   exec: "{project-root}/_bmad/bmb/workflows/workflow-compliance-check/workflow.md"
-    #   description: "[VW] Run compliance check on BMAD workflows against best practices"

src/modules/bmb/docs/agents/agent-compilation.md

@@ -8,7 +8,7 @@ What the compiler auto-injects. **DO NOT duplicate these in your YAML.**
 agent.yaml → Handlebars processing → XML generation → frontmatter.md
 ```
 
-Source: `tools/cli/lib/agent/yaml-xml-builder.js`
+Source: `tools/cli/lib/agent/compiler.js`
 
 ## File Naming Convention
 

src/modules/bmb/docs/agents/expert-agent-architecture.md

@@ -223,7 +223,7 @@ Same as simple agents, PLUS:
 
 ## Reference Example
 
-See: `bmb/reference/agents/expert-examples/journal-keeper/`
+See: [journal-keeper/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper)
 
 Features demonstrated:
 

src/modules/bmb/docs/agents/index.md

@@ -9,7 +9,7 @@ Comprehensive guides for each agent type (choose based on use case):
 - [Understanding Agent Types](./understanding-agent-types.md) - **START HERE** - Architecture vs capability, "The Same Agent, Three Ways"
 - [Simple Agent Architecture](./simple-agent-architecture.md) - Self-contained, optimized, personality-driven
 - [Expert Agent Architecture](./expert-agent-architecture.md) - Memory, sidecar files, domain restrictions
-- [Module Agent Architecture](./module-agent-architecture.md) - Workflow integration, professional tools
+- Module Agent Architecture _(TODO)_ - Workflow integration, professional tools
 
 ## Agent Design Patterns
 
@@ -18,20 +18,20 @@ Comprehensive guides for each agent type (choose based on use case):
 
 ## Reference Examples
 
-Production-ready examples in `/bmb/reference/agents/`:
+Production-ready examples in [bmb/reference/agents/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents):
 
-**Simple Agents** (`simple-examples/`)
+**Simple Agents** ([simple-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/simple-examples))
 
-- `commit-poet.agent.yaml` - Commit message artisan with style customization
+- [commit-poet.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml) - Commit message artisan with style customization
 
-**Expert Agents** (`expert-examples/`)
+**Expert Agents** ([expert-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples))
 
-- `journal-keeper/` - Personal journal companion with memory and pattern recognition
+- [journal-keeper/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper) - Personal journal companion with memory and pattern recognition
 
-**Module Agents** (`module-examples/`)
+**Module Agents** ([module-examples/](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/agents/module-examples))
 
-- `security-engineer.agent.yaml` - BMM security specialist with threat modeling
-- `trend-analyst.agent.yaml` - CIS trend intelligence expert
+- [security-engineer.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml) - BMM security specialist with threat modeling
+- [trend-analyst.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/trend-analyst.agent.yaml) - CIS trend intelligence expert
 
 ## Installation Guide
 
@@ -52,4 +52,4 @@ Agents are authored in YAML with Handlebars templating. The compiler auto-inject
 
 **Critical:** See [Agent Compilation](./agent-compilation.md) to avoid duplicating auto-injected content.
 
-Source: `tools/cli/lib/agent/yaml-xml-builder.js`
+Source: `tools/cli/lib/agent/compiler.js`

src/modules/bmb/docs/agents/simple-agent-architecture.md

@@ -178,7 +178,7 @@ Content when false
 
 ## What Gets Injected at Compile Time
 
-The `tools/cli/lib/agent/yaml-xml-builder.js` automatically adds:
+The `tools/cli/lib/agent/compiler.js` automatically adds:
 
 1. **YAML Frontmatter**
 
@@ -206,7 +206,7 @@ The `tools/cli/lib/agent/yaml-xml-builder.js` automatically adds:
 
 ## Reference Example
 
-See: `../../reference/agents/simple-examples/commit-poet.agent.yaml`
+See: [commit-poet.agent.yaml](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml)
 
 Features demonstrated:
 

src/modules/bmb/docs/index.md

@@ -16,7 +16,9 @@ Specialized tools and workflows for creating, customizing, and extending BMad co
 
 ### 🤖 Agents
 
-There is a dedicated Agent expert, a Workflow Expert, and a Module Expert agent available!
+**BMad Builder** - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.
+
+- Install Location: `_bmad/bmb/agents/bmad-builder.md`
 
 ### 📚 Documentation
 
@@ -42,33 +44,33 @@ There is a dedicated Agent expert, a Workflow Expert, and a Module Expert agent
 
 - **[Workflow Index](./workflows/index.md)** - Core workflow system overview
 - **[Architecture Guide](./workflows/architecture.md)** - Step-file design and JIT loading
-- **[Template System](./workflows/templates/step-template.md)** - Standard step file template
+- **Template System** _(TODO)_ - Standard step file template
 - **[Intent vs Prescriptive](./workflows/intent-vs-prescriptive-spectrum.md)** - Design philosophy
 
 ## Reference Materials
 
 ### 🤖 Agent Examples
 
-- **[Simple Agent Example](../reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
-- **[Expert Agent Example](../reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml)** - Agent with persistent memory
-- **[Module Add On Agent Examples](../reference/agents/module-examples/security-engineer.agent.yaml)** - Integration patterns (BMM, CIS)
+- **[Simple Agent Example](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/simple-examples/commit-poet.agent.yaml)** - Self-contained agent
+- **[Expert Agent Example](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/expert-examples/journal-keeper/journal-keeper.agent.yaml)** - Agent with persistent memory
+- **[Module Add On Agent Examples](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/agents/module-examples/security-engineer.agent.yaml)** - Integration patterns (BMM, CIS)
 
 ### 📋 Workflow Examples
 
-- **[Meal Prep & Nutrition](./reference/workflows/meal-prep-nutrition/)** - Complete step-file workflow demonstration
+- **[Meal Prep & Nutrition](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/src/modules/bmb/reference/workflows/meal-prep-nutrition)** - Complete step-file workflow demonstration
 - **Template patterns** for document generation and state management
 
 ## Core Workflows
 
 ### Creation Workflows (Step-File Architecture)
 
-**[create-agent](./workflows/create-agent/)** - Build BMad agents
+**create-agent** _(TODO)_ - Build BMad agents
 
 - 11 guided steps from brainstorming to celebration
 - 18 reference data files with validation checklists
 - Template-based agent generation
 
-**[create-workflow](./workflows/create-workflow/)** - Design workflows
+**create-workflow** _(TODO)_ - Design workflows
 
 - 12 structured steps from init to review
 - 9 template files for workflow creation
@@ -76,13 +78,13 @@ There is a dedicated Agent expert, a Workflow Expert, and a Module Expert agent
 
 ### Editing Workflows
 
-**[edit-agent](./workflows/edit-agent/)** - Modify existing agents
+**edit-agent** _(TODO)_ - Modify existing agents
 
 - 5 steps: discovery → validation
 - Intent-driven analysis and updates
 - Best practice compliance
 
-**[edit-workflow](./workflows/edit-workflow/)** - Update workflows
+**edit-workflow** _(TODO)_ - Update workflows
 
 - 5 steps: analyze → compliance check
 - Structure maintenance and validation
@@ -90,7 +92,7 @@ There is a dedicated Agent expert, a Workflow Expert, and a Module Expert agent
 
 ### Quality Assurance
 
-**[workflow-compliance-check](./workflows/workflow-compliance-check/)** - Validation
+**workflow-compliance-check** _(TODO)_ - Validation
 
 - 8 systematic validation steps
 - Adversarial analysis approach
@@ -131,12 +133,21 @@ BMB creates three agent architectures:
 
 ## Quick Start
 
-### Using BMad Builder Agents
+### Using BMad Builder Agent
 
-1. **Load BMad Builder agents** in your IDE:
+1. **Load BMad Builder agent** in your IDE:
    ```
-   /bmad:bmb:agents:agent-builder|module-builder|workflow-builder
+   /bmad:bmb:agents:bmad-builder
    ```
+2. **Choose creation type:**
+   - `[CA]` Create Agent - Build new agents
+   - `[CW]` Create Workflow - Design workflows
+   - `[EA]` Edit Agent - Modify existing agents
+   - `[EW]` Edit Workflow - Update workflows
+   - `[VA]` Validate Agent - Quality check agents
+   - `[VW]` Validate Workflow - Quality check workflows
+
+3. **Follow interactive prompts** for step-by-step guidance
 
 ### Example: Creating an Agent
 

src/modules/bmb/docs/workflows/index.md

@@ -12,27 +12,27 @@ Essential terminology and concepts for understanding BMAD workflows.
 
 The micro-file architecture, JIT step loading, state management, and collaboration patterns that make BMAD workflows optimal for AI execution.
 
-### [Writing Workflows](./writing-workflows.md)
+### Writing Workflows _(TODO)_
 
 Complete guide to creating workflows: workflow.md control files, step files, CSV data integration, and frontmatter design.
 
-### [Step Files & Dialog Patterns](./step-files.md)
+### Step Files & Dialog Patterns _(TODO)_
 
 Crafting effective step files: structure, execution rules, prescriptive vs intent-based dialog, and validation patterns.
 
-### [Templates & Content Generation](./templates.md)
+### Templates & Content Generation _(TODO)_
 
 Creating append-only templates, frontmatter design, conditional content, and dynamic content generation strategies.
 
-### [Workflow Patterns](./patterns.md)
+### Workflow Patterns _(TODO)_
 
 Common workflow types: linear, conditional, protocol integration, multi-agent workflows, and real-world examples.
 
-### [Migration Guide](./migration.md)
+### Migration Guide _(TODO)_
 
 Converting from XML-heavy workflows to the new pure markdown format, with before/after examples and checklist.
 
-### [Best Practices & Reference](./best-practices.md)
+### Best Practices & Reference _(TODO)_
 
 Critical rules, anti-patterns, performance optimization, debugging, quick reference templates, and troubleshooting.
 

src/modules/bmb/docs/workflows/templates/step-template.md

@@ -243,7 +243,7 @@ Display: "**Select an Option:** [A] [Continue to Step Foo] [A] [Continue to Step
 
 ### Initialization Step Example
 
-See [step-01-init.md](../reference/workflows/meal-prep-nutrition/steps/step-01-init.md) for an example of:
+See [step-01-init.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01-init.md) for an example of:
 
 - Detecting existing workflow state and short circuit to 1b
 - Creating output documents from templates
@@ -252,7 +252,7 @@ See [step-01-init.md](../reference/workflows/meal-prep-nutrition/steps/step-01-i
 
 ### Continuation Step Example
 
-See [step-01b-continue.md](../reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md) for an example of:
+See [step-01b-continue.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-01b-continue.md) for an example of:
 
 - Handling already-in-progress workflows
 - Detecting completion status
@@ -261,7 +261,7 @@ See [step-01b-continue.md](../reference/workflows/meal-prep-nutrition/steps/step
 
 ### Standard Step with Menu Example
 
-See [step-02-profile.md](../reference/workflows/meal-prep-nutrition/steps/step-02-profile.md) for an example of:
+See [step-02-profile.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-02-profile.md) for an example of:
 
 - Presenting a menu with A/P/C options
 - Forcing halt until user selects 'C' (Continue)
@@ -271,7 +271,7 @@ See [step-02-profile.md](../reference/workflows/meal-prep-nutrition/steps/step-0
 
 ### Final Step Example
 
-See [step-06-prep-schedule.md](../reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md) for an example of:
+See [step-06-prep-schedule.md](https://github.com/bmad-code-org/BMAD-METHOD/blob/main/src/modules/bmb/reference/workflows/meal-prep-nutrition/steps/step-06-prep-schedule.md) for an example of:
 
 - Completing workflow deliverables
 - Marking workflow as complete in frontmatter

src/modules/bmb/workflows-legacy/edit-module/README.md

@@ -154,7 +154,7 @@ Workflow: Analyzes BMM → You choose option 8 (add new workflow)
 
 ## Activation
 
-Invoke via BMad Module Builder agent:
+Invoke via BMad Builder agent:
 
 ```
 /bmad:bmb:agents:bmad-builder

src/modules/bmb/workflows/create-agent/templates/simple-agent.template.md

@@ -178,7 +178,7 @@ Content when false
 
 ## What Gets Injected at Compile Time
 
-The `tools/cli/lib/agent/yaml-xml-builder.js` automatically adds:
+The `tools/cli/lib/agent/compiler.js` automatically adds:
 
 1. **YAML Frontmatter**
 

src/modules/bmgd/agents/game-architect.agent.yaml

@@ -25,27 +25,28 @@ agent:
     - "Always document performance budgets and critical path decisions"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+      description: Get workflow status or initialize a workflow if not already done
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Game Architect"
-
-    - trigger: GA or game-architecture or fuzzy match on game architecture
+    - trigger: create-architecture
       exec: "{project-root}/_bmad/bmgd/workflows/3-technical/game-architecture/workflow.md"
-      description: "[GA] Produce a Scale Adaptive Game Architecture"
+      description: Produce a Scale Adaptive Game Architecture
 
-    - trigger: PC or project-context or fuzzy match on project context
+    - trigger: generate-project-context
       exec: "{project-root}/_bmad/bmgd/workflows/3-technical/generate-project-context/workflow.md"
-      description: "[PC] Create optimized project-context.md for AI agent consistency"
+      description: Create optimized project-context.md for AI agent consistency
 
-    - trigger: CC or correct-course or fuzzy match on correct course
+    - trigger: correct-course
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
-      description: "[CC] Course Correction Analysis (when implementation is off-track)"
+      description: Course Correction Analysis (when implementation is off-track)
       ide-only: true
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmgd/agents/game-designer.agent.yaml

@@ -22,35 +22,39 @@ agent:
     - "When creating GDDs, always validate against game pillars and core loop"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+      description: Get workflow status or initialize a workflow if not already done
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Game Designer"
+    - multi: "[BG] Brainstorm Game, [GB] Create Game Brief, [GDD] Create GDD, [ND] Narrative Design"
+      triggers:
+        - brainstorm-game:
+            - input: BG or fuzzy match brainstorm game
+            - route: "{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md"
+            - type: exec
+        - create-game-brief:
+            - input: GB or fuzzy match create game brief
+            - route: "{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md"
+            - type: exec
+        - create-gdd:
+            - input: GDD or fuzzy match create gdd
+            - route: "{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.md"
+            - type: exec
+        - narrative:
+            - input: ND or fuzzy match narrative design
+            - route: "{project-root}/_bmad/bmgd/workflows/2-design/narrative/workflow.md"
+            - type: exec
 
-    - trigger: BG or brainstorm-game or fuzzy match on brainstorm game
-      exec: "{project-root}/_bmad/bmgd/workflows/1-preproduction/brainstorm-game/workflow.md"
-      description: "[BG] Brainstorm Game ideas and concepts"
-
-    - trigger: GB or game-brief or fuzzy match on game brief
-      exec: "{project-root}/_bmad/bmgd/workflows/1-preproduction/game-brief/workflow.md"
-      description: "[GB] Create a Game Brief document"
-
-    - trigger: GDD or create-gdd or fuzzy match on gdd
-      exec: "{project-root}/_bmad/bmgd/workflows/2-design/gdd/workflow.md"
-      description: "[GDD] Create a Game Design Document"
-
-    - trigger: ND or narrative-design or fuzzy match on narrative design
-      exec: "{project-root}/_bmad/bmgd/workflows/2-design/narrative/workflow.md"
-      description: "[ND] Design narrative elements and story"
-
-    - trigger: QP or quick-prototype or fuzzy match on quick prototype
+    - trigger: quick-prototype
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
-      description: "[QP] Rapid game prototyping - test mechanics and ideas quickly"
+      description: Rapid game prototyping - test mechanics and ideas quickly
       ide-only: true
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmgd/agents/game-dev.agent.yaml

@@ -24,37 +24,33 @@ agent:
     - "Always check for performance implications on game loop code"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or check current sprint progress (optional)"
+      description: Get workflow status or check current sprint progress
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Game Developer"
-
-    - trigger: DS or dev-story or fuzzy match on dev story
+    - trigger: dev-story
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/dev-story/workflow.yaml"
-      description: "[DS] Execute Dev Story workflow, implementing tasks and tests"
+      description: Execute Dev Story workflow, implementing tasks and tests
 
-    - trigger: CR or code-review or fuzzy match on code review
+    - trigger: code-review
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/code-review/workflow.yaml"
-      description: "[CR] Perform a thorough clean context QA code review on a story flagged Ready for Review"
+      description: Perform a thorough clean context QA code review on a story flagged Ready for Review
 
-    - trigger: QD or quick-dev or fuzzy match on quick dev
+    - trigger: quick-dev
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
-      description: "[QD] Flexible game development - implement features with game-specific considerations"
+      description: Flexible game development - implement features with game-specific considerations
       ide-only: true
 
-    - trigger: QP or quick-prototype or fuzzy match on quick prototype
+    - trigger: quick-prototype
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
-      description: "[QP] Rapid game prototyping - test mechanics and ideas quickly"
+      description: Rapid game prototyping - test mechanics and ideas quickly
       ide-only: true
 
-    - trigger: AE or advanced-elicitation or fuzzy match on advanced elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
-      web-only: true
-
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmgd/agents/game-qa.agent.yaml

@@ -26,43 +26,39 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or check current project state (optional)"
+      description: Get workflow status or check current project state
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Game QA Architect"
-
-    - trigger: TF or test-framework or fuzzy match on test framework
+    - trigger: test-framework
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml"
-      description: "[TF] Initialize game test framework (Unity/Unreal/Godot)"
+      description: Initialize game test framework (Unity/Unreal/Godot)
 
-    - trigger: TD or test-design or fuzzy match on test design
+    - trigger: test-design
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-design/workflow.yaml"
-      description: "[TD] Create comprehensive game test scenarios"
+      description: Create comprehensive game test scenarios
 
-    - trigger: TA or test-automate or fuzzy match on test automate
+    - trigger: automate
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/automate/workflow.yaml"
-      description: "[TA] Generate automated game tests"
+      description: Generate automated game tests
 
-    - trigger: PP or playtest-plan or fuzzy match on playtest plan
+    - trigger: playtest-plan
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/playtest-plan/workflow.yaml"
-      description: "[PP] Create structured playtesting plan"
+      description: Create structured playtesting plan
 
-    - trigger: PT or performance-test or fuzzy match on performance test
+    - trigger: performance-test
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/performance/workflow.yaml"
-      description: "[PT] Design performance testing strategy"
+      description: Design performance testing strategy
 
-    - trigger: TR or test-review or fuzzy match on test review
+    - trigger: test-review
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-review/workflow.yaml"
-      description: "[TR] Review test quality and coverage"
+      description: Review test quality and coverage
 
-    - trigger: AE or advanced-elicitation or fuzzy match on advanced elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
-      web-only: true
-
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmgd/agents/game-scrum-master.agent.yaml

@@ -24,44 +24,40 @@ agent:
     - "Generate complete story drafts from existing documentation without additional elicitation"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+      description: Get workflow status or initialize a workflow if not already done
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Game Dev Scrum Master"
-
-    - trigger: SP or sprint-planning or fuzzy match on sprint planning
+    - trigger: sprint-planning
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/sprint-planning/workflow.yaml"
-      description: "[SP] Generate or update sprint-status.yaml from epic files (Required after GDD+Epics are created)"
+      description: Generate or update sprint-status.yaml from epic files (Required after GDD+Epics are created)
 
-    - trigger: SS or sprint-status or fuzzy match on sprint status
+    - trigger: sprint-status
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/sprint-status/workflow.yaml"
-      description: "[SS] View sprint progress, surface risks, and get next action recommendation"
+      description: View sprint progress, surface risks, and get next action recommendation
 
-    - trigger: CS or create-story or fuzzy match on create story
+    - trigger: create-story
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
-      description: "[CS] Create Story with direct ready-for-dev marking (Required to prepare stories for development)"
+      description: Create Story with direct ready-for-dev marking (Required to prepare stories for development)
 
-    - trigger: VS or validate-story or fuzzy match on validate story
+    - trigger: validate-create-story
       validate-workflow: "{project-root}/_bmad/bmgd/workflows/4-production/create-story/workflow.yaml"
-      description: "[VS] Validate Story Draft with Independent Review (Highly Recommended)"
+      description: Validate Story Draft with Independent Review (Highly Recommended)
 
-    - trigger: ER or epic-retrospective or fuzzy match on epic retrospective
+    - trigger: epic-retrospective
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/retrospective/workflow.yaml"
       data: "{project-root}/_bmad/_config/agent-manifest.csv"
-      description: "[ER] Facilitate team retrospective after a game development epic is completed"
+      description: Facilitate team retrospective after a game development epic is completed
 
-    - trigger: CC or correct-course or fuzzy match on correct course
+    - trigger: correct-course
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/correct-course/workflow.yaml"
-      description: "[CC] Navigate significant changes during game dev sprint (When implementation is off-track)"
+      description: Navigate significant changes during game dev sprint (When implementation is off-track)
 
-    - trigger: AE or advanced-elicitation or fuzzy match on advanced elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
-      web-only: true
-
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmgd/agents/game-solo-dev.agent.yaml

@@ -22,39 +22,35 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmgd/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or check current project state (optional)"
+      description: Get workflow status or check current project state
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Game Solo Dev"
-
-    - trigger: QP or quick-prototype or fuzzy match on quick prototype
+    - trigger: quick-prototype
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-prototype/workflow.yaml"
-      description: "[QP] Rapid prototype to test if the mechanic is fun (Start here for new ideas)"
+      description: Rapid prototype to test if the mechanic is fun (Start here for new ideas)
 
-    - trigger: QD or quick-dev or fuzzy match on quick dev
+    - trigger: quick-dev
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/quick-dev/workflow.yaml"
-      description: "[QD] Implement features end-to-end solo with game-specific considerations"
+      description: Implement features end-to-end solo with game-specific considerations
 
-    - trigger: TS or tech-spec or fuzzy match on tech spec
+    - trigger: create-tech-spec
       workflow: "{project-root}/_bmad/bmgd/workflows/bmgd-quick-flow/create-tech-spec/workflow.yaml"
-      description: "[TS] Architect a technical spec with implementation-ready stories"
+      description: Architect a technical spec with implementation-ready stories
 
-    - trigger: CR or code-review or fuzzy match on code review
+    - trigger: code-review
       workflow: "{project-root}/_bmad/bmgd/workflows/4-production/code-review/workflow.yaml"
-      description: "[CR] Review code quality (use fresh context for best results)"
+      description: Review code quality (use fresh context for best results)
 
-    - trigger: TF or test-framework or fuzzy match on test framework
+    - trigger: test-framework
       workflow: "{project-root}/_bmad/bmgd/workflows/gametest/test-framework/workflow.yaml"
-      description: "[TF] Set up automated testing for your game engine"
+      description: Set up automated testing for your game engine
 
-    - trigger: AE or advanced-elicitation or fuzzy match on advanced elicitation
-      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
-      description: "[AE] Advanced elicitation techniques to challenge the LLM to get better results"
-      web-only: true
-
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring in other experts when specialized backup is needed"
+      description: Bring in other experts when specialized backup is needed
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmgd/docs/index.md

@@ -163,8 +163,8 @@ BMGD Documentation
 
 ### Related Documentation
 
-- **[BMM Documentation](../../bmm/docs/README.md)** - Core BMad Method documentation
-- **[IDE Setup Guides](../../../../docs/ide-info/)** - Configure your development environment
+- **[BMM Documentation](../../bmm/docs/index.md)** - Core BMad Method documentation
+- **[IDE Guides](../../ide-info/)** - Configure your development environment
 
 ---
 

src/modules/bmm/README.md

@@ -6,7 +6,7 @@ Core orchestration system for AI-driven agile development, providing comprehensi
 
 ## 📚 Complete Documentation
 
-👉 **[BMM Documentation Hub](./docs/README.md)** - Start here for complete guides, tutorials, and references
+👉 **[BMM Documentation Hub](./docs/index.md)** - Start here for complete guides, tutorials, and references
 
 **Quick Links:**
 
@@ -48,7 +48,7 @@ bmm/
 **Phase 3:** Solutioning (required) - 3 workflows
 **Phase 4:** Implementation (iterative) - 7 workflows
 
-👉 **[Workflow Guides](./docs/README.md#-workflow-guides)** - Detailed documentation for each phase
+👉 **[Workflow Guides](./docs/index.md#-workflow-guides)** - Detailed documentation for each phase
 
 ---
 

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

@@ -18,31 +18,35 @@ agent:
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+      description: Get workflow status or initialize a workflow if not already done (optional)
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Business Analyst"
-
-    - trigger: BP or brainstorm-project or fuzzy match on brainstorm
+    - trigger: brainstorm-project
       exec: "{project-root}/_bmad/core/workflows/brainstorming/workflow.md"
       data: "{project-root}/_bmad/bmm/data/project-context-template.md"
-      description: "[BP] Guided Project Brainstorming session with final report (optional)"
+      description: Guided Project Brainstorming session with final report (optional)
 
-    - trigger: RS or research or fuzzy match on research
+    - trigger: research
       exec: "{project-root}/_bmad/bmm/workflows/1-analysis/research/workflow.md"
-      description: "[RS] Guided Research scoped to market, domain, competitive analysis, or technical research (optional)"
+      description: Guided Research scoped to market, domain, competitive analysis, or technical research (optional)
 
-    - trigger: PB or product-brief or fuzzy match on product brief
+    - trigger: product-brief
       exec: "{project-root}/_bmad/bmm/workflows/1-analysis/create-product-brief/workflow.md"
-      description: "[PB] Create a Product Brief (recommended input for PRD)"
+      description: Create a Product Brief (recommended input for PRD)
 
-    - trigger: DP or document-project or fuzzy match on document project
+    - trigger: document-project
       workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
-      description: "[DP] Document your existing project (optional, but recommended for existing brownfield project efforts)"
+      description: Document your existing project (optional, but recommended for existing brownfield project efforts)
 
-    - trigger: PS or party-mode or fuzzy match on party mode
-      exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+    - multi: "[SPM] Start Party Mode (optionally suggest attendees and topic), [CH] Chat"
+      triggers:
+        - party-mode:
+            - input: SPM or fuzzy match start party mode
+            - route: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
+            - data: what is being discussed or suggested with the command, along with custom party custom agents if specified
+            - type: exec
+        - expert-chat:
+            - input: CH or fuzzy match validate agent
+            - action: agent responds as expert based on its persona to converse
+            - type: action

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

@@ -18,22 +18,31 @@ agent:
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+      description: Get workflow status or initialize a workflow if not already done (optional)
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Architect Agent"
-
-    - trigger: CA or create-architecture or fuzzy match on create architecture
+    - trigger: create-architecture
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-architecture/workflow.md"
-      description: "[CA] Create an Architecture Document"
+      description: Create an Architecture Document to Guide Development of a PRD (required for BMad Method projects)
 
-    - trigger: IR or implementation-readiness or fuzzy match on implementation readiness
+    - trigger: implementation-readiness
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
-      description: "[IR] Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)"
+      description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
 
-    - trigger: PS or party-mode or fuzzy match on party mode start
+    - trigger: create-excalidraw-diagram
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
+      description: Create system architecture or technical diagram (Excalidraw) (Use any time you need a diagram)
+
+    - trigger: create-excalidraw-dataflow
+      workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
+      description: Create data flow diagram (Excalidraw) (Use any time you need a diagram)
+
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

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

@@ -35,14 +35,14 @@ agent:
     - "NEVER lie about tests being written or passing - tests must actually exist and pass 100%"
 
   menu:
-    - trigger: DS or dev-story or fuzzy match on dev story
+    - trigger: DS or dev-story or fuzzy match on dev-story
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
       description: "[DS] Execute Dev Story workflow (full BMM path with sprint-status)"
 
-    - trigger: CR or code-review or fuzzy match on code review
+    - trigger: CR or code-review or fuzzy match on code-review
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
       description: "[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)"
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: PM or party-mode or fuzzy match on party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: "[PM] Bring the whole team in to chat with other expert agents from the party"

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

@@ -19,31 +19,32 @@ agent:
       - Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
+    - trigger: workflow-status
       workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
+      description: Get workflow status or initialize a workflow if not already done (optional)
 
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Product Manager"
-
-    - trigger: PR or prd or fuzzy match on prd
+    - trigger: create-prd
       exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/prd/workflow.md"
-      description: "[PR] Create Product Requirements Document (PRD) (Required for BMad Method flow)"
+      description: Create Product Requirements Document (PRD) (Required for BMad Method flow)
 
-    - trigger: ES or epics-stories or fuzzy match on epics and stories
+    - trigger: create-epics-and-stories
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/create-epics-and-stories/workflow.md"
-      description: "[ES] Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed)"
+      description: Create Epics and User Stories from PRD (Required for BMad Method flow AFTER the Architecture is completed)
 
-    - trigger: IR or implementation-readiness or fuzzy match on implementation readiness
+    - trigger: implementation-readiness
       exec: "{project-root}/_bmad/bmm/workflows/3-solutioning/check-implementation-readiness/workflow.md"
-      description: "[IR] Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)"
+      description: Validate PRD, UX, Architecture, Epics and stories aligned (Optional but recommended before development)
 
-    - trigger: CC or correct-course or fuzzy match on correct course
+    - trigger: correct-course
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: "[CC] Course Correction Analysis (optional during implementation when things go off track)"
+      description: Course Correction Analysis (optional during implementation when things go off track)
       ide-only: true
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmm/agents/quick-flow-solo-dev.agent.yaml

@@ -18,14 +18,10 @@ agent:
       - If `**/project-context.md` exists, follow it. If absent, proceed without.
 
   menu:
-    - trigger: TS or tech-spec or fuzzy match on tech spec
+    - trigger: TS or tech-spec or fuzzy match on tech-spec
       workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/create-tech-spec/workflow.yaml"
       description: "[TS] Architect a technical spec with implementation-ready stories (Required first step)"
 
-    - trigger: QD or quick-dev or fuzzy match on quick dev
+    - trigger: QD or quick-dev or fuzzy match on quick-dev
       workflow: "{project-root}/_bmad/bmm/workflows/bmad-quick-flow/quick-dev/workflow.yaml"
       description: "[QD] Implement the tech spec end-to-end solo (Core of Quick Flow)"
-
-    - trigger: CR or code-review or fuzzy match on code review
-      workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      description: "[CR] Perform a thorough clean context code review (Highly Recommended, use fresh context and different LLM)"

src/modules/bmm/agents/sm.agent.yaml

@@ -24,31 +24,35 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
-      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
-
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Scrum Master"
-
-    - trigger: SP or sprint-planning or fuzzy match on sprint planning
+    - trigger: sprint-planning
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/sprint-planning/workflow.yaml"
-      description: "[SP] Generate or re-generate sprint-status.yaml from epic files (Required after Epics+Stories are created)"
+      description: Generate or re-generate sprint-status.yaml from epic files (Required after Epics+Stories are created)
 
-    - trigger: CS or create-story or fuzzy match on create story
+    - trigger: create-story
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-      description: "[CS] Create Story (Required to prepare stories for development)"
+      description: Create Story (Required to prepare stories for development)
 
-    - trigger: ER or epic-retrospective or fuzzy match on epic retrospective
+    # TODO: validate-create-story is not yet implemented
+    # The validate-workflow: handler type is not recognized by the workflow engine
+    # See: https://github.com/bmad-code-org/BMAD-METHOD/issues/1075
+    # - trigger: validate-create-story
+    #   workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/create-story/validate-workflow.yaml"
+    #   description: Validate Story (Highly Recommended, use fresh context and different LLM for best results)
+
+    - trigger: epic-retrospective
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
       data: "{project-root}/_bmad/_config/agent-manifest.csv"
-      description: "[ER] Facilitate team retrospective after an epic is completed (Optional)"
+      description: Facilitate team retrospective after an epic is completed (Optional)
 
-    - trigger: CC or correct-course or fuzzy match on correct course
+    - trigger: correct-course
       workflow: "{project-root}/_bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: "[CC] Execute correct-course task (When implementation is off-track)"
+      description: Execute correct-course task (When implementation is off-track)
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmm/agents/tea.agent.yaml

@@ -28,46 +28,43 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
-      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
-
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Master Test Architect"
-
-    - trigger: TF or test-framework or fuzzy match on test framework
+    - trigger: framework
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/framework/workflow.yaml"
-      description: "[TF] Initialize production-ready test framework architecture"
+      description: Initialize production-ready test framework architecture
 
-    - trigger: AT or atdd or fuzzy match on atdd
+    - trigger: atdd
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/atdd/workflow.yaml"
-      description: "[AT] Generate E2E tests first, before starting implementation"
+      description: Generate E2E tests first, before starting implementation
 
-    - trigger: TA or test-automate or fuzzy match on test automate
+    - trigger: automate
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/automate/workflow.yaml"
-      description: "[TA] Generate comprehensive test automation"
+      description: Generate comprehensive test automation
 
-    - trigger: TD or test-design or fuzzy match on test design
+    - trigger: test-design
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-design/workflow.yaml"
-      description: "[TD] Create comprehensive test scenarios"
+      description: Create comprehensive test scenarios
 
-    - trigger: TR or test-trace or fuzzy match on test trace
+    - trigger: trace
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/trace/workflow.yaml"
-      description: "[TR] Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)"
+      description: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)
 
-    - trigger: NR or nfr-assess or fuzzy match on nfr assess
+    - trigger: nfr-assess
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
-      description: "[NR] Validate non-functional requirements"
+      description: Validate non-functional requirements
 
-    - trigger: CI or ci or fuzzy match on ci
+    - trigger: ci
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/ci/workflow.yaml"
-      description: "[CI] Scaffold CI/CD quality pipeline"
+      description: Scaffold CI/CD quality pipeline
 
-    - trigger: RV or test-review or fuzzy match on test review
+    - trigger: test-review
       workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-review/workflow.yaml"
-      description: "[RV] Review test quality using comprehensive knowledge base and best practices"
+      description: Review test quality using comprehensive knowledge base and best practices
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmm/agents/tech-writer.agent.yaml

@@ -21,42 +21,47 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
-      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
-
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the Technical Writer"
-
-    - trigger: DP or document-project or fuzzy match on document project
+    - trigger: document-project
       workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
-      description: "[DP] Comprehensive project documentation (brownfield analysis, architecture scanning)"
+      description: Comprehensive project documentation (brownfield analysis, architecture scanning)
 
-    - trigger: MG or mermaid-gen or fuzzy match on mermaid
+    - trigger: generate-mermaid
       action: "Create a Mermaid diagram based on user description. Ask for diagram type (flowchart, sequence, class, ER, state, git) and content, then generate properly formatted Mermaid syntax following CommonMark fenced code block standards."
-      description: "[MG] Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)"
+      description: Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
 
-    - trigger: EF or excalidraw-flowchart or fuzzy match on excalidraw flowchart
+    - trigger: create-excalidraw-flowchart
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-flowchart/workflow.yaml"
-      description: "[EF] Create Excalidraw flowchart for processes and logic flows"
+      description: Create Excalidraw flowchart for processes and logic flows
 
-    - trigger: ED or excalidraw-diagram or fuzzy match on excalidraw diagram
+    - trigger: create-excalidraw-diagram
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-diagram/workflow.yaml"
-      description: "[ED] Create Excalidraw system architecture or technical diagram"
+      description: Create Excalidraw system architecture or technical diagram
 
-    - trigger: DF or dataflow or fuzzy match on dataflow
+    - trigger: create-excalidraw-dataflow
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-dataflow/workflow.yaml"
-      description: "[DF] Create Excalidraw data flow diagram"
+      description: Create Excalidraw data flow diagram
 
-    - trigger: VD or validate-doc or fuzzy match on validate doc
+    - trigger: validate-doc
       action: "Review the specified document against CommonMark standards, technical writing best practices, and style guide compliance. Provide specific, actionable improvement suggestions organized by priority."
-      description: "[VD] Validate documentation against standards and best practices"
+      description: Validate documentation against standards and best practices
 
-    - trigger: EC or explain-concept or fuzzy match on explain concept
+    - trigger: improve-readme
+      action: "Analyze the current README file and suggest improvements for clarity, completeness, and structure. Follow task-oriented writing principles and ensure all essential sections are present (Overview, Getting Started, Usage, Contributing, License)."
+      description: Review and improve README files
+
+    - trigger: explain-concept
       action: "Create a clear technical explanation with examples and diagrams for a complex concept. Break it down into digestible sections using task-oriented approach. Include code examples and Mermaid diagrams where helpful."
-      description: "[EC] Create clear technical explanations with examples"
+      description: Create clear technical explanations with examples
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: standards-guide
+      action: "Display the complete documentation standards from {project-root}/_bmad/bmm/data/documentation-standards.md in a clear, formatted way for the user."
+      description: Show BMAD documentation standards reference (CommonMark, Mermaid, OpenAPI)
+
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmm/agents/ux-designer.agent.yaml

@@ -23,22 +23,26 @@ agent:
     - "Find if this exists, if it does, always treat it as the bible I plan and execute against: `**/project-context.md`"
 
   menu:
-    - trigger: WS or workflow-status or fuzzy match on workflow status
-      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: "[WS] Get workflow status or initialize a workflow if not already done (optional)"
-
-    - trigger: CH or fuzzy match on chat
-      action: agent responds as expert based on its persona to converse
-      description: "[CH] Chat with the UX Designer"
-
-    - trigger: UX or ux-design or fuzzy match on ux design
+    - trigger: create-ux-design
       exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
-      description: "[UX] Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)"
+      description: Generate a UX Design and UI Plan from a PRD (Recommended before creating Architecture)
 
-    - trigger: XW or wireframe or fuzzy match on wireframe
+    # TODO: validate-design is not yet implemented
+    # The validate-workflow: handler type is not recognized by the workflow engine
+    # See: https://github.com/bmad-code-org/BMAD-METHOD/issues/1075
+    # - trigger: validate-design
+    #   workflow: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/validate-workflow.yaml"
+    #   description: Validate UX Specification and Design Artifacts
+
+    - trigger: create-excalidraw-wireframe
       workflow: "{project-root}/_bmad/bmm/workflows/excalidraw-diagrams/create-wireframe/workflow.yaml"
-      description: "[XW] Create website or app wireframe (Excalidraw)"
+      description: Create website or app wireframe (Excalidraw)
 
-    - trigger: PS or party-mode or fuzzy match on party mode
+    - trigger: party-mode
       exec: "{project-root}/_bmad/core/workflows/party-mode/workflow.md"
-      description: "[PS] Bring the whole team in to chat with other expert agents from the party"
+      description: Bring the whole team in to chat with other expert agents from the party
+
+    - trigger: advanced-elicitation
+      exec: "{project-root}/_bmad/core/tasks/advanced-elicitation.xml"
+      description: Advanced elicitation techniques to challenge the LLM to get better results
+      web-only: true

src/modules/bmm/docs/brownfield-guide.md

@@ -726,7 +726,7 @@ flowchart TD
 - **[Glossary](./glossary.md)** - Key terminology
 - **[FAQ](./faq.md)** - Common questions
 - **[Troubleshooting](./troubleshooting.md)** - Problem resolution
-- **[Workflow Documentation](./README.md#-workflow-guides)** - Complete workflow reference
+- **[Workflow Documentation](./index.md#-workflow-guides)** - Complete workflow reference
 
 ---
 

src/modules/bmm/docs/enterprise-agentic-development.md

@@ -678,7 +678,7 @@ PMs write BMad PRDs → Stories auto-fed to cloud AI agents → Parallel impleme
 - [FAQ](./faq.md) - Common questions
 - [Scale Adaptive System](./scale-adaptive-system.md) - Project levels explained
 - [Quick Start Guide](./quick-start.md) - Getting started
-- [Workflow Documentation](./README.md#-workflow-guides) - Complete workflow reference
+- [Workflow Documentation](./index.md#-workflow-guides) - Complete workflow reference
 - [Agents Guide](./agents-guide.md) - Understanding BMad agents
 
 ---

src/modules/bmm/docs/faq.md

@@ -0,0 +1,542 @@
+# BMM Frequently Asked Questions
+
+Quick answers to common questions about the BMad Method Module.
+
+---
+
+## Table of Contents
+
+- [Getting Started](#getting-started)
+- [Choosing the Right Level](#choosing-the-right-level)
+- [Workflows and Phases](#workflows-and-phases)
+- [Planning Documents](#planning-documents)
+- [Implementation](#implementation)
+- [Brownfield Development](#brownfield-development)
+- [Tools and Technical](#tools-and-technical)
+
+---
+
+## Getting Started
+
+### Q: Do I always need to run workflow-init?
+
+**A:** No, once you learn the flow you can go directly to workflows. However, workflow-init is helpful because it:
+
+- Determines your project's appropriate level automatically
+- Creates the tracking status file
+- Routes you to the correct starting workflow
+
+For experienced users: use the [Quick Reference](./quick-start.md#quick-reference-agent-document-mapping) to go directly to the right agent/workflow.
+
+### Q: Why do I need fresh chats for each workflow?
+
+**A:** Context-intensive workflows (like brainstorming, PRD creation, architecture design) can cause AI hallucinations if run in sequence within the same chat. Starting fresh ensures the agent has maximum context capacity for each workflow. This is particularly important for:
+
+- Planning workflows (PRD, architecture)
+- Analysis workflows (brainstorming, research)
+- Complex story implementation
+
+Quick workflows like status checks can reuse chats safely.
+
+### Q: Can I skip workflow-status and just start working?
+
+**A:** Yes, if you already know your project level and which workflow comes next. workflow-status is mainly useful for:
+
+- New projects (guides initial setup)
+- When you're unsure what to do next
+- After breaks in work (reminds you where you left off)
+- Checking overall progress
+
+### Q: What's the minimum I need to get started?
+
+**A:** For the fastest path:
+
+1. Install BMad Method: `npx bmad-method@alpha install`
+2. For small changes: Load PM agent → run tech-spec → implement
+3. For larger projects: Load PM agent → run prd → architect → implement
+
+### Q: How do I know if I'm in Phase 1, 2, 3, or 4?
+
+**A:** Check your `bmm-workflow-status.md` file (created by workflow-init). It shows your current phase and progress. If you don't have this file, you can also tell by what you're working on:
+
+- **Phase 1** - Brainstorming, research, product brief (optional)
+- **Phase 2** - Creating either a PRD or tech-spec (always required)
+- **Phase 3** - Architecture design (Level 2-4 only)
+- **Phase 4** - Actually writing code, implementing stories
+
+---
+
+## Choosing the Right Level
+
+### Q: How do I know which level my project is?
+
+**A:** Use workflow-init for automatic detection, or self-assess using these keywords:
+
+- **Level 0:** "fix", "bug", "typo", "small change", "patch" → 1 story
+- **Level 1:** "simple", "basic", "small feature", "add" → 2-10 stories
+- **Level 2:** "dashboard", "several features", "admin panel" → 5-15 stories
+- **Level 3:** "platform", "integration", "complex", "system" → 12-40 stories
+- **Level 4:** "enterprise", "multi-tenant", "multiple products" → 40+ stories
+
+When in doubt, start smaller. You can always run create-prd later if needed.
+
+### Q: Can I change levels mid-project?
+
+**A:** Yes! If you started at Level 1 but realize it's Level 2, you can run create-prd to add proper planning docs. The system is flexible - your initial level choice isn't permanent.
+
+### Q: What if workflow-init suggests the wrong level?
+
+**A:** You can override it! workflow-init suggests a level but always asks for confirmation. If you disagree, just say so and choose the level you think is appropriate. Trust your judgment.
+
+### Q: Do I always need architecture for Level 2?
+
+**A:** No, architecture is **optional** for Level 2. Only create architecture if you need system-level design. Many Level 2 projects work fine with just PRD created during planning.
+
+### Q: What's the difference between Level 1 and Level 2?
+
+**A:**
+
+- **Level 1:** 1-10 stories, uses tech-spec (simpler, faster), no architecture
+- **Level 2:** 5-15 stories, uses PRD (product-focused), optional architecture
+
+The overlap (5-10 stories) is intentional. Choose based on:
+
+- Need product-level planning? → Level 2
+- Just need technical plan? → Level 1
+- Multiple epics? → Level 2
+- Single epic? → Level 1
+
+---
+
+## Workflows and Phases
+
+### Q: What's the difference between workflow-status and workflow-init?
+
+**A:**
+
+- **workflow-status:** Checks existing status and tells you what's next (use when continuing work)
+- **workflow-init:** Creates new status file and sets up project (use when starting new project)
+
+If status file exists, use workflow-status. If not, use workflow-init.
+
+### Q: Can I skip Phase 1 (Analysis)?
+
+**A:** Yes! Phase 1 is optional for all levels, though recommended for complex projects. Skip if:
+
+- Requirements are clear
+- No research needed
+- Time-sensitive work
+- Small changes (Level 0-1)
+
+### Q: When is Phase 3 (Architecture) required?
+
+**A:**
+
+- **Level 0-1:** Never (skip entirely)
+- **Level 2:** Optional (only if system design needed)
+- **Level 3-4:** Required (comprehensive architecture mandatory)
+
+### Q: What happens if I skip a recommended workflow?
+
+**A:** Nothing breaks! Workflows are guidance, not enforcement. However, skipping recommended workflows (like architecture for Level 3) may cause:
+
+- Integration issues during implementation
+- Rework due to poor planning
+- Conflicting design decisions
+- Longer development time overall
+
+### Q: How do I know when Phase 3 is complete and I can start Phase 4?
+
+**A:** For Level 3-4, run the implementation-readiness workflow. It validates PRD + Architecture + Epics + UX (optional) are aligned before implementation. Pass the gate check = ready for Phase 4.
+
+### Q: Can I run workflows in parallel or do they have to be sequential?
+
+**A:** Most workflows must be sequential within a phase:
+
+- Phase 1: brainstorm → research → product-brief (optional order)
+- Phase 2: PRD must complete before moving forward
+- Phase 3: architecture → epics+stories → implementation-readiness (sequential)
+- Phase 4: Stories within an epic should generally be sequential, but stories in different epics can be parallel if you have capacity
+
+---
+
+## Planning Documents
+
+### Q: Why no tech-spec at Level 2+?
+
+**A:** Level 2+ projects need product-level planning (PRD) and system-level design (Architecture), which tech-spec doesn't provide. Tech-spec is too narrow for coordinating multiple features. Instead, Level 2-4 uses:
+
+- PRD (product vision, functional requirements, non-functional requirements)
+- Architecture (system design)
+- Epics+Stories (created AFTER architecture is complete)
+
+### Q: Do I need a PRD for a bug fix?
+
+**A:** No! Bug fixes are typically Level 0 (single atomic change). Use Quick Spec Flow:
+
+- Load PM agent
+- Run tech-spec workflow
+- Implement immediately
+
+PRDs are for Level 2-4 projects with multiple features requiring product-level coordination.
+
+### Q: Can I skip the product brief?
+
+**A:** Yes, product brief is always optional. It's most valuable for:
+
+- Level 3-4 projects needing strategic direction
+- Projects with stakeholders requiring alignment
+- Novel products needing market research
+- When you want to explore solution space before committing
+
+---
+
+## Implementation
+
+### Q: Does create-story include implementation context?
+
+**A:** Yes! The create-story workflow generates story files that include implementation-specific guidance, references existing patterns from your documentation, and provides technical context. The workflow loads your architecture, PRD, and existing project documentation to create comprehensive stories. For Quick Flow projects using tech-spec, the tech-spec itself is already comprehensive, so stories can be simpler.
+
+### Q: How do I mark a story as done?
+
+**A:** After dev-story completes and code-review passes:
+
+1. Open `sprint-status.yaml` (created by sprint-planning)
+2. Change the story status from `review` to `done`
+3. Save the file
+
+### Q: Can I work on multiple stories at once?
+
+**A:** Yes, if you have capacity! Stories within different epics can be worked in parallel. However, stories within the same epic are usually sequential because they build on each other.
+
+### Q: What if my story takes longer than estimated?
+
+**A:** That's normal! Stories are estimates. If implementation reveals more complexity:
+
+1. Continue working until DoD is met
+2. Consider if story should be split
+3. Document learnings in retrospective
+4. Adjust future estimates based on this learning
+
+### Q: When should I run retrospective?
+
+**A:** After completing all stories in an epic (when epic is done). Retrospectives capture:
+
+- What went well
+- What could improve
+- Technical insights
+- Learnings for future epics
+
+Don't wait until project end - run after each epic for continuous improvement.
+
+---
+
+## Brownfield Development
+
+### Q: What is brownfield vs greenfield?
+
+**A:**
+
+- **Greenfield:** New project, starting from scratch, clean slate
+- **Brownfield:** Existing project, working with established codebase and patterns
+
+### Q: Do I have to run document-project for brownfield?
+
+**A:** Highly recommended, especially if:
+
+- No existing documentation
+- Documentation is outdated
+- AI agents need context about existing code
+- Level 2-4 complexity
+
+You can skip it if you have comprehensive, up-to-date documentation including `docs/index.md`.
+
+### Q: What if I forget to run document-project on brownfield?
+
+**A:** Workflows will lack context about existing code. You may get:
+
+- Suggestions that don't match existing patterns
+- Integration approaches that miss existing APIs
+- Architecture that conflicts with current structure
+
+Run document-project and restart planning with proper context.
+
+### Q: Can I use Quick Spec Flow for brownfield projects?
+
+**A:** Yes! Quick Spec Flow works great for brownfield. It will:
+
+- Auto-detect your existing stack
+- Analyze brownfield code patterns
+- Detect conventions and ask for confirmation
+- Generate context-rich tech-spec that respects existing code
+
+Perfect for bug fixes and small features in existing codebases.
+
+### Q: How does workflow-init handle brownfield with old planning docs?
+
+**A:** workflow-init asks about YOUR current work first, then uses old artifacts as context:
+
+1. Shows what it found (old PRD, epics, etc.)
+2. Asks: "Is this work in progress, previous effort, or proposed work?"
+3. If previous effort: Asks you to describe your NEW work
+4. Determines level based on YOUR work, not old artifacts
+
+This prevents old Level 3 PRDs from forcing Level 3 workflow for new Level 0 bug fix.
+
+### Q: What if my existing code doesn't follow best practices?
+
+**A:** Quick Spec Flow detects your conventions and asks: "Should I follow these existing conventions?" You decide:
+
+- **Yes** → Maintain consistency with current codebase
+- **No** → Establish new standards (document why in tech-spec)
+
+BMM respects your choice - it won't force modernization, but it will offer it.
+
+---
+
+## Tools and Technical
+
+### Q: Why are my Mermaid diagrams not rendering?
+
+**A:** Common issues:
+
+1. Missing language tag: Use ` ```mermaid` not just ` ``` `
+2. Syntax errors in diagram (validate at mermaid.live)
+3. Tool doesn't support Mermaid (check your Markdown renderer)
+
+All BMM docs use valid Mermaid syntax that should render in GitHub, VS Code, and most IDEs.
+
+### Q: Can I use BMM with GitHub Copilot / Cursor / other AI tools?
+
+**A:** Yes! BMM is complementary. BMM handles:
+
+- Project planning and structure
+- Workflow orchestration
+- Agent Personas and expertise
+- Documentation generation
+- Quality gates
+
+Your AI coding assistant handles:
+
+- Line-by-line code completion
+- Quick refactoring
+- Test generation
+
+Use them together for best results.
+
+### Q: What IDEs/tools support BMM?
+
+**A:** BMM requires tools with **agent mode** and access to **high-quality LLM models** that can load and follow complex workflows, then properly implement code changes.
+
+**Recommended Tools:**
+
+- **Claude Code** ⭐ **Best choice**
+  - Sonnet 4.5 (excellent workflow following, coding, reasoning)
+  - Opus (maximum context, complex planning)
+  - Native agent mode designed for BMM workflows
+
+- **Cursor**
+  - Supports Anthropic (Claude) and OpenAI models
+  - Agent mode with composer
+  - Good for developers who prefer Cursor's UX
+
+- **Windsurf**
+  - Multi-model support
+  - Agent capabilities
+  - Suitable for BMM workflows
+
+**What Matters:**
+
+1. **Agent mode** - Can load long workflow instructions and maintain context
+2. **High-quality LLM** - Models ranked high on SWE-bench (coding benchmarks)
+3. **Model selection** - Access to Claude Sonnet 4.5, Opus, or GPT-4o class models
+4. **Context capacity** - Can handle large planning documents and codebases
+
+**Why model quality matters:** BMM workflows require LLMs that can follow multi-step processes, maintain context across phases, and implement code that adheres to specifications. Tools with weaker models will struggle with workflow adherence and code quality.
+
+See [IDE Setup Guides](https://github.com/bmad-code-org/BMAD-METHOD/tree/main/docs/ide-info) for configuration specifics.
+
+### Q: Can I customize agents?
+
+**A:** Yes! Agents are installed as markdown files with XML-style content (optimized for LLMs, readable by any model). Create customization files in `_bmad/_config/agents/[agent-name].customize.yaml` to override default behaviors while keeping core functionality intact. See agent documentation for customization options.
+
+**Note:** While source agents in this repo are YAML, they install as `.md` files with XML-style tags - a format any LLM can read and follow.
+
+### Q: What happens to my planning docs after implementation?
+
+**A:** Keep them! They serve as:
+
+- Historical record of decisions
+- Onboarding material for new team members
+- Reference for future enhancements
+- Audit trail for compliance
+
+For enterprise projects (Level 4), consider archiving completed planning artifacts to keep workspace clean.
+
+### Q: Can I use BMM for non-software projects?
+
+**A:** BMM is optimized for software development, but the methodology principles (scale-adaptive planning, just-in-time design, context injection) can apply to other complex project types. You'd need to adapt workflows and agents for your domain.
+
+---
+
+## Advanced Questions
+
+### Q: What if my project grows from Level 1 to Level 3?
+
+**A:** Totally fine! When you realize scope has grown:
+
+1. Run create-prd to add product-level planning
+2. Run create-architecture for system design
+3. Use existing tech-spec as input for PRD
+4. Continue with updated level
+
+The system is flexible - growth is expected.
+
+### Q: Can I mix greenfield and brownfield approaches?
+
+**A:** Yes! Common scenario: adding new greenfield feature to brownfield codebase. Approach:
+
+1. Run document-project for brownfield context
+2. Use greenfield workflows for new feature planning
+3. Explicitly document integration points between new and existing
+4. Test integration thoroughly
+
+### Q: How do I handle urgent hotfixes during a sprint?
+
+**A:** Use correct-course workflow or just:
+
+1. Save your current work state
+2. Load PM agent → quick tech-spec for hotfix
+3. Implement hotfix (Level 0 flow)
+4. Deploy hotfix
+5. Return to original sprint work
+
+Level 0 Quick Spec Flow is perfect for urgent fixes.
+
+### Q: What if I disagree with the workflow's recommendations?
+
+**A:** Workflows are guidance, not enforcement. If a workflow recommends something that doesn't make sense for your context:
+
+- Explain your reasoning to the agent
+- Ask for alternative approaches
+- Skip the recommendation if you're confident
+- Document why you deviated (for future reference)
+
+Trust your expertise - BMM supports your decisions.
+
+### Q: Can multiple developers work on the same BMM project?
+
+**A:** Yes! But the paradigm is fundamentally different from traditional agile teams.
+
+**Key Difference:**
+
+- **Traditional:** Multiple devs work on stories within one epic (months)
+- **Agentic:** Each dev owns complete epics (days)
+
+**In traditional agile:** A team of 5 devs might spend 2-3 months on a single epic, with each dev owning different stories.
+
+**With BMM + AI agents:** A single dev can complete an entire epic in 1-3 days. What used to take months now takes days.
+
+**Team Work Distribution:**
+
+- **Recommended:** Split work by **epic** (not story)
+- Each developer owns complete epics end-to-end
+- Parallel work happens at epic level
+- Minimal coordination needed
+
+**For full-stack apps:**
+
+- Frontend and backend can be separate epics (unusual in traditional agile)
+- Frontend dev owns all frontend epics
+- Backend dev owns all backend epics
+- Works because delivery is so fast
+
+**Enterprise Considerations:**
+
+- Use **git submodules** for BMM installation (not .gitignore)
+- Allows personal configurations without polluting main repo
+- Teams may use different AI tools (Claude Code, Cursor, etc.)
+- Developers may follow different methods or create custom agents/workflows
+
+**Quick Tips:**
+
+- Share `sprint-status.yaml` (single source of truth)
+- Assign entire epics to developers (not individual stories)
+- Coordinate at epic boundaries, not story level
+- Use git submodules for BMM in enterprise settings
+
+**For comprehensive coverage of enterprise team collaboration, work distribution strategies, git submodule setup, and velocity expectations, see:**
+
+👉 **[Enterprise Agentic Development Guide](./enterprise-agentic-development.md)**
+
+### Q: What is party mode and when should I use it?
+
+**A:** Party mode is a unique multi-agent collaboration feature where ALL your installed agents (19+ from BMM, CIS, BMB, custom modules) discuss your challenges together in real-time.
+
+**How it works:**
+
+1. Run `/bmad:core:workflows:party-mode` (or `*party-mode` from any agent)
+2. Introduce your topic
+3. BMad Master selects 2-3 most relevant agents per message
+4. Agents cross-talk, debate, and build on each other's ideas
+
+**Best for:**
+
+- Strategic decisions with trade-offs (architecture choices, tech stack, scope)
+- Creative brainstorming (game design, product innovation, UX ideation)
+- Cross-functional alignment (epic kickoffs, retrospectives, phase transitions)
+- Complex problem-solving (multi-faceted challenges, risk assessment)
+
+**Example parties:**
+
+- **Product Strategy:** PM + Innovation Strategist (CIS) + Analyst
+- **Technical Design:** Architect + Creative Problem Solver (CIS) + Game Architect
+- **User Experience:** UX Designer + Design Thinking Coach (CIS) + Storyteller (CIS)
+
+**Why it's powerful:**
+
+- Diverse perspectives (technical, creative, strategic)
+- Healthy debate reveals blind spots
+- Emergent insights from agent interaction
+- Natural collaboration across modules
+
+**For complete documentation:**
+
+👉 **[Party Mode Guide](./party-mode.md)** - How it works, when to use it, example compositions, best practices
+
+---
+
+## Getting Help
+
+### Q: Where do I get help if my question isn't answered here?
+
+**A:**
+
+1. Search [Complete Documentation](./README.md) for related topics
+2. Ask in [Discord Community](https://discord.gg/gk8jAdXWmj) (#general-dev)
+3. Open a [GitHub Issue](https://github.com/bmad-code-org/BMAD-METHOD/issues)
+4. Watch [YouTube Tutorials](https://www.youtube.com/@BMadCode)
+
+### Q: How do I report a bug or request a feature?
+
+**A:** Open a GitHub issue at: <https://github.com/bmad-code-org/BMAD-METHOD/issues>
+
+Please include:
+
+- BMM version (check your installed version)
+- Steps to reproduce (for bugs)
+- Expected vs actual behavior
+- Relevant workflow or agent involved
+
+---
+
+## Related Documentation
+
+- [Quick Start Guide](./quick-start.md) - Get started with BMM
+- [Glossary](./glossary.md) - Terminology reference
+- [Scale Adaptive System](./scale-adaptive-system.md) - Understanding levels
+- [Brownfield Guide](./brownfield-guide.md) - Existing codebase workflows
+
+---
+
+**Have a question not answered here?** Please [open an issue](https://github.com/bmad-code-org/BMAD-METHOD/issues) or ask in [Discord](https://discord.gg/gk8jAdXWmj) so we can add it!

src/modules/bmm/docs/glossary.md

@@ -0,0 +1,306 @@
+# BMM Glossary
+
+Comprehensive terminology reference for the BMad Method Module.
+
+---
+
+## Navigation
+
+- [Core Concepts](#core-concepts)
+- [Scale and Complexity](#scale-and-complexity)
+- [Planning Documents](#planning-documents)
+- [Workflow and Phases](#workflow-and-phases)
+- [Agents and Roles](#agents-and-roles)
+- [Status and Tracking](#status-and-tracking)
+- [Project Types](#project-types)
+- [Implementation Terms](#implementation-terms)
+
+---
+
+## Core Concepts
+
+### BMM (BMad Method Module)
+
+Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
+
+### BMad Method
+
+The complete methodology for AI-assisted software development, encompassing planning, architecture, implementation, and quality assurance workflows that adapt to project complexity.
+
+### Scale-Adaptive System
+
+BMad Method's intelligent workflow orchestration that automatically adjusts planning depth, documentation requirements, and implementation processes based on project needs through three distinct planning tracks (Quick Flow, BMad Method, Enterprise Method).
+
+### Agent
+
+A specialized AI persona with specific expertise (PM, Architect, SM, DEV, TEA) that guides users through workflows and creates deliverables. Agents have defined capabilities, communication styles, and workflow access.
+
+### Workflow
+
+A multi-step guided process that orchestrates AI agent activities to produce specific deliverables. Workflows are interactive and adapt to user context.
+
+---
+
+## Scale and Complexity
+
+### Quick Flow Track
+
+Fast implementation track using tech-spec planning only. Best for bug fixes, small features, and changes with clear scope. Typical range: 1-15 stories. No architecture phase needed. Examples: bug fixes, OAuth login, search features.
+
+### BMad Method Track
+
+Full product planning track using PRD + Architecture + UX. Best for products, platforms, and complex features requiring system design. Typical range: 10-50+ stories. Examples: admin dashboards, e-commerce platforms, SaaS products.
+
+### Enterprise Method Track
+
+Extended enterprise planning track adding Security Architecture, DevOps Strategy, and Test Strategy to BMad Method. Best for enterprise requirements, compliance needs, and multi-tenant systems. Typical range: 30+ stories. Examples: multi-tenant platforms, compliance-driven systems, mission-critical applications.
+
+### Planning Track
+
+The methodology path (Quick Flow, BMad Method, or Enterprise Method) chosen for a project based on planning needs, complexity, and requirements rather than story count alone.
+
+**Note:** Story counts are guidance, not definitions. Tracks are determined by what planning the project needs, not story math.
+
+---
+
+## Planning Documents
+
+### Tech-Spec (Technical Specification)
+
+**Quick Flow track only.** Comprehensive technical plan created upfront that serves as the primary planning document for small changes or features. Contains problem statement, solution approach, file-level changes, stack detection (brownfield), testing strategy, and developer resources.
+
+### PRD (Product Requirements Document)
+
+**BMad Method/Enterprise tracks.** Product-level planning document containing vision, goals, Functional Requirements (FRs), Non-Functional Requirements (NFRs), success criteria, and UX considerations. Replaces tech-spec for larger projects that need product planning. **V6 Note:** PRD focuses on WHAT to build (requirements). Epic+Stories are created separately AFTER architecture via create-epics-and-stories workflow.
+
+### Architecture Document
+
+**BMad Method/Enterprise tracks.** System-wide design document defining structure, components, interactions, data models, integration patterns, security, performance, and deployment.
+
+**Scale-Adaptive:** Architecture complexity scales with track - BMad Method is lightweight to moderate, Enterprise Method is comprehensive with security/devops/test strategies.
+
+### Epics
+
+High-level feature groupings that contain multiple related stories. Typically span 5-15 stories each and represent cohesive functionality (e.g., "User Authentication Epic").
+
+### Product Brief
+
+Optional strategic planning document created in Phase 1 (Analysis) that captures product vision, market context, user needs, and high-level requirements before detailed planning.
+
+### GDD (Game Design Document)
+
+Game development equivalent of PRD, created by Game Designer agent for game projects.
+
+---
+
+## Workflow and Phases
+
+### Phase 0: Documentation (Prerequisite)
+
+**Conditional phase for brownfield projects.** Creates comprehensive codebase documentation before planning. Only required if existing documentation is insufficient for AI agents.
+
+### Phase 1: Analysis (Optional)
+
+Discovery and research phase including brainstorming, research workflows, and product brief creation. Optional for Quick Flow, recommended for BMad Method, required for Enterprise Method.
+
+### Phase 2: Planning (Required)
+
+**Always required.** Creates formal requirements and work breakdown. Routes to tech-spec (Quick Flow) or PRD (BMad Method/Enterprise) based on selected track.
+
+### Phase 3: Solutioning (Track-Dependent)
+
+Architecture design phase. Required for BMad Method and Enterprise Method tracks. Includes architecture creation, validation, and gate checks.
+
+### Phase 4: Implementation (Required)
+
+Sprint-based development through story-by-story iteration. Uses sprint-planning, create-story, dev-story, code-review, and retrospective workflows.
+
+### Documentation (Prerequisite for Brownfield)
+
+**Conditional prerequisite for brownfield projects.** Creates comprehensive codebase documentation before planning. Only required if existing documentation is insufficient for AI agents. Uses the `document-project` workflow.
+
+### Quick Spec Flow
+
+Fast-track workflow system for Quick Flow track projects that goes straight from idea to tech-spec to implementation, bypassing heavy planning. Designed for bug fixes, small features, and rapid prototyping.
+
+---
+
+## Agents and Roles
+
+### PM (Product Manager)
+
+Agent responsible for creating PRDs, tech-specs, and managing product requirements. Primary agent for Phase 2 planning.
+
+### Analyst (Business Analyst)
+
+Agent that initializes workflows, conducts research, creates product briefs, and tracks progress. Often the entry point for new projects.
+
+### Architect
+
+Agent that designs system architecture, creates architecture documents, performs technical reviews, and validates designs. Primary agent for Phase 3 solutioning.
+
+### SM (Scrum Master)
+
+Agent that manages sprints, creates stories, generates contexts, and coordinates implementation. Primary orchestrator for Phase 4 implementation.
+
+### DEV (Developer)
+
+Agent that implements stories, writes code, runs tests, and performs code reviews. Primary implementer in Phase 4.
+
+### TEA (Test Architect)
+
+Agent responsible for test strategy, quality gates, NFR assessment, and comprehensive quality assurance. Integrates throughout all phases.
+
+### Technical Writer
+
+Agent specialized in creating and maintaining high-quality technical documentation. Expert in documentation standards, information architecture, and professional technical writing. The agent's internal name is "paige" but is presented as "Technical Writer" to users.
+
+### UX Designer
+
+Agent that creates UX design documents, interaction patterns, and visual specifications for UI-heavy projects.
+
+### Game Designer
+
+Specialized agent for game development projects. Creates game design documents (GDD) and game-specific workflows.
+
+### BMad Master
+
+Meta-level orchestrator agent from BMad Core. Facilitates party mode, lists available tasks and workflows, and provides high-level guidance across all modules.
+
+### Party Mode
+
+Multi-agent collaboration feature where all installed agents (19+ from BMM, CIS, BMB, custom modules) discuss challenges together in real-time. BMad Master orchestrates, selecting 2-3 relevant agents per message for natural cross-talk and debate. Best for strategic decisions, creative brainstorming, cross-functional alignment, and complex problem-solving. See [Party Mode Guide](./party-mode.md).
+
+---
+
+## Status and Tracking
+
+### bmm-workflow-status.yaml
+
+**Phases 1-3.** Tracking file that shows current phase, completed workflows, progress, and next recommended actions. Created by workflow-init, updated automatically.
+
+### sprint-status.yaml
+
+**Phase 4 only.** Single source of truth for implementation tracking. Contains all epics, stories, and retrospectives with current status for each. Created by sprint-planning, updated by agents.
+
+### Story Status Progression
+
+```
+backlog → ready-for-dev → in-progress → review → done
+```
+
+- **backlog** - Story exists in epic but not yet created
+- **ready-for-dev** - Story file created via create-story; validation is optional (run `validate-create-story` for quality check before dev picks it up)
+- **in-progress** - DEV is implementing via dev-story
+- **review** - Implementation complete, awaiting code-review
+- **done** - Completed with DoD met
+
+### Epic Status Progression
+
+```
+backlog → in-progress → done
+```
+
+- **backlog** - Epic not yet started
+- **in-progress** - Epic actively being worked on
+- **done** - All stories in epic completed
+
+### Retrospective
+
+Workflow run after completing each epic to capture learnings, identify improvements, and feed insights into next epic planning. Critical for continuous improvement.
+
+---
+
+## Project Types
+
+### Greenfield
+
+New project starting from scratch with no existing codebase. Freedom to establish patterns, choose stack, and design from clean slate.
+
+### Brownfield
+
+Existing project with established codebase, patterns, and constraints. Requires understanding existing architecture, respecting established conventions, and planning integration with current systems.
+
+**Critical:** Brownfield projects should run document-project workflow BEFORE planning to ensure AI agents have adequate context about existing code.
+
+### document-project Workflow
+
+**Brownfield prerequisite.** Analyzes and documents existing codebase, creating comprehensive documentation including project overview, architecture analysis, source tree, API contracts, and data models. Three scan levels: quick, deep, exhaustive.
+
+---
+
+## Implementation Terms
+
+### Story
+
+Single unit of implementable work with clear acceptance criteria, typically 2-8 hours of development effort. Stories are grouped into epics and tracked in sprint-status.yaml.
+
+### Story File
+
+Markdown file containing story details: description, acceptance criteria, technical notes, dependencies, implementation guidance, and testing requirements.
+
+### Story Context
+
+Implementation guidance embedded within story files during the create-story workflow. Provides implementation-specific context, references existing patterns, suggests approaches, and helps maintain consistency with established codebase conventions.
+
+### Sprint Planning
+
+Workflow that initializes Phase 4 implementation by creating sprint-status.yaml, extracting all epics/stories from planning docs, and setting up tracking infrastructure.
+
+### Gate Check
+
+Validation workflow (implementation-readiness) run before Phase 4 to ensure PRD + Architecture + Epics + UX (optional) are aligned with no gaps or contradictions. Required for BMad Method and Enterprise Method tracks.
+
+### DoD (Definition of Done)
+
+Criteria that must be met before marking a story as done. Typically includes: implementation complete, tests written and passing, code reviewed, documentation updated, and acceptance criteria validated.
+
+### Shard / Sharding
+
+**For runtime LLM optimization only (NOT human docs).** Splitting large planning documents (PRD, epics, architecture) into smaller section-based files to improve workflow efficiency. Phase 1-3 workflows load entire sharded documents transparently. Phase 4 workflows selectively load only needed sections for massive token savings.
+
+---
+
+## Additional Terms
+
+### Workflow Status
+
+Universal entry point workflow that checks for existing status file, displays current phase/progress, and recommends next action based on project state.
+
+### Workflow Init
+
+Initialization workflow that creates bmm-workflow-status.yaml, detects greenfield vs brownfield, determines planning track, and sets up appropriate workflow path.
+
+### Track Selection
+
+Automatic analysis by workflow-init that uses keyword analysis, complexity indicators, and project requirements to suggest appropriate track (Quick Flow, BMad Method, or Enterprise Method). User can override suggested track.
+
+### Correct Course
+
+Workflow run during Phase 4 when significant changes or issues arise. Analyzes impact, proposes solutions, and routes to appropriate remediation workflows.
+
+### Migration Strategy
+
+Plan for handling changes to existing data, schemas, APIs, or patterns during brownfield development. Critical for ensuring backward compatibility and smooth rollout.
+
+### Feature Flags
+
+Implementation technique for brownfield projects that allows gradual rollout of new functionality, easy rollback, and A/B testing. Recommended for BMad Method and Enterprise brownfield changes.
+
+### Integration Points
+
+Specific locations where new code connects with existing systems. Must be documented explicitly in brownfield tech-specs and architectures.
+
+### Convention Detection
+
+Quick Spec Flow feature that automatically detects existing code style, naming conventions, patterns, and frameworks from brownfield codebases, then asks user to confirm before proceeding.
+
+---
+
+## Related Documentation
+
+- [Quick Start Guide](./quick-start.md) - Learn BMM basics
+- [Scale Adaptive System](./scale-adaptive-system.md) - Deep dive on tracks and complexity
+- [Brownfield Guide](./brownfield-guide.md) - Working with existing codebases
+- [Quick Spec Flow](./quick-spec-flow.md) - Fast-track for Quick Flow track
+- [FAQ](./faq.md) - Common questions

src/modules/bmm/docs/party-mode.md

@@ -171,7 +171,7 @@ Party mode can include **19+ agents** from all installed modules:
 
 **CIS (5 agents):** Brainstorming Coach, Creative Problem Solver, Design Thinking Coach, Innovation Strategist, Storyteller
 
-**BMB (3 agents):** Agent, Workflow, and Module Expert Agents
+**BMB (1 agent):** BMad Builder
 
 **Core (1 agent):** BMad Master (orchestrator)
 

src/modules/bmm/docs/quick-spec-flow.md

@@ -629,7 +629,7 @@ Quick Spec Flow is your **fast path from idea to implementation** for:
 ## Next Steps
 
 - **Try it now:** Load PM agent and describe a small change
-- **Learn more:** See the [BMM Workflow Guides](./README.md#-workflow-guides) for comprehensive workflow documentation
+- **Learn more:** See the [BMM Workflow Guides](./index.md#-workflow-guides) for comprehensive workflow documentation
 - **Need help deciding?** Run `workflow-init` to get a recommendation
 - **Have questions?** Join us on Discord: <https://discord.gg/gk8jAdXWmj>
 

src/modules/bmm/docs/quick-start.md

@@ -350,7 +350,7 @@ A: Yes, once you learn the flow. Use the Quick Reference in Step 2 to go directl
 
 - **During workflows**: Agents guide you with questions and explanations
 - **Community**: [Discord](https://discord.gg/gk8jAdXWmj) - #general-dev, #bugs-issues
-- **Complete guide**: [BMM Workflow Documentation](./README.md#-workflow-guides)
+- **Complete guide**: [BMM Workflow Documentation](./index.md#-workflow-guides)
 - **YouTube tutorials**: [BMad Code Channel](https://www.youtube.com/@BMadCode)
 
 ---

src/modules/bmm/docs/scale-adaptive-system.md

@@ -611,7 +611,7 @@ Run `workflow-init` on existing projects to migrate to new tracking system. It d
 - **[Brownfield Guide](./brownfield-guide.md)** - Existing codebase workflows
 - **[Glossary](./glossary.md)** - Complete terminology
 - **[FAQ](./faq.md)** - Common questions
-- **[Workflows Guide](./README.md#-workflow-guides)** - Complete workflow reference
+- **[Workflows Guide](./index.md#-workflow-guides)** - Complete workflow reference
 
 ---
 

src/modules/bmm/docs/test-architecture.md

@@ -440,15 +440,15 @@ Provides fixture-based utilities that integrate into TEA's test generation and r
 
 <br></br>
 
-| Command        | Workflow README                                   | Primary Outputs                                                                               | Notes                                                | With Playwright MCP Enhancements                                                                             |
-| -------------- | ------------------------------------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| `*framework`   | [📖](../workflows/testarch/framework/README.md)   | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs                           | Use when no production-ready harness exists          | -                                                                                                            |
-| `*ci`          | [📖](../workflows/testarch/ci/README.md)          | CI workflow, selective test scripts, secrets checklist                                        | Platform-aware (GitHub Actions default)              | -                                                                                                            |
-| `*test-design` | [📖](../workflows/testarch/test-design/README.md) | Combined risk assessment, mitigation plan, and coverage strategy                              | Risk scoring + optional exploratory mode             | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)           |
-| `*atdd`        | [📖](../workflows/testarch/atdd/README.md)        | Failing acceptance tests + implementation checklist                                           | TDD red phase + optional recording mode              | **+ Recording**: AI generation verified with live browser (accurate selectors from real DOM)                 |
-| `*automate`    | [📖](../workflows/testarch/automate/README.md)    | Prioritized specs, fixtures, README/script updates, DoD summary                               | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Pattern fixes enhanced with visual debugging + **+ Recording**: AI verified with live browser |
-| `*test-review` | [📖](../workflows/testarch/test-review/README.md) | Test quality review report with 0-100 score, violations, fixes                                | Reviews tests against knowledge base patterns        | -                                                                                                            |
-| `*nfr-assess`  | [📖](../workflows/testarch/nfr-assess/README.md)  | NFR assessment report with actions                                                            | Focus on security/performance/reliability            | -                                                                                                            |
-| `*trace`       | [📖](../workflows/testarch/trace/README.md)       | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision     | -                                                                                                            |
+| Command        | Workflow README                                         | Primary Outputs                                                                               | Notes                                                | With Playwright MCP Enhancements                                                                             |
+| -------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
+| `*framework`   | [📖](../workflows/testarch/framework/instructions.md)   | Playwright/Cypress scaffold, `.env.example`, `.nvmrc`, sample specs                           | Use when no production-ready harness exists          | -                                                                                                            |
+| `*ci`          | [📖](../workflows/testarch/ci/instructions.md)          | CI workflow, selective test scripts, secrets checklist                                        | Platform-aware (GitHub Actions default)              | -                                                                                                            |
+| `*test-design` | [📖](../workflows/testarch/test-design/instructions.md) | Combined risk assessment, mitigation plan, and coverage strategy                              | Risk scoring + optional exploratory mode             | **+ Exploratory**: Interactive UI discovery with browser automation (uncover actual functionality)           |
+| `*atdd`        | [📖](../workflows/testarch/atdd/instructions.md)        | Failing acceptance tests + implementation checklist                                           | TDD red phase + optional recording mode              | **+ Recording**: AI generation verified with live browser (accurate selectors from real DOM)                 |
+| `*automate`    | [📖](../workflows/testarch/automate/instructions.md)    | Prioritized specs, fixtures, README/script updates, DoD summary                               | Optional healing/recording, avoid duplicate coverage | **+ Healing**: Pattern fixes enhanced with visual debugging + **+ Recording**: AI verified with live browser |
+| `*test-review` | [📖](../workflows/testarch/test-review/instructions.md) | Test quality review report with 0-100 score, violations, fixes                                | Reviews tests against knowledge base patterns        | -                                                                                                            |
+| `*nfr-assess`  | [📖](../workflows/testarch/nfr-assess/instructions.md)  | NFR assessment report with actions                                                            | Focus on security/performance/reliability            | -                                                                                                            |
+| `*trace`       | [📖](../workflows/testarch/trace/instructions.md)       | Phase 1: Coverage matrix, recommendations. Phase 2: Gate decision (PASS/CONCERNS/FAIL/WAIVED) | Two-phase workflow: traceability + gate decision     | -                                                                                                            |
 
 **📖** = Click to view detailed workflow documentation