bmad-fh 6.0.0-alpha.23

package/src/bmm/agents/tech-writer/tech-writer-sidecar/documentation-standards.md

@@ -0,0 +1,224 @@
+# Technical Documentation Standards for BMAD
+
+CommonMark standards, technical writing best practices, and style guide compliance.
+
+## User Specified CRITICAL Rules - Supersedes General CRITICAL RULES
+
+None
+
+## General CRITICAL RULES
+
+### Rule 1: CommonMark Strict Compliance
+
+ALL documentation MUST follow CommonMark specification exactly. No exceptions.
+
+### Rule 2: NO TIME ESTIMATES
+
+NEVER document time estimates, durations, level of effort or completion times for any workflow, task, or activity unless EXPLICITLY asked by the user. This includes:
+
+- NO Workflow execution time (e.g., "30-60 min", "2-8 hours")
+- NO Task duration and level of effort estimates
+- NO Reading time estimates
+- NO Implementation time ranges
+- NO Any temporal or capacity based measurements
+
+**Instead:** Focus on workflow steps, dependencies, and outputs. Let users determine their own timelines and level of effort.
+
+### CommonMark Essentials
+
+**Headers:**
+
+- Use ATX-style ONLY: `#` `##` `###` (NOT Setext underlines)
+- Single space after `#`: `# Title` (NOT `#Title`)
+- No trailing `#`: `# Title` (NOT `# Title #`)
+- Hierarchical order: Don't skip levels (h1→h2→h3, not h1→h3)
+
+**Code Blocks:**
+
+- Use fenced blocks with language identifier:
+  ````markdown
+  ```javascript
+  const example = 'code';
+  ```
+  ````
+- NOT indented code blocks (ambiguous)
+
+**Lists:**
+
+- Consistent markers within list: all `-` or all `*` or all `+` (don't mix)
+- Proper indentation for nested items (2 or 4 spaces, stay consistent)
+- Blank line before/after list for clarity
+
+**Links:**
+
+- Inline: `[text](url)`
+- Reference: `[text][ref]` then `[ref]: url` at bottom
+- NO bare URLs without `<>` brackets
+
+**Emphasis:**
+
+- Italic: `*text*` or `_text_`
+- Bold: `**text**` or `__text__`
+- Consistent style within document
+
+**Line Breaks:**
+
+- Two spaces at end of line + newline, OR
+- Blank line between paragraphs
+- NO single line breaks (they're ignored)
+
+## Mermaid Diagrams: Valid Syntax Required
+
+**Critical Rules:**
+
+1. Always specify diagram type first line
+2. Use valid Mermaid v10+ syntax
+3. Test syntax before outputting (mental validation)
+4. Keep focused: 5-10 nodes ideal, max 15
+
+**Diagram Type Selection:**
+
+- **flowchart** - Process flows, decision trees, workflows
+- **sequenceDiagram** - API interactions, message flows, time-based processes
+- **classDiagram** - Object models, class relationships, system structure
+- **erDiagram** - Database schemas, entity relationships
+- **stateDiagram-v2** - State machines, lifecycle stages
+- **gitGraph** - Branch strategies, version control flows
+
+**Formatting:**
+
+````markdown
+```mermaid
+flowchart TD
+    Start[Clear Label] --> Decision{Question?}
+    Decision -->|Yes| Action1[Do This]
+    Decision -->|No| Action2[Do That]
+```
+````
+
+## Style Guide Principles (Distilled)
+
+Apply in this hierarchy:
+
+1. **Project-specific guide** (if exists) - always ask first
+2. **BMAD conventions** (this document)
+3. **Google Developer Docs style** (defaults below)
+4. **CommonMark spec** (when in doubt)
+
+### Core Writing Rules
+
+**Task-Oriented Focus:**
+
+- Write for user GOALS, not feature lists
+- Start with WHY, then HOW
+- Every doc answers: "What can I accomplish?"
+
+**Clarity Principles:**
+
+- Active voice: "Click the button" NOT "The button should be clicked"
+- Present tense: "The function returns" NOT "The function will return"
+- Direct language: "Use X for Y" NOT "X can be used for Y"
+- Second person: "You configure" NOT "Users configure" or "One configures"
+
+**Structure:**
+
+- One idea per sentence
+- One topic per paragraph
+- Headings describe content accurately
+- Examples follow explanations
+
+**Accessibility:**
+
+- Descriptive link text: "See the API reference" NOT "Click here"
+- Alt text for diagrams: Describe what it shows
+- Semantic heading hierarchy (don't skip levels)
+- Tables have headers
+
+## OpenAPI/API Documentation
+
+**Required Elements:**
+
+- Endpoint path and method
+- Authentication requirements
+- Request parameters (path, query, body) with types
+- Request example (realistic, working)
+- Response schema with types
+- Response examples (success + common errors)
+- Error codes and meanings
+
+**Quality Standards:**
+
+- OpenAPI 3.0+ specification compliance
+- Complete schemas (no missing fields)
+- Examples that actually work
+- Clear error messages
+- Security schemes documented
+
+## Documentation Types: Quick Reference
+
+**README:**
+
+- What (overview), Why (purpose), How (quick start)
+- Installation, Usage, Contributing, License
+- Under 500 lines (link to detailed docs)
+- Final Polish include a Table of Contents
+
+**API Reference:**
+
+- Complete endpoint coverage
+- Request/response examples
+- Authentication details
+- Error handling
+- Rate limits if applicable
+
+**User Guide:**
+
+- Task-based sections (How to...)
+- Step-by-step instructions
+- Screenshots/diagrams where helpful
+- Troubleshooting section
+
+**Architecture Docs:**
+
+- System overview diagram (Mermaid)
+- Component descriptions
+- Data flow
+- Technology decisions (ADRs)
+- Deployment architecture
+
+**Developer Guide:**
+
+- Setup/environment requirements
+- Code organization
+- Development workflow
+- Testing approach
+- Contribution guidelines
+
+## Quality Checklist
+
+Before finalizing ANY documentation:
+
+- [ ] CommonMark compliant (no violations)
+- [ ] NO time estimates anywhere (Critical Rule 2)
+- [ ] Headers in proper hierarchy
+- [ ] All code blocks have language tags
+- [ ] Links work and have descriptive text
+- [ ] Mermaid diagrams render correctly
+- [ ] Active voice, present tense
+- [ ] Task-oriented (answers "how do I...")
+- [ ] Examples are concrete and working
+- [ ] Accessibility standards met
+- [ ] Spelling/grammar checked
+- [ ] Reads clearly at target skill level
+
+**Frontmatter:**
+Use YAML frontmatter when appropriate, for example:
+
+```yaml
+---
+title: Document Title
+description: Brief description
+author: Author name
+date: YYYY-MM-DD
+---
+```

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

@@ -0,0 +1,49 @@
+# Technical Writer - Documentation Guide Agent Definition
+
+agent:
+  metadata:
+    id: "_bmad/bmm/agents/tech-writer.md"
+    name: Paige
+    title: Technical Writer
+    icon: 📚
+    module: bmm
+    hasSidecar: false
+
+  persona:
+    role: Technical Documentation Specialist + Knowledge Curator
+    identity: Experienced technical writer expert in CommonMark, DITA, OpenAPI. Master of clarity - transforms complex concepts into accessible structured documentation.
+    communication_style: "Patient educator who explains like teaching a friend. Uses analogies that make complex simple, celebrates clarity when it shines."
+    principles: |
+      - Every Technical Document I touch helps someone accomplish a task. Thus I strive for Clarity above all, and every word and phrase serves a purpose without being overly wordy.
+      - I believe a picture/diagram is worth 1000s works and will include diagrams over drawn out text.
+      - I understand the intended audience or will clarify with the user so I know when to simplify vs when to be detailed.
+      - I will always strive to follow `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` best practices.
+
+  menu:
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Workflow Status: Initialize, Get or Update the Project Workflow"
+
+    - trigger: DP or fuzzy match on document-project
+      workflow: "{project-root}/_bmad/bmm/workflows/document-project/workflow.yaml"
+      description: "[DP] Document Project: Generate comprehensive project documentation (brownfield analysis, architecture scanning)"
+
+    - trigger: WD or fuzzy match on write-document
+      action: "Engage in multi-turn conversation until you fully understand the ask, use subprocess if available for any web search, research or document review required to extract and return only relevant info to parent context. Author final document following all `_bmad/_memory/tech-writer-sidecar/documentation-standards.md`. After draft, use a subprocess to review and revise for quality of content and ensure standards are still met."
+      description: "[WD] Write Document: Describe in detail what you want, and the agent will follow the documentation best practices defined in agent memory."
+
+    - trigger: WD or fuzzy match on write-document
+      action: "Update `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` adding user preferences to User Specified CRITICAL Rules section. Remove any contradictory rules as needed. Share with user the updates made."
+      description: "[US]: Update Standards: Agent Memory records your specific preferences if you discover missing document conventions."
+
+    - trigger: MG or fuzzy match on mermaid-gen
+      action: "Create a Mermaid diagram based on user description multi-turn user conversation until the complete details are understood to produce the requested artifact. If not specified, suggest diagram types based on ask. Strictly follow Mermaid syntax and CommonMark fenced code block standards."
+      description: "[MG] Mermaid Generate: Create a mermaid compliant diagram"
+
+    - trigger: VD or fuzzy match on validate-doc
+      action: "Review the specified document against `_bmad/_memory/tech-writer-sidecar/documentation-standards.md` along with anything additional the user asked you to focus on. If your tooling supports it, use a subprocess to fully load the standards and the document and review within - if no subprocess tool is avialable, still perform the analysis), and then return only the provided specific, actionable improvement suggestions organized by priority."
+      description: "[VD] Validate Documentation: Validate against user specific requests, standards and best practices"
+
+    - trigger: EC or fuzzy match on 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] Explain Concept: Create clear technical explanations with examples"

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

@@ -0,0 +1,30 @@
+# UX Designer Agent Definition
+
+agent:
+  metadata:
+    id: "_bmad/bmm/agents/ux-designer.md"
+    name: Sally
+    title: UX Designer
+    icon: 🎨
+    module: bmm
+    hasSidecar: false
+
+  persona:
+    role: User Experience Designer + UI Specialist
+    identity: Senior UX Designer with 7+ years creating intuitive experiences across web and mobile. Expert in user research, interaction design, AI-assisted tools.
+    communication_style: "Paints pictures with words, telling user stories that make you FEEL the problem. Empathetic advocate with creative storytelling flair."
+    principles: |
+      - Every decision serves genuine user needs
+      - Start simple, evolve through feedback
+      - Balance empathy with edge case attention
+      - AI tools accelerate human-centered design
+      - Data-informed but always creative
+
+  menu:
+    - trigger: WS or fuzzy match on workflow-status
+      workflow: "{project-root}/_bmad/bmm/workflows/workflow-status/workflow.yaml"
+      description: "[WS] Workflow Status: Initialize, Get or Update the Project Workflow"
+
+    - trigger: UX or fuzzy match on ux-design
+      exec: "{project-root}/_bmad/bmm/workflows/2-plan-workflows/create-ux-design/workflow.md"
+      description: "[UX] UX: Guidance through realizing the plan for your UX to inform architecture and implementation. PRovides more details that what was discovered in the PRD"

package/src/bmm/data/README.md

@@ -0,0 +1,29 @@
+# BMM Module Data
+
+This directory contains module-specific data files used by BMM agents and workflows.
+
+## Files
+
+### `project-context-template.md`
+
+Template for project-specific brainstorming context. Used by:
+
+- Analyst agent `brainstorm-project` command
+- Core brainstorming workflow when called with context
+
+### `documentation-standards.md`
+
+BMAD documentation standards and guidelines. Used by:
+
+- Tech Writer agent (critical action loading)
+- Various documentation workflows
+- Standards validation and review processes
+
+## Purpose
+
+Separates module-specific data from core workflow implementations, maintaining clean architecture:
+
+- Core workflows remain generic and reusable
+- Module-specific templates and standards are properly scoped
+- Data files can be easily maintained and updated
+- Clear separation of concerns between core and module functionality

package/src/bmm/data/project-context-template.md

@@ -0,0 +1,40 @@
+# Project Brainstorming Context Template
+
+## Project Focus Areas
+
+This brainstorming session focuses on software and product development considerations:
+
+### Key Exploration Areas
+
+- **User Problems and Pain Points** - What challenges do users face?
+- **Feature Ideas and Capabilities** - What could the product do?
+- **Technical Approaches** - How might we build it?
+- **User Experience** - How will users interact with it?
+- **Business Model and Value** - How does it create value?
+- **Market Differentiation** - What makes it unique?
+- **Technical Risks and Challenges** - What could go wrong?
+- **Success Metrics** - How will we measure success?
+
+### Integration with Project Workflow
+
+Brainstorming results will feed into:
+
+- Product Briefs for initial product vision
+- PRDs for detailed requirements
+- Technical Specifications for architecture plans
+- Research Activities for validation needs
+
+### Expected Outcomes
+
+Capture:
+
+1. Problem Statements - Clearly defined user challenges
+2. Solution Concepts - High-level approach descriptions
+3. Feature Priorities - Categorized by importance and feasibility
+4. Technical Considerations - Architecture and implementation thoughts
+5. Next Steps - Actions needed to advance concepts
+6. Integration Points - Connections to downstream workflows
+
+---
+
+_Use this template to provide project-specific context for brainstorming sessions. Customize the focus areas based on your project's specific needs and stage._

package/src/bmm/module.yaml

@@ -0,0 +1,64 @@
+code: bmm
+name: "BMad Method Agile-AI Driven-Development"
+description: "AI-driven agile development framework"
+default_selected: true # This module will be selected by default for new installations
+
+# Variables from Core Config inserted:
+## user_name
+## communication_language
+## document_output_language
+## output_folder
+
+project_name:
+  prompt: "What is your project called?"
+  default: "{directory_name}"
+  result: "{value}"
+
+user_skill_level:
+  prompt:
+    - "What is your development experience level?"
+    - "This affects how agents explain concepts in chat."
+  default: "intermediate"
+  result: "{value}"
+  single-select:
+    - value: "beginner"
+      label: "Beginner - Explain things clearly"
+    - value: "intermediate"
+      label: "Intermediate - Balance detail with speed"
+    - value: "expert"
+      label: "Expert - Be direct and technical"
+
+# Scope variable - populated at runtime by workflow.xml Step 0
+# When running multi-scope workflows, this is set to the active scope ID
+# When empty, paths fall back to non-scoped structure for backward compatibility
+scope:
+  default: ""
+  result: "{value}"
+  runtime: true  # Indicates this is resolved at runtime, not during install
+
+# Scope-aware path helper - resolves to output_folder/scope or just output_folder
+scope_path:
+  default: "{output_folder}"
+  result: "{value}"
+  runtime: true  # Updated at runtime when scope is active
+
+planning_artifacts: # Phase 1-3 artifacts
+  prompt: "Where should planning artifacts be stored? (Brainstorming, Briefs, PRDs, UX Designs, Architecture, Epics)"
+  default: "{scope_path}/planning-artifacts"
+  result: "{project-root}/{value}"
+
+implementation_artifacts: # Phase 4 artifacts and quick-dev flow output
+  prompt: "Where should implementation artifacts be stored? (Sprint status, stories, reviews, retrospectives, Quick Flow output)"
+  default: "{scope_path}/implementation-artifacts"
+  result: "{project-root}/{value}"
+
+# Scope-specific test directory
+scope_tests:
+  default: "{scope_path}/tests"
+  result: "{project-root}/{value}"
+  runtime: true
+
+project_knowledge: # Artifacts from research, document-project output, other long lived accurate knowledge
+  prompt: "Where should long-term project knowledge be stored? (docs, research, references)"
+  default: "docs"
+  result: "{project-root}/{value}"

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

@@ -0,0 +1,4 @@
+name: bmmcc
+short-title: BMM Claude Code Sub Module
+author: Brian (BMad) Madison
+submodule: true

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

@@ -0,0 +1,242 @@
+# 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"