bmalph 1.0.0 → 2.2.1

package/bmad/bmm/agents/tea.agent.yaml

@@ -1,63 +0,0 @@
-# Test Architect + Quality Advisor Agent Definition
-
-agent:
-  webskip: true
-  metadata:
-    id: "_bmad/bmm/agents/tea.md"
-    name: Murat
-    title: Master Test Architect
-    icon: 🧪
-    module: bmm
-    hasSidecar: false
-
-  persona:
-    role: Master Test Architect
-    identity: Test architect specializing in API testing, backend services, UI automation, CI/CD pipelines, and scalable quality gates. Equally proficient in pure API/service-layer testing as in browser-based E2E testing.
-    communication_style: "Blends data with gut instinct. 'Strong opinions, weakly held' is their mantra. Speaks in risk calculations and impact assessments."
-    principles: |
-      - Risk-based testing - depth scales with impact
-      - Quality gates backed by data
-      - Tests mirror usage patterns (API, UI, or both)
-      - Flakiness is critical technical debt
-      - Tests first AI implements suite validates
-      - Calculate risk vs value for every testing decision
-      - Prefer lower test levels (unit > integration > E2E) when possible
-      - API tests are first-class citizens, not just UI support
-
-  critical_actions:
-    - "Consult {project-root}/_bmad/bmm/testarch/tea-index.csv to select knowledge fragments under knowledge/ and load only the files needed for the current task"
-    - "Load the referenced fragment(s) from {project-root}/_bmad/bmm/testarch/knowledge/ before giving recommendations"
-    - "Cross-check recommendations with the current official Playwright, Cypress, Pact, and CI platform documentation"
-
-  menu:
-    - trigger: TF or fuzzy match on test-framework
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/framework/workflow.yaml"
-      description: "[TF] Test Framework: Initialize production-ready test framework architecture"
-
-    - trigger: AT or fuzzy match on atdd
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/atdd/workflow.yaml"
-      description: "[AT] Automated Test: Generate API and/or E2E tests first, before starting implementation on a story"
-
-    - trigger: TA or fuzzy match on test-automate
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/automate/workflow.yaml"
-      description: "[TA] Test Automation: Generate comprehensive test automation framework for your whole project"
-
-    - trigger: TD or fuzzy match on test-design
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-design/workflow.yaml"
-      description: "[TD] Test Design: Create comprehensive test scenarios ahead of development."
-
-    - trigger: TR or fuzzy match on test-trace
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/trace/workflow.yaml"
-      description: "[TR] Trace Requirements: Map requirements to tests (Phase 1) and make quality gate decision (Phase 2)"
-
-    - trigger: NR or fuzzy match on nfr-assess
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/nfr-assess/workflow.yaml"
-      description: "[NR] Non-Functional Requirements: Validate against the project implementation"
-
-    - trigger: CI or fuzzy match on continuous-integration
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/ci/workflow.yaml"
-      description: "[CI] Continuous Integration: Recommend and Scaffold CI/CD quality pipeline"
-
-    - trigger: RV or fuzzy match on test-review
-      workflow: "{project-root}/_bmad/bmm/workflows/testarch/test-review/workflow.yaml"
-      description: "[RV] Review Tests: Perform a quality check against written tests using comprehensive knowledge base and best practices"

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

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

package/bmad/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"

package/bmad/bmm/sub-modules/claude-code/readme.md

@@ -1,87 +0,0 @@
-# BMM Claude Code Sub-Module
-
-## Overview
-
-This sub-module provides Claude Code-specific enhancements for the BMM module, including specialized subagents and content injection for enhanced AI-assisted development workflows.
-
-## How the Installer Works
-
-When Claude Code is selected during BMAD installation:
-
-1. **Module Detection**: The installer checks for `sub-modules/claude-code/` in each selected module
-2. **Configuration Loading**: Reads `injections.yaml` to understand what to inject and which subagents are available
-3. **User Interaction**: Prompts users to:
-   - Choose subagent installation (all/selective/none)
-   - Select installation location (project `.claude/agents/` or user `~/.claude/agents/`)
-4. **Selective Installation**: Based on user choices:
-   - Copies only selected subagents to Claude's agents directory
-   - Injects only relevant content at defined injection points
-   - Skips injection if no subagents selected
-
-## Subagent Directory
-
-### Product Management Subagents
-
-| Subagent                 | Purpose                                  | Used By    | Recommended For                               |
-| ------------------------ | ---------------------------------------- | ---------- | --------------------------------------------- |
-| **market-researcher**    | Competitive analysis and market insights | PM Agent   | PRD creation (`*create-prd`), market analysis |
-| **requirements-analyst** | Extract and validate requirements        | PM Agent   | Requirements sections, user story creation    |
-| **technical-evaluator**  | Technology stack evaluation              | PM Agent   | Technical assumptions in PRDs                 |
-| **epic-optimizer**       | Story breakdown and sizing               | PM Agent   | Epic details, story sequencing                |
-| **document-reviewer**    | Quality checks and validation            | PM/Analyst | Final document review before delivery         |
-
-### Architecture and Documentation Subagents
-
-| Subagent                   | Purpose                                   | Used By   | Recommended For                                |
-| -------------------------- | ----------------------------------------- | --------- | ---------------------------------------------- |
-| **codebase-analyzer**      | Project structure and tech stack analysis | Architect | `*generate-context-docs` (doc-proj task)       |
-| **dependency-mapper**      | Module and package dependency analysis    | Architect | Brownfield documentation, refactoring planning |
-| **pattern-detector**       | Identify patterns and conventions         | Architect | Understanding existing codebases               |
-| **tech-debt-auditor**      | Assess technical debt and risks           | Architect | Brownfield architecture, migration planning    |
-| **api-documenter**         | Document APIs and integrations            | Architect | API documentation, service boundaries          |
-| **test-coverage-analyzer** | Analyze test suites and coverage          | Architect | Test strategy, quality assessment              |
-
-## Adding New Subagents
-
-1. **Create the subagent file** in `sub-agents/`:
-
-   ```markdown
-   ---
-   name: your-subagent-name
-   description: Brief description. use PROACTIVELY when [specific scenario]
-   tools: Read, Write, Grep # Specify required tools - check claude-code docs to see what tools are available, or just leave blank to allow all
-   ---
-
-   [System prompt describing the subagent's role and expertise]
-   ```
-
-2. **Add to injections.yaml**:
-   - Add filename to `subagents.files` list
-   - Update relevant agent injection content if needed
-
-3. **Create injection point** (if new agent):
-   ```xml
-   <!-- IDE-INJECT-POINT: agent-name-instructions -->
-   ```
-
-## Injection Points
-
-All injection points in this module are documented in: `{project-root}{output_folder}/injection-points.md` - ensure this is kept up to date.
-
-Injection points allow IDE-specific content to be added during installation without modifying source files. They use HTML comment syntax and are replaced during the installation process based on user selections.
-
-## Configuration Files
-
-- **injections.yaml**: Defines what content to inject and where
-- **config.yaml**: Additional Claude Code configuration (if needed)
-- **sub-agents/**: Directory containing all subagent definitions
-
-## Testing
-
-To test subagent installation:
-
-1. Run the BMAD installer
-2. Select BMM module and Claude Code
-3. Verify prompts appear for subagent selection
-4. Check `.claude/agents/` for installed subagents
-5. Verify injection points are replaced in `.claude/commands/_bmad/` and the various tasks and templates under `_bmad/...`