bmad-method 6.0.0-alpha.21 → 6.0.0-alpha.23

package/{src/modules/bmm/docs/agents-guide.md → docs/reference/agents/index.md}

@@ -1,98 +1,91 @@
-# BMM Agents Reference
+---
+title: "Agents Reference"
+description: Complete reference for BMad Method agents and their commands
+---
 
-Quick reference of what each agent can do based on their available commands.
+
+Quick reference of all BMad Method agents and their available commands.
 
 ---
 
-## Analyst (Mary) | `/bmad:bmm:agents:analyst`
+## Analyst (Mary)
 
 Business analysis and research.
 
-**Capabilities:**
-
+**Commands:**
 - `*workflow-status` - Get workflow status or initialize tracking
 - `*brainstorm-project` - Guided brainstorming session
 - `*research` - Market, domain, competitive, or technical research
 - `*product-brief` - Create a product brief (input for PRD)
 - `*document-project` - Document existing brownfield projects
-- Party mode and advanced elicitation
 
 ---
 
-## PM (John) | `/bmad:bmm:agents:pm`
+## PM (John)
 
 Product requirements and planning.
 
-**Capabilities:**
-
+**Commands:**
 - `*workflow-status` - Get workflow status or initialize tracking
 - `*create-prd` - Create Product Requirements Document
 - `*create-epics-and-stories` - Break PRD into epics and user stories (after Architecture)
 - `*implementation-readiness` - Validate PRD, UX, Architecture, Epics alignment
 - `*correct-course` - Course correction during implementation
-- Party mode and advanced elicitation
 
 ---
 
-## Architect (Winston) | `/bmad:bmm:agents:architect`
+## Architect (Winston)
 
 System architecture and technical design.
 
-**Capabilities:**
-
+**Commands:**
 - `*workflow-status` - Get workflow status or initialize tracking
 - `*create-architecture` - Create architecture document to guide development
 - `*implementation-readiness` - Validate PRD, UX, Architecture, Epics alignment
 - `*create-excalidraw-diagram` - System architecture or technical diagrams
 - `*create-excalidraw-dataflow` - Data flow diagrams
-- Party mode and advanced elicitation
 
 ---
 
-## SM (Bob) | `/bmad:bmm:agents:sm`
+## SM (Bob)
 
 Sprint planning and story preparation.
 
-**Capabilities:**
-
+**Commands:**
 - `*sprint-planning` - Generate sprint-status.yaml from epic files
 - `*create-story` - Create story from epic (prep for development)
 - `*validate-create-story` - Validate story quality
 - `*epic-retrospective` - Team retrospective after epic completion
 - `*correct-course` - Course correction during implementation
-- Party mode and advanced elicitation
 
 ---
 
-## DEV (Amelia) | `/bmad:bmm:agents:dev`
+## DEV (Amelia)
 
 Story implementation and code review.
 
-**Capabilities:**
-
+**Commands:**
 - `*dev-story` - Execute story workflow (implementation with tests)
 - `*code-review` - Thorough code review
 
 ---
 
-## Quick Flow Solo Dev (Barry) | `/bmad:bmm:agents:quick-flow-solo-dev`
+## Quick Flow Solo Dev (Barry)
 
 Fast solo development without handoffs.
 
-**Capabilities:**
-
-- `*create-tech-spec` - Architect technical spec with implementation-ready stories
+**Commands:**
+- `*quick-spec` - Architect technical spec with implementation-ready stories
 - `*quick-dev` - Implement tech spec end-to-end solo
 - `*code-review` - Review and improve code
 
 ---
 
-## TEA (Murat) | `/bmad:bmm:agents:tea`
+## TEA (Murat)
 
 Test architecture and quality strategy.
 
-**Capabilities:**
-
+**Commands:**
 - `*framework` - Initialize production-ready test framework
 - `*atdd` - Generate E2E tests first (before implementation)
 - `*automate` - Comprehensive test automation
@@ -104,33 +97,31 @@ Test architecture and quality strategy.
 
 ---
 
-## UX Designer (Sally) | `/bmad:bmm:agents:ux-designer`
+## UX Designer (Sally)
 
 User experience and UI design.
 
-**Capabilities:**
-
+**Commands:**
 - `*create-ux-design` - Generate UX design and UI plan from PRD
 - `*validate-design` - Validate UX specification and design artifacts
 - `*create-excalidraw-wireframe` - Create website or app wireframe
 
 ---
 
-## Technical Writer (Paige) | `/bmad:bmm:agents:tech-writer`
+## Technical Writer (Paige)
 
 Technical documentation and diagrams.
 
-**Capabilities:**
-
-- `*document-project` - Comprehensive project documentation (brownfield analysis)
-- `*generate-mermaid` - Generate Mermaid diagrams (architecture, sequence, flow, ER, class, state)
+**Commands:**
+- `*document-project` - Comprehensive project documentation
+- `*generate-mermaid` - Generate Mermaid diagrams
 - `*create-excalidraw-flowchart` - Process and logic flow visualizations
 - `*create-excalidraw-diagram` - System architecture or technical diagrams
 - `*create-excalidraw-dataflow` - Data flow visualizations
 - `*validate-doc` - Review documentation against standards
 - `*improve-readme` - Review and improve README files
-- `*explain-concept` - Create clear technical explanations with examples
-- `*standards-guide` - Show BMAD documentation standards reference
+- `*explain-concept` - Create clear technical explanations
+- `*standards-guide` - Show BMad documentation standards
 
 ---
 
@@ -140,5 +131,11 @@ Available to all agents:
 
 - `*menu` - Redisplay menu options
 - `*dismiss` - Dismiss agent
+- `*party-mode` - Multi-agent collaboration (most agents)
+
+---
+
+## Related
 
-Party mode is available to most agents for multi-agent collaboration.
+- [Agent Roles](/docs/explanation/core-concepts/agent-roles.md) - Understanding agent responsibilities
+- [What Are Agents](/docs/explanation/core-concepts/what-are-agents.md) - Foundational concepts

package/docs/reference/configuration/core-tasks.md

@@ -0,0 +1,67 @@
+---
+title: "Core Tasks"
+---
+
+
+Core Tasks are reusable task definitions that can be invoked by any BMad module, workflow, or agent. These tasks provide standardized functionality for common operations.
+
+## Table of Contents
+
+- [Index Docs](#index-docs) — Generate directory index files
+- [Adversarial Review](#adversarial-review-general) — Critical content review
+- [Shard Document](#shard-document) — Split large documents into sections
+
+---
+
+## Index Docs
+
+**Generates or updates an index.md file documenting all documents in a specified directory.**
+
+This task scans a target directory, reads file contents to understand their purpose, and creates a well-organized index with accurate descriptions. Files are grouped by type, purpose, or subdirectory, and descriptions are generated from actual content rather than guessing from filenames.
+
+**Use it when:** You need to create navigable documentation for a folder of markdown files, or you want to maintain an updated index as content evolves.
+
+**How it works:**
+1. Scan the target directory for files and subdirectories
+2. Group content by type, purpose, or location
+3. Read each file to generate brief (3-10 word) descriptions based on actual content
+4. Create or update index.md with organized listings using relative paths
+
+**Output format:** A markdown index with sections for Files and Subdirectories, each entry containing a relative link and description.
+
+---
+
+## Adversarial Review (General)
+
+**Performs a cynical, skeptical review of any content to identify issues and improvement opportunities.**
+
+This task applies adversarial thinking to content review—approaching the material with the assumption that problems exist. It's designed to find what's missing, not just what's wrong, and produces at least ten specific findings. The reviewer adopts a professional but skeptical tone, looking for gaps, inconsistencies, oversights, and areas that need clarification.
+
+**Use it when:** You need a critical eye on code diffs, specifications, user stories, documentation, or any artifact before finalizing. It's particularly valuable before merging code, releasing documentation, or considering a specification complete.
+
+**How it works:**
+1. Load the content to review (diff, branch, uncommitted changes, document, etc.)
+2. Perform adversarial analysis with extreme skepticism—assume problems exist
+3. Find at least ten issues to fix or improve
+4. Output findings as a markdown list
+
+**Note:** This task is designed to run in a separate subagent/process with read access to the project but no prior context, ensuring an unbiased review.
+
+---
+
+## Shard Document
+
+**Splits large markdown documents into smaller, organized files based on level 2 (##) sections.**
+
+Uses the `@kayvan/markdown-tree-parser` tool to automatically break down large documents into a folder structure. Each level 2 heading becomes a separate file, and an index.md is generated to tie everything together. This makes large documents more maintainable and allows for easier navigation and updates to individual sections.
+
+**Use it when:** A markdown file has grown too large to effectively work with, or you want to break a monolithic document into manageable sections that can be edited independently.
+
+**How it works:**
+1. Confirm source document path and verify it's a markdown file
+2. Determine destination folder (defaults to same location as source, folder named after document)
+3. Execute the sharding command using npx @kayvan/markdown-tree-parser
+4. Verify output files and index.md were created
+5. Handle the original document—delete, move to archive, or keep with warning
+
+**Handling the original:** After sharding, the task prompts you to delete, archive, or keep the original document. Deleting or archiving is recommended to avoid confusion and ensure updates happen in the sharded files only.

package/docs/reference/configuration/global-config.md

@@ -0,0 +1,14 @@
+---
+title: "Core Module Global Inheritable Config"
+---
+
+
+The Core Modules module.yaml file defines configuration values that are useful and unique for all other modules to utilize, and by default all other modules installed will clone the values defined in the core module yaml.config into their own. It is possible for other modules to override these values, but the general intent it to accept the core module values and define their own values as needed, or extend the core values.
+
+Currently, the core module.yaml config will define (asking the user upon installation, and recording to the core module config.yaml):
+- `user_name`: string (defaults to the system defined user name)
+- `communication_language`: string (defaults to english)
+- `document_output_language`: string (defaults to english)
+- `output_folder`: string (default `_bmad-output`)
+
+An example of extending one of these values, in the BMad Method module.yaml it defines a planning_artifacts config, which will default to `default: "{output_folder}/planning-artifacts"` thus whatever the output_folder will be, this extended versions default will use the value from this core module and append a new folder onto it. The user can choose to replace this without utilizing the output_folder from the core if they so chose.

package/{src/modules/bmm/docs/glossary.md → docs/reference/glossary/index.md}

@@ -1,6 +1,9 @@
-# BMM Glossary
+---
+title: "BMad Glossary"
+---
 
-Comprehensive terminology reference for the BMad Method Module.
+
+Comprehensive terminology reference for the BMad Method.
 
 ---
 
@@ -14,11 +17,16 @@ Comprehensive terminology reference for the BMad Method Module.
 - [Status and Tracking](#status-and-tracking)
 - [Project Types](#project-types)
 - [Implementation Terms](#implementation-terms)
+- [Game Development Terms](#game-development-terms)
 
 ---
 
 ## Core Concepts
 
+### BMad (Breakthrough Method of Agile AI Driven Development)
+
+AI-driven agile development framework with specialized agents, guided workflows, and scale-adaptive intelligence.
+
 ### BMM (BMad Method Module)
 
 Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
@@ -89,7 +97,11 @@ Optional strategic planning document created in Phase 1 (Analysis) that captures
 
 ### GDD (Game Design Document)
 
-Game development equivalent of PRD, created by Game Designer agent for game projects.
+Game development equivalent of PRD, created by Game Designer agent for game projects. Comprehensive document detailing all aspects of game design: mechanics, systems, content, and more.
+
+### Game Brief
+
+Document capturing the game's core vision, pillars, target audience, and scope. Foundation for the GDD.
 
 ---
 
@@ -115,10 +127,6 @@ Architecture design phase. Required for BMad Method and Enterprise Method tracks
 
 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.
@@ -153,7 +161,7 @@ Agent responsible for test strategy, quality gates, NFR assessment, and comprehe
 
 ### 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.
+Agent specialized in creating and maintaining high-quality technical documentation. Expert in documentation standards, information architecture, and professional technical writing.
 
 ### UX Designer
 
@@ -163,13 +171,17 @@ Agent that creates UX design documents, interaction patterns, and visual specifi
 
 Specialized agent for game development projects. Creates game design documents (GDD) and game-specific workflows.
 
+### Game Architect
+
+Agent that designs game system architecture, creates technical architecture for games, and validates game-specific designs.
+
 ### 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).
+Multi-agent collaboration feature where all installed agents 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.
 
 ---
 
@@ -190,7 +202,7 @@ 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)
+- **ready-for-dev** - Story file created via create-story; validation is optional
 - **in-progress** - DEV is implementing via dev-story
 - **review** - Implementation complete, awaiting code-review
 - **done** - Completed with DoD met
@@ -247,6 +259,10 @@ Implementation guidance embedded within story files during the create-story work
 
 Workflow that initializes Phase 4 implementation by creating sprint-status.yaml, extracting all epics/stories from planning docs, and setting up tracking infrastructure.
 
+### Sprint
+
+Time-boxed period of development work, typically 1-2 weeks.
+
 ### 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.
@@ -261,6 +277,66 @@ Criteria that must be met before marking a story as done. Typically includes: im
 
 ---
 
+## Game Development Terms
+
+### Core Fantasy
+
+The emotional experience players seek from your game. What they want to FEEL.
+
+### Core Loop
+
+The fundamental cycle of actions players repeat throughout gameplay. The heart of your game.
+
+### Design Pillar
+
+Core principle that guides all design decisions. Typically 3-5 pillars define a game's identity.
+
+### Game Type
+
+Genre classification that determines which specialized GDD sections are included.
+
+### Narrative Complexity
+
+How central story is to the game experience:
+- **Critical** - Story IS the game (visual novels)
+- **Heavy** - Deep narrative with gameplay (RPGs)
+- **Moderate** - Meaningful story supporting gameplay
+- **Light** - Minimal story, gameplay-focused
+
+### Environmental Storytelling
+
+Narrative communicated through the game world itself—visual details, audio, found documents—rather than explicit dialogue.
+
+### MDA Framework
+
+Mechanics → Dynamics → Aesthetics. Framework for analyzing and designing games.
+
+### Procedural Generation
+
+Algorithmic creation of game content (levels, items, characters) rather than hand-crafted.
+
+### Roguelike
+
+Genre featuring procedural generation, permadeath, and run-based progression.
+
+### Metroidvania
+
+Genre featuring interconnected world exploration with ability-gated progression.
+
+### Meta-Progression
+
+Persistent progression that carries between individual runs or sessions.
+
+### Permadeath
+
+Game mechanic where character death is permanent, typically requiring a new run.
+
+### Player Agency
+
+The degree to which players can make meaningful choices that affect outcomes.
+
+---
+
 ## Additional Terms
 
 ### Workflow Status
@@ -279,10 +355,6 @@ Automatic analysis by workflow-init that uses keyword analysis, complexity indic
 
 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.
@@ -291,16 +363,10 @@ Implementation technique for brownfield projects that allows gradual rollout of
 
 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.
+### Context Engineering
 
----
+Loading domain-specific standards and patterns into AI context automatically, rather than relying on prompts alone. In TEA, this means the `tea-index.csv` manifest loads relevant knowledge fragments so the AI doesn't relearn testing patterns each session. This approach ensures consistent, production-ready outputs regardless of prompt variation.
 
-## Related Documentation
+### Convention Detection
 
-- [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
+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.

package/{src/modules/bmgd/docs/workflows-guide.md → docs/reference/workflows/bmgd-workflows.md}

@@ -1,4 +1,7 @@
-# BMGD Workflows Guide
+---
+title: "BMGD Workflows Guide"
+---
+
 
 Complete reference for all BMGD workflows organized by development phase.
 
@@ -8,7 +11,7 @@ Complete reference for all BMGD workflows organized by development phase.
 
 BMGD workflows are organized into four phases:
 
-![BMGD Workflow Overview](./workflow-overview.jpg)
+![BMGD Workflow Overview](../../tutorials/getting-started/images/workflow-overview.jpg)
 
 ---
 
@@ -161,7 +164,7 @@ Production workflows inherit from BMM and add game-specific overrides.
 **Command:** `sprint-planning`
 **Agent:** Game Scrum Master
 **Input:** GDD with epics
-**Output:** `{output_folder}/sprint-status.yaml`
+**Output:** `{implementation_artifacts}/sprint-status.yaml`
 
 **Description:**
 Generates or updates sprint tracking from epic files. Sets up the sprint backlog and tracking.
@@ -259,7 +262,7 @@ Checks current project status across all phases. Shows completed documents, curr
 
 ## Quick-Flow Workflows
 
-Fast-track workflows that skip full planning phases. See **[Quick-Flow Guide](./quick-flow-guide.md)** for detailed usage.
+Fast-track workflows that skip full planning phases. See **[Quick-Flow Guide](/docs/how-to/workflows/bmgd-quick-flow.md)** for detailed usage.
 
 ### Quick-Prototype
 
@@ -457,7 +460,7 @@ This means:
 
 ## Next Steps
 
-- **[Quick Start Guide](./quick-start.md)** - Get started with BMGD
-- **[Quick-Flow Guide](./quick-flow-guide.md)** - Rapid prototyping and development
-- **[Agents Guide](./agents-guide.md)** - Agent reference
-- **[Game Types Guide](./game-types-guide.md)** - Game type templates
+- **[Quick Start Guide](/docs/tutorials/getting-started/quick-start-bmgd.md)** - Get started with BMGD
+- **[Quick-Flow Guide](/docs/how-to/workflows/bmgd-quick-flow.md)** - Rapid prototyping and development
+- **[Agents Guide](/docs/explanation/game-dev/agents.md)** - Agent reference
+- **[Game Types Guide](/docs/explanation/game-dev/game-types.md)** - Game type templates

package/docs/reference/workflows/core-workflows.md

@@ -0,0 +1,33 @@
+---
+title: "Core Workflows"
+---
+
+
+Core Workflows are domain-agnostic workflows that can be utilized by any BMad-compliant module, workflow, or agent. These workflows are installed by default and available at any time.
+
+## Available Core Workflows
+
+### [Party Mode](/docs/explanation/features/party-mode.md)
+
+Orchestrate dynamic multi-agent conversations with your entire BMad team. Engage with multiple specialized perspectives simultaneously—each agent maintaining their unique personality, expertise, and communication style.
+
+### [Brainstorming](/docs/explanation/features/brainstorming-techniques.md)
+
+Facilitate structured creative sessions using 60+ proven ideation techniques. The AI acts as coach and guide, using proven creativity methods to draw out ideas and insights that are already within you.
+
+### [Advanced Elicitation](/docs/explanation/features/advanced-elicitation.md)
+
+Push the LLM to rethink its work through 50+ reasoning methods—the inverse of brainstorming. The LLM applies sophisticated techniques to re-examine and enhance content it has just generated, essentially "LLM brainstorming" to find better approaches and uncover improvements.
+
+---
+
+## Workflow Integration
+
+Core Workflows are designed to be invoked and configured by other modules. When called from another workflow, they accept contextual parameters to customize the session:
+
+- **Topic focus** — Direct the session toward a specific domain or question
+- **Additional personas** (Party Mode) — Inject expert agents into the roster at runtime
+- **Guardrails** (Brainstorming) — Set constraints and boundaries for ideation
+- **Output goals** — Define what the final output needs to accomplish
+
+This allows modules to leverage these workflows' capabilities while maintaining focus on their specific domain and objectives.

package/docs/reference/workflows/document-project.md

@@ -0,0 +1,74 @@
+---
+title: "Document Project Workflow - Technical Reference"
+---
+
+
+**Module:** BMM (BMad Method Module)
+
+## Purpose
+
+Analyzes and documents brownfield projects by scanning codebase, architecture, and patterns to create comprehensive reference documentation for AI-assisted development. Generates a master index and multiple documentation files tailored to project structure and type.
+
+## How to Invoke
+```bash
+/bmad:bmm:workflows:document-project
+```
+---
+
+## Scan Levels
+
+Choose the right scan depth for your needs:
+
+### 1. Quick Scan (Default)
+
+**What it does:** Pattern-based analysis without reading source files
+**Reads:** Config files, package manifests, directory structure, README
+**Use when:**
+
+- You need a fast project overview
+- Initial understanding of project structure
+- Planning next steps before deeper analysis
+
+**Does NOT read:** Source code files (`_.js`, `_.ts`, `_.py`, `_.go`, etc.)
+
+### 2. Deep Scan
+
+**What it does:** Reads files in critical directories based on project type
+**Reads:** Files in critical paths defined by documentation requirements
+**Use when:**
+
+- Creating comprehensive documentation for brownfield PRD
+- Need detailed analysis of key areas
+- Want balance between depth and speed
+
+**Example:** For a web app, reads controllers/, models/, components/, but not every utility file
+
+### 3. Exhaustive Scan
+
+**What it does:** Reads ALL source files in project
+**Reads:** Every source file (excludes node_modules, dist, build, .git)
+**Use when:**
+
+- Complete project analysis needed
+- Migration planning requires full understanding
+- Detailed audit of entire codebase
+- Deep technical debt assessment
+
+**Note:** Deep-dive mode ALWAYS uses exhaustive scan (no choice)
+
+---
+
+## Resumability
+
+The workflow can be interrupted and resumed without losing progress:
+
+- **State Tracking:** Progress saved in `project-scan-report.json`
+- **Auto-Detection:** Workflow detects incomplete runs (<24 hours old)
+- **Resume Prompt:** Choose to resume or start fresh
+- **Step-by-Step:** Resume from exact step where interrupted
+- **Archiving:** Old state files automatically archived
+
+**Related Documentation:**
+
+- [Brownfield Development Guide](/docs/how-to/brownfield/index.md)
+- [Implementation Workflows](/docs/how-to/workflows/run-sprint-planning.md)

package/docs/reference/workflows/index.md

@@ -0,0 +1,16 @@
+---
+title: "Workflows Reference"
+description: Reference documentation for BMad Method workflows
+---
+
+
+Complete reference documentation for all BMad Method workflows.
+
+## Core Workflows
+
+- [Core Workflows](/docs/reference/workflows/core-workflows.md) - Domain-agnostic workflows available to all modules
+- [Document Project](/docs/reference/workflows/document-project.md) - Brownfield project documentation workflow
+
+## Module-Specific Workflows
+
+- [BMGD Workflows](/docs/reference/workflows/bmgd-workflows.md) - Game development workflows