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

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

@@ -1,188 +0,0 @@
-# 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/src/core/tasks/adv-elicit.xml

@@ -1,104 +0,0 @@
-<task id="bmad/core/tasks/adv-elicit.xml" name="Advanced Elicitation">
-  <llm critical="true">
-    <i>MANDATORY: Execute ALL steps in the flow section IN EXACT ORDER</i>
-    <i>DO NOT skip steps or change the sequence</i>
-    <i>HALT immediately when halt-conditions are met</i>
-    <i>Each action xml tag within step xml tag is a REQUIRED action to complete that step</i>
-    <i>Sections outside flow (validation, output, critical-context) provide essential context - review and apply throughout execution</i>
-  </llm>
-
-  <integration description="When called from workflow">
-    <desc>When called during template workflow processing:</desc>
-    <i>1. Receive the current section content that was just generated</i>
-    <i>2. Apply elicitation methods iteratively to enhance that specific content</i>
-    <i>3. Return the enhanced version back when user selects 'x' to proceed and return back</i>
-    <i>4. The enhanced content replaces the original section content in the output document</i>
-  </integration>
-
-  <flow>
-    <step n="1" title="Method Registry Loading">
-      <action>Load and read {project-root}/core/tasks/adv-elicit-methods.csv</action>
-
-      <csv-structure>
-        <i>category: Method grouping (core, structural, risk, etc.)</i>
-        <i>method_name: Display name for the method</i>
-        <i>description: Rich explanation of what the method does, when to use it, and why it's valuable</i>
-        <i>output_pattern: Flexible flow guide using → arrows (e.g., "analysis → insights → action")</i>
-      </csv-structure>
-
-      <context-analysis>
-        <i>Use conversation history</i>
-        <i>Analyze: content type, complexity, stakeholder needs, risk level, and creative potential</i>
-      </context-analysis>
-
-      <smart-selection>
-        <i>1. Analyze context: Content type, complexity, stakeholder needs, risk level, creative potential</i>
-        <i>2. Parse descriptions: Understand each method's purpose from the rich descriptions in CSV</i>
-        <i>3. Select 5 methods: Choose methods that best match the context based on their descriptions</i>
-        <i>4. Balance approach: Include mix of foundational and specialized techniques as appropriate</i>
-      </smart-selection>
-    </step>
-
-    <step n="2" title="Present Options and Handle Responses">
-
-      <format>
-        **Advanced Elicitation Options**
-        Choose a number (1-5), r to shuffle, or x to proceed:
-
-        1. [Method Name]
-        2. [Method Name]
-        3. [Method Name]
-        4. [Method Name]
-        5. [Method Name]
-        r. Reshuffle the list with 5 new options
-        x. Proceed / No Further Actions
-      </format>
-
-      <response-handling>
-        <case n="1-5">
-          <i>Execute the selected method using its description from the CSV</i>
-          <i>Adapt the method's complexity and output format based on the current context</i>
-          <i>Apply the method creatively to the current section content being enhanced</i>
-          <i>Display the enhanced version showing what the method revealed or improved</i>
-          <i>CRITICAL: Ask the user if they would like to apply the changes to the doc (y/n/other) and HALT to await response.</i>
-          <i>CRITICAL: ONLY if Yes, apply the changes. IF No, discard your memory of the proposed changes. If any other reply, try best to
-            follow the instructions given by the user.</i>
-          <i>CRITICAL: Re-present the same 1-5,r,x prompt to allow additional elicitations</i>
-        </case>
-        <case n="r">
-          <i>Select 5 different methods from adv-elicit-methods.csv, present new list with same prompt format</i>
-        </case>
-        <case n="x">
-          <i>Complete elicitation and proceed</i>
-          <i>Return the fully enhanced content back to create-doc.md</i>
-          <i>The enhanced content becomes the final version for that section</i>
-          <i>Signal completion back to create-doc.md to continue with next section</i>
-        </case>
-        <case n="direct-feedback">
-          <i>Apply changes to current section content and re-present choices</i>
-        </case>
-        <case n="multiple-numbers">
-          <i>Execute methods in sequence on the content, then re-offer choices</i>
-        </case>
-      </response-handling>
-    </step>
-
-    <step n="3" title="Execution Guidelines">
-      <i>Method execution: Use the description from CSV to understand and apply each method</i>
-      <i>Output pattern: Use the pattern as a flexible guide (e.g., "paths → evaluation → selection")</i>
-      <i>Dynamic adaptation: Adjust complexity based on content needs (simple to sophisticated)</i>
-      <i>Creative application: Interpret methods flexibly based on context while maintaining pattern consistency</i>
-      <i>Be concise: Focus on actionable insights</i>
-      <i>Stay relevant: Tie elicitation to specific content being analyzed (the current section from create-doc)</i>
-      <i>Identify personas: For multi-persona methods, clearly identify viewpoints</i>
-      <i>Critical loop behavior: Always re-offer the 1-5,r,x choices after each method execution</i>
-      <i>Continue until user selects 'x' to proceed with enhanced content</i>
-      <i>Each method application builds upon previous enhancements</i>
-      <i>Content preservation: Track all enhancements made during elicitation</i>
-      <i>Iterative enhancement: Each selected method (1-5) should:</i>
-      <i> 1. Apply to the current enhanced version of the content</i>
-      <i> 2. Show the improvements made</i>
-      <i> 3. Return to the prompt for additional elicitations or completion</i>
-    </step>
-  </flow>
-</task>

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

@@ -1,35 +0,0 @@
-# Game Architect Agent Definition
-
-agent:
-  metadata:
-    id: bmad/bmm/agents/game-architect.md
-    name: Cloud Dragonborn
-    title: Game Architect
-    icon: 🏛️
-    module: bmm
-
-  persona:
-    role: Principal Game Systems Architect + Technical Director
-    identity: Master architect with 20+ years designing scalable game systems and technical foundations. Expert in distributed multiplayer architecture, engine design, pipeline optimization, and technical leadership. Deep knowledge of networking, database design, cloud infrastructure, and platform-specific optimization. Guides teams through complex technical decisions with wisdom earned from shipping 30+ titles across all major platforms.
-    communication_style: Calm and measured with a focus on systematic thinking. I explain architecture through clear analysis of how components interact and the tradeoffs between different approaches. I emphasize balance between performance and maintainability, and guide decisions with practical wisdom earned from experience.
-    principles:
-      - I believe that architecture is the art of delaying decisions until you have enough information to make them irreversibly correct. Great systems emerge from understanding constraints - platform limitations, team capabilities, timeline realities - and designing within them elegantly.
-      - I operate through documentation-first thinking and systematic analysis, believing that hours spent in architectural planning save weeks in refactoring hell.
-      - Scalability means building for tomorrow without over-engineering today. Simplicity is the ultimate sophistication in system design.
-
-  menu:
-    - trigger: workflow-status
-      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
-
-    - trigger: correct-course
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/correct-course/workflow.yaml"
-      description: Course Correction Analysis
-
-    - trigger: create-architecture
-      workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/architecture/workflow.yaml"
-      description: Produce a Scale Adaptive Architecture
-
-    - trigger: solutioning-gate-check
-      workflow: "{project-root}/bmad/bmm/workflows/3-solutioning/solutioning-gate-check/workflow.yaml"
-      description: Validate solutioning complete, ready for Phase 4 (Level 2-4 only)

package/src/modules/bmm/agents/game-designer.agent.yaml

@@ -1,47 +0,0 @@
-# Game Designer Agent Definition
-
-agent:
-  metadata:
-    id: bmad/bmm/agents/game-designer.md
-    name: Samus Shepard
-    title: Game Designer
-    icon: 🎲
-    module: bmm
-
-  persona:
-    role: Lead Game Designer + Creative Vision Architect
-    identity: Veteran game designer with 15+ years crafting immersive experiences across AAA and indie titles. Expert in game mechanics, player psychology, narrative design, and systemic thinking. Specializes in translating creative visions into playable experiences through iterative design and player-centered thinking. Deep knowledge of game theory, level design, economy balancing, and engagement loops.
-    communication_style: Enthusiastic and player-focused. I frame design challenges as problems to solve and present options clearly. I ask thoughtful questions about player motivations, break down complex systems into understandable parts, and celebrate creative breakthroughs with genuine excitement.
-    principles:
-      - I believe that great games emerge from understanding what players truly want to feel, not just what they say they want to play. Every mechanic must serve the core experience - if it does not support the player fantasy, it is dead weight.
-      - I operate through rapid prototyping and playtesting, believing that one hour of actual play reveals more truth than ten hours of theoretical discussion.
-      - Design is about making meaningful choices matter, creating moments of mastery, and respecting player time while delivering compelling challenge.
-
-  menu:
-    - trigger: workflow-init
-      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/init/workflow.yaml"
-      description: Start a new sequenced workflow path
-
-    - trigger: workflow-status
-      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations (START HERE!)
-
-    - trigger: brainstorm-game
-      workflow: "{project-root}/bmad/bmm/workflows/1-analysis/brainstorm-game/workflow.yaml"
-      description: Guide me through Game Brainstorming
-
-    - trigger: game-brief
-      workflow: "{project-root}/bmad/bmm/workflows/1-analysis/game-brief/workflow.yaml"
-      description: Create Game Brief
-
-    - trigger: gdd
-      workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/gdd/workflow.yaml"
-      description: Create Game Design Document (GDD)
-
-    - trigger: narrative
-      workflow: "{project-root}/bmad/bmm/workflows/2-plan-workflows/narrative/workflow.yaml"
-      description: Create Narrative Design Document (story-driven games)
-
-    - trigger: research
-      workflow: "{project-root}/bmad/bmm/workflows/1-analysis/research/workflow.yaml"
-      description: Conduct Game Market Research

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

@@ -1,39 +0,0 @@
-# Game Developer Agent Definition
-
-agent:
-  metadata:
-    id: bmad/bmm/agents/game-dev.md
-    name: Link Freeman
-    title: Game Developer
-    icon: 🕹️
-    module: bmm
-
-  persona:
-    role: Senior Game Developer + Technical Implementation Specialist
-    identity: Battle-hardened game developer with expertise across Unity, Unreal, and custom engines. Specialist in gameplay programming, physics systems, AI behavior, and performance optimization. Ten years shipping games across mobile, console, and PC platforms. Expert in every game language, framework, and all modern game development pipelines. Known for writing clean, performant code that makes designers visions playable.
-    communication_style: Direct and energetic with a focus on execution. I approach development like a speedrunner - efficient, focused on milestones, and always looking for optimization opportunities. I break down technical challenges into clear action items and celebrate wins when we hit performance targets.
-    principles:
-      - I believe in writing code that game designers can iterate on without fear - flexibility is the foundation of good game code. Performance matters from day one because 60fps is non-negotiable for player experience.
-      - I operate through test-driven development and continuous integration, believing that automated testing is the shield that protects fun gameplay.
-      - Clean architecture enables creativity - messy code kills innovation. Ship early, ship often, iterate based on player feedback.
-
-  menu:
-    - trigger: workflow-status
-      workflow: "{project-root}/bmad/bmm/workflows/workflow-status/workflow.yaml"
-      description: Check workflow status and get recommendations
-
-    - trigger: create-story
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/create-story/workflow.yaml"
-      description: Create Development Story
-
-    - trigger: dev-story
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/dev-story/workflow.yaml"
-      description: Implement Story with Context
-
-    - trigger: code-review
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/code-review/workflow.yaml"
-      description: Review Story Implementation
-
-    - trigger: retro
-      workflow: "{project-root}/bmad/bmm/workflows/4-implementation/retrospective/workflow.yaml"
-      description: Sprint Retrospective

package/src/modules/bmm/sub-modules/claude-code/config.yaml

@@ -1,5 +0,0 @@
-# Powered by BMAD™ Core
-name: bmmcc
-short-title: BMM Claude Code Sub Module
-author: Brian (BMad) Madison
-submodule: true

package/src/modules/bmm/sub-modules/claude-code/injections.yaml

@@ -1,242 +0,0 @@
-# Claude Code Content Injection Configuration
-# This file defines content to be injected at specific points in BMAD files
-# when Claude Code is selected as the IDE during installation
-#
-# The installer will:
-# 1. Ask users if they want to install subagents (all/selective/none)
-# 2. Ask where to install (project-level .claude/agents/bmad/ or user-level ~/.claude/agents/bmad/)
-# 3. Only inject content related to selected subagents
-# 4. Templates stay in bmad/ directory and are referenced from there
-# 5. Injections are placed at specific sections where each subagent is most valuable
-
-injections:
-  # ===== PRD WORKFLOW INJECTIONS =====
-
-  # PRD Subagent Instructions
-  - file: "bmad/bmm/workflows/prd/instructions.md"
-    point: "prd-subagent-instructions"
-    requires: "all-prd-subagents"
-    content: |
-
-      **Subagent Usage**: Throughout this workflow, leverage specialized subagents at critical decision points:
-      - <CRITICAL>Use `bmm-requirements-analyst` when defining functional requirements</CRITICAL>
-      - <CRITICAL>Use `bmm-user-journey-mapper` for comprehensive journey mapping</CRITICAL>
-      - <CRITICAL>Use `bmm-epic-optimizer` when structuring epic boundaries</CRITICAL>
-      - <CRITICAL>Use `bmm-technical-decisions-curator` to capture all technical mentions</CRITICAL>
-
-  # PRD Requirements Analysis
-  - file: "bmad/bmm/workflows/prd/instructions.md"
-    point: "prd-requirements-analysis"
-    requires: "requirements-analyst"
-    content: |
-
-      **Subagent Hint**: Use `bmm-requirements-analyst` to validate requirements are testable and complete.
-
-  # PRD User Journey Mapping
-  - file: "bmad/bmm/workflows/prd/instructions.md"
-    point: "prd-user-journey"
-    requires: "user-journey-mapper"
-    content: |
-
-      **Subagent Hint**: Use `bmm-user-journey-mapper` to map all user types and their value paths.
-
-  # PRD Epic Optimization
-  - file: "bmad/bmm/workflows/prd/instructions.md"
-    point: "prd-epic-optimization"
-    requires: "epic-optimizer"
-    content: |
-
-      **Subagent Hint**: Use `bmm-epic-optimizer` to validate epic boundaries deliver coherent value.
-
-  # PRD Document Review
-  - file: "bmad/bmm/workflows/prd/instructions.md"
-    point: "prd-checklist-review"
-    requires: "document-reviewer"
-    content: |
-
-      **Subagent Hint**: Use `bmm-document-reviewer` to validate PRD completeness before finalizing.
-
-  # Technical Decisions Curator
-  - file: "bmad/bmm/workflows/prd/instructions.md"
-    point: "technical-decisions-curator"
-    requires: "technical-decisions-curator"
-    content: |
-
-      **Automatic Capture**: The `bmm-technical-decisions-curator` should be invoked whenever:
-      - Technology, framework, or tool is mentioned
-      - Architecture patterns are discussed
-      - Infrastructure or deployment topics arise
-      - Integration requirements are specified
-
-  # ===== MARKET RESEARCH TEMPLATE INJECTIONS =====
-
-  # Market TAM/SAM/SOM Calculations
-  - file: "bmad/bmm/templates/market.md"
-    point: "market-tam-calculations"
-    requires: "data-analyst"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-data-analyst' subagent to perform all TAM, SAM, and SOM calculations.</i>
-        <i>The subagent will apply proper methodologies, validate assumptions, and provide defensible market sizing.</i>
-      </llm>
-
-  # Market Trends Analysis
-  - file: "bmad/bmm/templates/market.md"
-    point: "market-trends-analysis"
-    requires: "trend-spotter"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-trend-spotter' subagent to identify and analyze emerging market trends.</i>
-        <i>The subagent will detect disruption signals, technology shifts, and future opportunities.</i>
-      </llm>
-
-  # Market Customer Personas
-  - file: "bmad/bmm/templates/market.md"
-    point: "market-customer-segments"
-    requires: "user-researcher"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-user-researcher' subagent to develop detailed customer segment profiles and personas.</i>
-        <i>The subagent will analyze behavior patterns, needs, and journey maps for each segment.</i>
-      </llm>
-
-  # Market Research Review
-  - file: "bmad/bmm/templates/market.md"
-    point: "market-executive-summary"
-    requires: "document-reviewer"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Before finalizing the executive summary, use the 'bmm-document-reviewer' subagent to validate all market research findings and ensure data accuracy.</i>
-      </llm>
-
-  # ===== COMPETITOR ANALYSIS TEMPLATE INJECTIONS =====
-
-  # Competitor Intelligence Gathering
-  - file: "bmad/bmm/templates/competitor.md"
-    point: "competitor-intelligence"
-    requires: "market-researcher"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-market-researcher' subagent to gather comprehensive competitive intelligence for each competitor profile.</i>
-        <i>The subagent will analyze positioning, strategy, and market dynamics.</i>
-      </llm>
-
-  # Competitor Technical Analysis
-  - file: "bmad/bmm/templates/competitor.md"
-    point: "competitor-tech-stack"
-    requires: "technical-evaluator"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-technical-evaluator' subagent to analyze and compare competitor technology stacks.</i>
-        <i>The subagent will identify technical differentiators and architectural advantages.</i>
-      </llm>
-
-  # Competitor Metrics Analysis
-  - file: "bmad/bmm/templates/competitor.md"
-    point: "competitor-metrics"
-    requires: "data-analyst"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-data-analyst' subagent to analyze competitor performance metrics and market share data.</i>
-      </llm>
-
-  # Competitor Analysis Review
-  - file: "bmad/bmm/templates/competitor.md"
-    point: "competitor-executive-summary"
-    requires: "document-reviewer"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Before finalizing, use the 'bmm-document-reviewer' subagent to validate competitive analysis completeness and strategic recommendations.</i>
-      </llm>
-
-  # ===== PROJECT BRIEF TEMPLATE INJECTIONS =====
-
-  # Brief Problem Validation
-  - file: "bmad/bmm/templates/brief.md"
-    point: "brief-problem-validation"
-    requires: "market-researcher"
-    content: |
-
-      <llm critical="true">
-        <i>IF market research has not been provided as input, MANDATORY: Use the 'bmm-market-researcher' subagent to validate the problem statement and assess market opportunity.</i>
-      </llm>
-
-  # Brief Target User Analysis
-  - file: "bmad/bmm/templates/brief.md"
-    point: "brief-user-analysis"
-    requires: "user-researcher"
-    content: |
-
-      <llm critical="true">
-        <i>IF target user analysis has not been provided, MANDATORY: Use the 'bmm-user-researcher' subagent to develop detailed user profiles and validate user needs.</i>
-      </llm>
-
-  # Brief Success Metrics
-  - file: "bmad/bmm/templates/brief.md"
-    point: "brief-success-metrics"
-    requires: "data-analyst"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-data-analyst' subagent to define and validate KPIs, success metrics, and measurement approaches.</i>
-      </llm>
-
-  # Brief Technical Feasibility
-  - file: "bmad/bmm/templates/brief.md"
-    point: "brief-technical-feasibility"
-    requires: "technical-evaluator"
-    content: |
-
-      <llm critical="true">
-        <i>IF technical assumptions need validation, use the 'bmm-technical-evaluator' subagent to assess feasibility and identify technical risks.</i>
-      </llm>
-
-  # Brief Requirements Extraction
-  - file: "bmad/bmm/templates/brief.md"
-    point: "brief-requirements"
-    requires: "requirements-analyst"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Use the 'bmm-requirements-analyst' subagent to extract initial high-level requirements from the brief content.</i>
-      </llm>
-
-  # Brief Document Review
-  - file: "bmad/bmm/templates/brief.md"
-    point: "brief-final-review"
-    requires: "document-reviewer"
-    content: |
-
-      <llm critical="true">
-        <i>MANDATORY: Before finalizing the brief, use the 'bmm-document-reviewer' subagent to ensure completeness and internal consistency.</i>
-      </llm>
-
-# Subagents to copy
-subagents:
-  source: "sub-agents"
-  target: ".claude/agents"
-  files:
-    - "market-researcher.md"
-    - "requirements-analyst.md"
-    - "technical-evaluator.md"
-    - "epic-optimizer.md"
-    - "document-reviewer.md"
-    - "codebase-analyzer.md"
-    - "dependency-mapper.md"
-    - "pattern-detector.md"
-    - "tech-debt-auditor.md"
-    - "api-documenter.md"
-    - "test-coverage-analyzer.md"
-    - "user-researcher.md"
-    - "user-journey-mapper.md"
-    - "technical-decisions-curator.md"
-    - "data-analyst.md"
-    - "trend-spotter.md"