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

package/docs/conversion-report-shard-doc-2025-10-26.md

@@ -0,0 +1,188 @@
+# Legacy Task Conversion Report
+
+**Generated**: 2025-10-26
+**Converted By**: BMad Builder Agent
+**Conversion Type**: Legacy Task → v6 XML Task
+
+---
+
+## Source Information
+
+- **Original Location**: https://github.com/bmad-code-org/BMAD-METHOD/blob/main/bmad-core/tasks/shard-doc.md
+- **Original Format**: Markdown task (v4/legacy format)
+- **Original Type**: Document sharding utility task
+
+---
+
+## Target Information
+
+- **New Location**: `/Users/brianmadison/dev/BMAD-METHOD/src/core/tasks/shard-doc.xml`
+- **New Format**: v6 XML task format
+- **Task ID**: `bmad/core/tasks/shard-doc`
+- **Task Name**: Shard Document
+
+---
+
+## Conversion Summary
+
+### Components Converted
+
+✅ **Task Structure**: Converted from markdown to XML format
+✅ **Execution Flow**: 6 steps properly structured in `<flow>` section (simplified to tool-only)
+✅ **Critical Instructions**: Moved to `<llm critical="true">` section
+✅ **Validation Rules**: Extracted to `<validation>` section
+✅ **Halt Conditions**: Extracted to `<halt-conditions>` section
+✅ **Special Guidelines**: Moved to `<critical-context>` section
+✅ **Output Format**: Documented in `<output-format>` section
+✅ **Tool Information**: Preserved in `<tool-info>` section
+
+### Key Features Preserved
+
+- **Automated Tool**: Uses @kayvan/markdown-tree-parser exclusively
+- **Simplified Flow**: Removed all manual steps, tool handles everything
+- **Code Block Awareness**: Tool automatically handles ## inside code blocks
+- **Content Preservation**: Tool preserves all markdown formatting and special content
+- **Heading Adjustment**: Tool automatically reduces heading levels by one
+- **Index Generation**: Tool automatically creates index.md
+- **Validation Steps**: Verification of tool installation and output
+- **Error Handling**: Halt conditions for tool and file system issues
+
+### v6 Conventions Applied
+
+- ✅ Proper `<task>` wrapper with id and name attributes
+- ✅ `<llm critical="true">` section with mandatory instructions
+- ✅ `<flow>` section with numbered `<step>` elements
+- ✅ Used `<action>` tags for required actions
+- ✅ Used `<i>` tags for instruction lists and context
+- ✅ Conditional logic with `if` attributes on actions
+- ✅ Optional steps marked with `optional="true"`
+- ✅ Supporting sections for validation, halt conditions, output format
+- ✅ Consistent with existing v6 tasks (workflow.xml, adv-elicit.xml, index-docs.xml)
+
+---
+
+## Structural Comparison
+
+### Legacy Format (Markdown)
+
+```
+# Document Sharding Task
+## Primary Method: Automated Approach
+## Manual Method (Fallback)
+1. Identify target location
+2. Parse sections
+...
+## Critical Guidelines
+```
+
+### v6 Format (XML)
+
+```xml
+<task id="bmad/core/tasks/shard-doc" name="Shard Document">
+  <objective>...</objective>
+  <llm critical="true">...</llm>
+  <critical-context>...</critical-context>
+  <flow>
+    <step n="1" title="...">
+      <action>...</action>
+    </step>
+  </flow>
+  <halt-conditions>...</halt-conditions>
+  <validation>...</validation>
+</task>
+```
+
+---
+
+## Validation Results
+
+### XML Structure
+
+- ✅ Valid XML syntax
+- ✅ Properly nested elements
+- ✅ All tags closed correctly
+- ✅ Attributes properly formatted
+
+### v6 Compliance
+
+- ✅ Matches v6 task conventions
+- ✅ Follows existing core task patterns
+- ✅ Uses standard v6 tag set
+- ✅ Proper section organization
+
+### Content Integrity
+
+- ✅ All original instructions preserved
+- ✅ No functionality lost in conversion
+- ✅ Critical warnings maintained
+- ✅ Tool information preserved
+- ✅ Validation logic intact
+
+### File System
+
+- ✅ Saved to correct location: `src/core/tasks/`
+- ✅ Proper filename: `shard-doc.xml`
+- ✅ Follows core task naming convention
+
+---
+
+## Usage Notes
+
+### How to Invoke This Task
+
+From an agent or workflow, reference:
+
+```xml
+<invoke-task>{project-root}/bmad/core/tasks/shard-doc.xml</invoke-task>
+```
+
+Or from agent menu:
+
+```yaml
+menu:
+  - trigger: shard
+    description: 'Split large document into organized files'
+    exec: '{project-root}/bmad/core/tasks/shard-doc.xml'
+```
+
+### Task Capabilities
+
+1. **Automated Mode**: Uses @kayvan/markdown-tree-parser for fast sharding
+2. **Manual Mode**: Step-by-step guided process for controlled sharding
+3. **Safety Checks**: Validates code blocks aren't treated as headers
+4. **Content Preservation**: Maintains all formatting, code, tables, diagrams
+5. **Index Generation**: Creates navigable index.md automatically
+6. **Validation**: Verifies completeness and integrity
+
+---
+
+## Post-Conversion Actions
+
+### Recommended Next Steps
+
+1. ✅ **Task Created**: File saved to core tasks directory
+2. **Test Task**: Invoke from an agent or workflow to verify functionality
+3. **Update Documentation**: Reference in core task documentation if needed
+4. **Integration**: Add to relevant agent menus if appropriate
+
+### No Manual Adjustments Required
+
+The conversion is complete and ready for use. All legacy functionality has been successfully migrated to v6 XML format.
+
+---
+
+## Notes
+
+- Original legacy file can be archived or left as-is (located on GitHub)
+- This task is now a core BMAD task available to all modules
+- The task follows v6 conventions and is fully compatible with BMAD-CORE v6 alpha
+- **UPDATED 2025-10-26**: Manual fallback steps removed - task now exclusively uses @kayvan/markdown-tree-parser
+- Flow simplified from 8 steps to 6 steps (tool installation → execution → verification)
+- All manual parsing, file creation, and index generation logic removed (tool handles automatically)
+
+---
+
+**Conversion Status**: ✅ COMPLETE (Updated)
+**Ready for Use**: YES
+**Manual Adjustments Needed**: NONE
+**Approach**: Automated tool only (no manual fallback)

package/docs/ide-info/auggie.md

@@ -6,8 +6,8 @@ BMAD agents can be installed in multiple locations based on your setup.
 
 ### Common Locations
 
-- User Home: `~/.auggie/commands/`
-- Project: `.auggie/commands/`
+- User Home: `~/.augment/commands/`
+- Project: `.augment/commands/`
 - Custom paths you selected
 
 ### How to Use

package/docs/ide-info/claude-code.md

@@ -13,13 +13,13 @@ BMAD agents are installed as slash commands in `.claude/commands/bmad/`.
 ### Examples
 
 ```
-/bmad-dev - Activate development agent
-/bmad-architect - Activate architect agent
-/bmad-task-setup - Execute setup task
+/bmad:bmm:agents:dev - Activate development agent
+/bmad:bmm:agents:architect - Activate architect agent
+/bmad:bmm:workflows:dev-story - Execute dev-story workflow
 ```
 
 ### Notes
 
 - Commands are autocompleted when you type `/`
 - Agent remains active for the conversation
-- Start new conversation to switch agents
+- Start a new conversation to switch agents

package/docs/ide-info/codex.md

@@ -2,31 +2,20 @@
 
 ## Activating Agents
 
-BMAD agents are documented in `AGENTS.md` file in project root.
-
-### CLI Mode
-
-1. **Reference Agent**: Type `@{agent-name}` in prompt
-2. **Execute Task**: Type `@task-{task-name}`
-3. **Active Session**: Agent remains active for conversation
-
-### Web Mode
-
-1. **Navigate**: Go to Agents section in web interface
-2. **Select Agent**: Click to activate agent persona
-3. **Session**: Agent active for browser session
+BMAD agents, tasks and workflows are installed as custom prompts in
+`$CODEX_HOME/prompts/bmad-*.md` files. If `CODEX_HOME` is not set, it
+defaults to `$HOME/.codex/`.
 
 ### Examples
 
 ```
-@dev - Activate development agent
-@architect - Activate architect agent
-@task-setup - Execute setup task
+/bmad-bmm-agents-dev - Activate development agent
+/bmad-bmm-agents-architect - Activate architect agent
+/bmad-bmm-workflows-dev-story - Execute dev-story workflow
 ```
 
 ### Notes
 
-- All agents documented in AGENTS.md
-- CLI: Reference with @ syntax
-- Web: Use interface to select
-- One agent active at a time
+Prompts are autocompleted when you type /
+Agent remains active for the conversation
+Start a new conversation to switch agents

package/docs/ide-info/opencode.md

@@ -0,0 +1,24 @@
+# BMAD Method - OpenCode Instructions
+
+## Activating Agents
+
+BMAD agents are installed as OpenCode agents in `.opencode/agent/BMAD/{module_name}` and workflow commands in `.opencode/command/BMAD/{module_name}`.
+
+### How to Use
+
+1. **Switch Agents**: Press **Tab** to cycle through primary agents or select using the `/agents`
+2. **Activate Agent**: Once the Agent is selected say `hello` or any prompt to activate that agent persona
+3. **Execute Commands**: Type `/bmad` to see and execute bmad workflow commands (commands allow for fuzzy matching)
+
+### Examples
+
+```
+/agents - to see a list of agents and switch between them
+/bmad/bmm/workflows/workflow-init - Activate the workflow-init command
+```
+
+### Notes
+
+- Press **Tab** to switch between primary agents (Analyst, Architect, Dev, etc.)
+- Commands are autocompleted when you type `/` and allow for fuzzy matching
+- Workflow commands execute in current agent context, make sure you have the right agent activated before running a command

package/docs/installers-bundlers/ide-injections.md

@@ -184,13 +184,3 @@ injections:
   <cmds>...</cmds>
 </agent>
 ```
-
-## Testing Checklist
-
-- [ ] Injection points are properly named and unique
-- [ ] injections.yaml is valid YAML with correct structure
-- [ ] Content formatting is preserved after injection
-- [ ] Installation works without the IDE (injection points removed)
-- [ ] Installation works with the IDE (content properly injected)
-- [ ] Subagents/files are copied to correct locations
-- [ ] No IDE-specific content remains when different IDE selected

package/docs/installers-bundlers/installers-modules-platforms-reference.md

@@ -1,4 +1,4 @@
-# BMAD v6 Installation & Module System Reference
+# BMAD Installation & Module System Reference
 
 ## Table of Contents
 
@@ -13,63 +13,36 @@
 
 ## Overview
 
-BMAD v6 is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.
+BMad Core is a modular AI agent framework with intelligent installation, platform-agnostic support, and configuration inheritance.
 
 ### Key Features
 
-- **Modular Design**: Core + optional modules (BMM, CIS)
+- **Modular Design**: Core + optional modules (BMB, BMM, CIS)
 - **Smart Installation**: Interactive configuration with dependency resolution
-- **Multi-Platform**: Supports 15+ AI coding platforms
-- **Clean Architecture**: Centralized `bmad/` directory, no source pollution
-
-## Quick Start
-
-```bash
-# Interactive installation (recommended)
-bmad install
-
-# Install specific modules
-bmad install -m bmm cis
-
-# Full installation
-bmad install -f
-
-# Check status
-bmad status
-```
-
-### Installation Options
-
-- `-d <path>`: Target directory (default: current)
-- `-m <modules...>`: Specific modules (bmm, cis)
-- `-f`: Full installation
-- `-c`: Core only
-- `-i <ide...>`: Configure specific IDEs
-- `--skip-ide`: Skip IDE configuration
-- `-v`: Verbose output
+- **Clean Architecture**: Centralized `bmad/` directory add to project, no source pollution with multiple folders added
 
 ## Architecture
 
-### Directory Structure
+### Directory Structure upon installation
 
 ```
 project-root/
-├── bmad/                    # Centralized installation
-│   ├── _cfg/               # Configuration
-│   │   ├── agents/         # Agent configs
-│   │   └── agent-party.xml # Agent manifest
-│   ├── core/               # Core module
+├── bmad/                      # Centralized installation
+│   ├── _cfg/                  # Configuration
+│   │   ├── agents/            # Agent configs
+│   │   └── agent-manifest.csv # Agent manifest
+│   ├── core/                  # Core module
 │   │   ├── agents/
 │   │   ├── tasks/
 │   │   └── config.yaml
-│   ├── bmm/                # BMad Method module
+│   ├── bmm/                   # BMad Method module
 │   │   ├── agents/
 │   │   ├── tasks/
-│   │   ├── templates/
+│   │   ├── workflows/
 │   │   └── config.yaml
-│   └── cis/                # Creative Innovation Studio
+│   └── cis/                   # Creative Innovation Studio
 │       └── ...
-└── .claude/                # Platform-specific (example)
+└── .claude/                   # Platform-specific (example)
     └── agents/
 ```
 
@@ -78,11 +51,10 @@ project-root/
 1. **Detection**: Check existing installation
 2. **Selection**: Choose modules interactively or via CLI
 3. **Configuration**: Collect module-specific settings
-4. **Platform Setup**: Configure AI coding platforms
-5. **Installation**: Process and copy files
-6. **Generation**: Create config files with inheritance
-7. **Post-Install**: Run module installers
-8. **Manifest**: Track installed components
+4. **Installation**: Compile Process and copy files
+5. **Generation**: Create config files with inheritance
+6. **Post-Install**: Run module installers
+7. **Manifest**: Track installed components
 
 ### Key Exclusions
 
@@ -121,7 +93,7 @@ Creative Innovation Studio for design workflows
 src/modules/{module}/
 ├── _module-installer/       # Not copied to destination
 │   ├── installer.js        # Post-install logic
-│   └── install-menu-config.yaml
+│   └── install-config.yaml
 ├── agents/
 ├── tasks/
 ├── templates/
@@ -135,7 +107,7 @@ src/modules/{module}/
 
 ### Collection Process
 
-Modules define prompts in `install-menu-config.yaml`:
+Modules define prompts in `install-config.yaml`:
 
 ```yaml
 project_name:
@@ -246,12 +218,12 @@ Platform-specific content without source modification:
    src/modules/mymod/
    ├── _module-installer/
    │   ├── installer.js
-   │   └── install-menu-config.yaml
+   │   └── install-config.yaml
    ├── agents/
    └── tasks/
    ```
 
-2. **Configuration** (`install-menu-config.yaml`)
+2. **Configuration** (`install-config.yaml`)
 
    ```yaml
    code: mymod

package/docs/v4-to-v6-upgrade.md

@@ -0,0 +1,225 @@
+# BMad v4 to v6 Upgrade Guide
+
+## Overview
+
+BMad v6 represents a complete ground-up rewrite with significant architectural changes. This guide will help you migrate your v4 project to v6.
+
+---
+
+## Automatic V4 Detection
+
+When you run `npm run install:bmad` on a project with v4 installed, the installer automatically detects:
+
+- **Legacy folders**: Any folders starting with `.bmad`, `bmad` (lowercase), or `Bmad`
+- **IDE command artifacts**: Legacy bmad folders in IDE configuration directories (`.claude/commands/`, `.cursor/commands/`, etc.)
+
+### What Happens During Detection
+
+1. **Automatic Backup of v4 Modules**: All `.bmad-*` folders are moved to `v4-backup/` in your project root
+   - If a backup already exists, a timestamp is added to avoid conflicts
+   - Example: `.bmad-core` → `v4-backup/.bmad-core`
+   - Your project files and data are NOT affected
+
+2. **IDE Command Cleanup Recommended**: Legacy v4 IDE commands should be manually removed
+   - Located in IDE config folders: `.claude/commands/`, `.cursor/commands/`, etc.
+   - These old commands would still reference v4 folder structure if left in place
+   - The installer provides copy/paste terminal commands for your platform
+   - You can proceed without cleanup, but removing them prevents confusion with old v4 commands
+
+---
+
+## Module Migration
+
+### Deprecated Modules
+
+| v4 Module                     | v6 Status                                        |
+| ----------------------------- | ------------------------------------------------ |
+| `.bmad-2d-phaser-game-dev`    | Integrated into BMM                              |
+| `.bmad-2d-unity-game-dev`     | Integrated into BMM                              |
+| `.bmad-godot-game-dev`        | Integrated into BMM                              |
+| `.bmad-*-game-dev` (any)      | Integrated into BMM                              |
+| `.bmad-infrastructure-devops` | Deprecated - New core devops agent coming in BMM |
+| `.bmad-creative-writing`      | Not adapted - New module releasing soon          |
+
+**Game Development**: All game development functionality has been consolidated and expanded within the BMM (BMad Method) module. Game-specific workflows now adapt to your game type and engine.
+
+---
+
+## Architecture Changes
+
+### Folder Structure
+
+**v4 "Expansion Packs" Structure:**
+
+```
+your-project/
+├── .bmad-core/           # Was actually the BMad Method
+├── .bmad-game-dev/       # Separate expansion packs
+├── .bmad-creative-writing/
+└── .bmad-infrastructure-devops/
+```
+
+**v6 Unified Structure:**
+
+```
+your-project/
+└── bmad/                 # Single installation folder
+    ├── core/            # Real core framework (applies to all modules)
+    ├── bmm/             # BMad Method (software/game dev)
+    ├── bmb/             # BMad Builder (create agents/workflows)
+    ├── cis/             # Creative Intelligence Suite
+    └── _cfg/            # Your customizations
+        └── agents/      # Agent customization files
+```
+
+### Key Concept Changes
+
+- **v4 `.bmad-core`**: Was actually the BMad Method
+- **v6 `bmad/core/`**: Is the real universal core framework
+- **v6 `bmad/bmm/`**: Is the BMad Method module
+- **Module identification**: All modules now have a `config.yaml` file
+
+---
+
+## Project Progress Migration
+
+### If You've Completed Planning Phase (PRD/Architecture) with the BMad Method:
+
+After running the v6 installer:
+
+1. **Run `workflow-init`** workflow to set up the guided workflow system
+2. **Specify your project level** when prompted:
+   - If you followed v4's full workflow (PRD → Architecture → Stories), select **Level 3 or 4**
+   - This tells v6 you've already completed planning and solutioning phases
+3. **Document paths**: Keep your existing paths during installation
+   - Default PRD/Architecture location: `docs/`
+   - Default stories location: `docs/stories/`
+   - **Accept these defaults** if you're already using them in v4
+
+> **Important**: v6 workflows can handle both sharded and unsharded documents. You don't need to restructure your existing PRD or architecture files.
+
+### If You're Mid-Development (Stories Created/Implemented)
+
+1. Complete the v6 installation as above
+2. Run `workflow-init` and specify Level 3 or 4
+3. When ready to continue development, run the **`sprint-planning`** workflow (Phase 4)
+
+---
+
+## Agent Customization Migration
+
+### v4 Agent Customization
+
+In v4, you may have modified agent files directly in `.bmad-*` folders.
+
+### v6 Agent Customization
+
+**All customizations** now go in `bmad/_cfg/agents/` using customize files:
+
+**Example: Renaming an agent and changing communication style**
+
+File: `bmad/_cfg/agents/bmm-pm.customize.yaml`
+
+```yaml
+# Customize the PM agent
+persona:
+  name: 'Captain Jack' # Override agent name
+  role: 'Swashbuckling Product Owner'
+  communication_style: |
+    - Talk like a pirate
+    - Use nautical metaphors for software concepts
+    - Always upbeat and adventurous
+```
+
+**How it works:**
+
+- Base agent: `bmad/bmm/agents/pm.md`
+- Customization: `bmad/_cfg/agents/bmm-pm.customize.yaml`
+- Result: Agent uses your custom name and style, but updates don't overwrite your changes
+
+---
+
+## Document Compatibility
+
+### Sharded vs Unsharded Documents
+
+**Good news**: Unlike v4, v6 workflows are **fully flexible** with document structure:
+
+- ✅ Sharded documents (split into multiple files)
+- ✅ Unsharded documents (single file per section)
+- ✅ Custom sections for your project type
+- ✅ Mixed approaches
+
+All workflow files are scanned automatically. No manual configuration needed.
+
+---
+
+## Installation Steps
+
+### 1. Clone Repository
+
+```bash
+git clone https://github.com/bmad-code-org/BMAD-METHOD
+cd BMAD-METHOD
+npm install
+```
+
+### 2. Run Installer on Your v4 Project
+
+```bash
+npx bmad-method install
+```
+
+**Enter the full path to your v4 project** when prompted.
+
+### 3. Follow Interactive Prompts
+
+The installer will:
+
+1. Detect v4 installation and offer to backup `.bmad-*` folders
+2. Prompt for recommended cleanup (you can skip)
+3. Let you select modules (recommend: BMM for software and or game development)
+4. Configure core settings (name, language, etc.)
+5. Configure module-specific options
+6. Configure IDE integrations
+
+### 4. Accept Default Paths
+
+If you're using:
+
+- `docs/` for PRD and architecture
+- `docs/stories/` for story files
+
+**Accept these defaults** during installation.
+
+### 5. Initialize Workflow
+
+After installation:
+
+```bash
+# In your project have the agent mode run workflow-init, in Claude Code:
+/workflow-init
+# or run the analyst and tell the analyst after it loads
+*workflow-init
+```
+
+Select **Level 3 or 4** if you've already completed PRD/architecture in v4.
+
+---
+
+## Post-Migration Checklist
+
+- [ ] v4 folders backed up to `v4-backup/`
+- [ ] v6 installed to `bmad/` folder
+- [ ] `workflow-init` run with correct project level selected
+- [ ] Agent customizations migrated to `bmad/_cfg/agents/` if needed
+- [ ] IDE integration working (test by listing agents)
+- [ ] For active development: `sprint-planning` workflow executed
+
+---
+
+## Getting Help
+
+- **Discord**: [Join the BMad Community](https://discord.gg/gk8jAdXWmj)
+- **Issues**: [GitHub Issue Tracker](https://github.com/bmad-code-org/BMAD-METHOD/issues)
+- **Docs**: Check `bmad/docs/` in your installation for IDE-specific instructions

package/eslint.config.mjs

@@ -14,6 +14,8 @@ export default [
       'test/template-test-generator/**',
       'test/template-test-generator/**/*.js',
       'test/template-test-generator/**/*.md',
+      'test/fixtures/**',
+      'test/fixtures/**/*.yaml',
     ],
   },
 
@@ -59,9 +61,9 @@ export default [
     },
   },
 
-  // CLI/CommonJS scripts under tools/**
+  // CLI/CommonJS scripts under tools/** and test/**
   {
-    files: ['tools/**/*.js'],
+    files: ['tools/**/*.js', 'test/**/*.js'],
     rules: {
       // Allow CommonJS patterns for Node CLI scripts
       'unicorn/prefer-module': 'off',