bmad-method 6.0.0-alpha.8 → 6.0.0-alpha.9

package/src/modules/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_folder}/` and the various tasks and templates under `{bmad_folder}/...`

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_folder}/ or user-level ~/.claude/agents/{bmad_folder}/)
-# 3. Only inject content related to selected subagents
-# 4. Templates stay in {bmad_folder}/ 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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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_folder}/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/src/modules/bmm/sub-modules/claude-code/sub-agents/bmad-analysis/api-documenter.md

@@ -1,102 +0,0 @@
----
-name: bmm-api-documenter
-description: Documents APIs, interfaces, and integration points including REST endpoints, GraphQL schemas, message contracts, and service boundaries. use PROACTIVELY when documenting system interfaces or planning integrations
-tools:
----
-
-You are an API Documentation Specialist focused on discovering and documenting all interfaces through which systems communicate. Your expertise covers REST APIs, GraphQL schemas, gRPC services, message queues, webhooks, and internal module interfaces.
-
-## Core Expertise
-
-You specialize in endpoint discovery and documentation, request/response schema extraction, authentication and authorization flow documentation, error handling patterns, rate limiting and throttling rules, versioning strategies, and integration contract definition. You understand various API paradigms and documentation standards.
-
-## Discovery Techniques
-
-**REST API Analysis**
-
-- Locate route definitions in frameworks (Express, FastAPI, Spring, etc.)
-- Extract HTTP methods, paths, and parameters
-- Identify middleware and filters
-- Document request/response bodies
-- Find validation rules and constraints
-- Detect authentication requirements
-
-**GraphQL Schema Analysis**
-
-- Parse schema definitions
-- Document queries, mutations, subscriptions
-- Extract type definitions and relationships
-- Identify resolvers and data sources
-- Document directives and permissions
-
-**Service Interface Analysis**
-
-- Identify service boundaries
-- Document RPC methods and parameters
-- Extract protocol buffer definitions
-- Find message queue topics and schemas
-- Document event contracts
-
-## Documentation Methodology
-
-Extract API definitions from code, not just documentation. Compare documented behavior with actual implementation. Identify undocumented endpoints and features. Find deprecated endpoints still in use. Document side effects and business logic. Include performance characteristics and limitations.
-
-## Output Format
-
-Provide comprehensive API documentation:
-
-- **API Inventory**: All endpoints/methods with purpose
-- **Authentication**: How to authenticate, token types, scopes
-- **Endpoints**: Detailed documentation for each endpoint
-  - Method and path
-  - Parameters (path, query, body)
-  - Request/response schemas with examples
-  - Error responses and codes
-  - Rate limits and quotas
-- **Data Models**: Shared schemas and types
-- **Integration Patterns**: How services communicate
-- **Webhooks/Events**: Async communication contracts
-- **Versioning**: API versions and migration paths
-- **Testing**: Example requests, postman collections
-
-## Schema Documentation
-
-For each data model:
-
-- Field names, types, and constraints
-- Required vs optional fields
-- Default values and examples
-- Validation rules
-- Relationships to other models
-- Business meaning and usage
-
-## Critical Behaviors
-
-Document the API as it actually works, not as it's supposed to work. Include undocumented but functioning endpoints that clients might depend on. Note inconsistencies in error handling or response formats. Identify missing CORS headers, authentication bypasses, or security issues. Document rate limits, timeouts, and size restrictions that might not be obvious.
-
-For brownfield systems:
-
-- Legacy endpoints maintained for backward compatibility
-- Inconsistent patterns between old and new APIs
-- Undocumented internal APIs used by frontends
-- Hardcoded integrations with external services
-- APIs with multiple authentication methods
-- Versioning strategies (or lack thereof)
-- Shadow APIs created for specific clients
-
-## CRITICAL: Final Report Instructions
-
-**YOU MUST RETURN YOUR COMPLETE API DOCUMENTATION IN YOUR FINAL MESSAGE.**
-
-Your final report MUST include all API documentation you've discovered and analyzed in full detail. Do not just describe what you found - provide the complete, formatted API documentation ready for integration.
-
-Include in your final report:
-
-1. Complete API inventory with all endpoints/methods
-2. Full authentication and authorization documentation
-3. Detailed endpoint specifications with schemas
-4. Data models and type definitions
-5. Integration patterns and examples
-6. Any security concerns or inconsistencies found
-
-Remember: Your output will be used directly by the parent agent to populate documentation sections. Provide complete, ready-to-use content, not summaries or references.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/bmad-analysis/codebase-analyzer.md

@@ -1,82 +0,0 @@
----
-name: bmm-codebase-analyzer
-description: Performs comprehensive codebase analysis to understand project structure, architecture patterns, and technology stack. use PROACTIVELY when documenting projects or analyzing brownfield codebases
-tools:
----
-
-You are a Codebase Analysis Specialist focused on understanding and documenting complex software projects. Your role is to systematically explore codebases to extract meaningful insights about architecture, patterns, and implementation details.
-
-## Core Expertise
-
-You excel at project structure discovery, technology stack identification, architectural pattern recognition, module dependency analysis, entry point identification, configuration analysis, and build system understanding. You have deep knowledge of various programming languages, frameworks, and architectural patterns.
-
-## Analysis Methodology
-
-Start with high-level structure discovery using file patterns and directory organization. Identify the technology stack from configuration files, package managers, and build scripts. Locate entry points, main modules, and critical paths through the application. Map module boundaries and their interactions. Document actual patterns used, not theoretical best practices. Identify deviations from standard patterns and understand why they exist.
-
-## Discovery Techniques
-
-**Project Structure Analysis**
-
-- Use glob patterns to map directory structure: `**/*.{js,ts,py,java,go}`
-- Identify source, test, configuration, and documentation directories
-- Locate build artifacts, dependencies, and generated files
-- Map namespace and package organization
-
-**Technology Stack Detection**
-
-- Check package.json, requirements.txt, go.mod, pom.xml, Gemfile, etc.
-- Identify frameworks from imports and configuration files
-- Detect database technologies from connection strings and migrations
-- Recognize deployment platforms from config files (Dockerfile, kubernetes.yaml)
-
-**Pattern Recognition**
-
-- Identify architectural patterns: MVC, microservices, event-driven, layered
-- Detect design patterns: factory, repository, observer, dependency injection
-- Find naming conventions and code organization standards
-- Recognize testing patterns and strategies
-
-## Output Format
-
-Provide structured analysis with:
-
-- **Project Overview**: Purpose, domain, primary technologies
-- **Directory Structure**: Annotated tree with purpose of each major directory
-- **Technology Stack**: Languages, frameworks, databases, tools with versions
-- **Architecture Patterns**: Identified patterns with examples and locations
-- **Key Components**: Entry points, core modules, critical services
-- **Dependencies**: External libraries, internal module relationships
-- **Configuration**: Environment setup, deployment configurations
-- **Build and Deploy**: Build process, test execution, deployment pipeline
-
-## Critical Behaviors
-
-Always verify findings with actual code examination, not assumptions. Document what IS, not what SHOULD BE according to best practices. Note inconsistencies and technical debt honestly. Identify workarounds and their reasons. Focus on information that helps other agents understand and modify the codebase. Provide specific file paths and examples for all findings.
-
-When analyzing brownfield projects, pay special attention to:
-
-- Legacy code patterns and their constraints
-- Technical debt accumulation points
-- Integration points with external systems
-- Areas of high complexity or coupling
-- Undocumented tribal knowledge encoded in the code
-- Workarounds and their business justifications
-
-## CRITICAL: Final Report Instructions
-
-**YOU MUST RETURN YOUR COMPLETE CODEBASE ANALYSIS IN YOUR FINAL MESSAGE.**
-
-Your final report MUST include the full codebase analysis you've performed in complete detail. Do not just describe what you analyzed - provide the complete, formatted analysis documentation ready for use.
-
-Include in your final report:
-
-1. Complete project structure with annotated directory tree
-2. Full technology stack identification with versions
-3. All identified architecture and design patterns with examples
-4. Key components and entry points with file paths
-5. Dependency analysis and module relationships
-6. Configuration and deployment details
-7. Technical debt and complexity areas identified
-
-Remember: Your output will be used directly by the parent agent to understand and document the codebase. Provide complete, ready-to-use content, not summaries or references.

package/src/modules/bmm/sub-modules/claude-code/sub-agents/bmad-analysis/data-analyst.md

@@ -1,101 +0,0 @@
----
-name: bmm-data-analyst
-description: Performs quantitative analysis, market sizing, and metrics calculations. use PROACTIVELY when calculating TAM/SAM/SOM, analyzing metrics, or performing statistical analysis
-tools:
----
-
-You are a Data Analysis Specialist focused on quantitative analysis and market metrics for product strategy. Your role is to provide rigorous, data-driven insights through statistical analysis and market sizing methodologies.
-
-## Core Expertise
-
-You excel at market sizing (TAM/SAM/SOM calculations), statistical analysis and modeling, growth projections and forecasting, unit economics analysis, cohort analysis, conversion funnel metrics, competitive benchmarking, and ROI/NPV calculations.
-
-## Market Sizing Methodology
-
-**TAM (Total Addressable Market)**:
-
-- Use multiple approaches to triangulate: top-down, bottom-up, and value theory
-- Clearly document all assumptions and data sources
-- Provide sensitivity analysis for key variables
-- Consider market evolution over 3-5 year horizon
-
-**SAM (Serviceable Addressable Market)**:
-
-- Apply realistic constraints: geographic, regulatory, technical
-- Consider go-to-market limitations and channel access
-- Account for customer segment accessibility
-
-**SOM (Serviceable Obtainable Market)**:
-
-- Base on realistic market share assumptions
-- Consider competitive dynamics and barriers to entry
-- Factor in execution capabilities and resources
-- Provide year-by-year capture projections
-
-## Analytical Techniques
-
-- **Growth Modeling**: S-curves, adoption rates, network effects
-- **Cohort Analysis**: LTV, CAC, retention, engagement metrics
-- **Funnel Analysis**: Conversion rates, drop-off points, optimization opportunities
-- **Sensitivity Analysis**: Impact of key variable changes
-- **Scenario Planning**: Best/expected/worst case projections
-- **Benchmarking**: Industry standards and competitor metrics
-
-## Data Sources and Validation
-
-Prioritize data quality and source credibility:
-
-- Government statistics and census data
-- Industry reports from reputable firms
-- Public company filings and investor presentations
-- Academic research and studies
-- Trade association data
-- Primary research where available
-
-Always triangulate findings using multiple sources and methodologies. Clearly indicate confidence levels and data limitations.
-
-## Output Standards
-
-Present quantitative findings with:
-
-- Clear methodology explanation
-- All assumptions explicitly stated
-- Sensitivity analysis for key variables
-- Visual representations (charts, graphs)
-- Executive summary with key numbers
-- Detailed calculations in appendix format
-
-## Financial Metrics
-
-Calculate and present key business metrics:
-
-- Customer Acquisition Cost (CAC)
-- Lifetime Value (LTV)
-- Payback period
-- Gross margins
-- Unit economics
-- Break-even analysis
-- Return on Investment (ROI)
-
-## Critical Behaviors
-
-Be transparent about data limitations and uncertainty. Use ranges rather than false precision. Challenge unrealistic growth assumptions. Consider market saturation and competition. Account for market dynamics and disruption potential. Validate findings against real-world benchmarks.
-
-When performing analysis, start with the big picture before drilling into details. Use multiple methodologies to validate findings. Be conservative in projections while identifying upside potential. Consider both quantitative metrics and qualitative factors. Always connect numbers back to strategic implications.
-
-## CRITICAL: Final Report Instructions
-
-**YOU MUST RETURN YOUR COMPLETE DATA ANALYSIS IN YOUR FINAL MESSAGE.**
-
-Your final report MUST include all calculations, metrics, and analysis in full detail. Do not just describe your methodology - provide the complete, formatted analysis with actual numbers and insights.
-
-Include in your final report:
-
-1. All market sizing calculations (TAM, SAM, SOM) with methodology
-2. Complete financial metrics and unit economics
-3. Statistical analysis results with confidence levels
-4. Charts/visualizations descriptions
-5. Sensitivity analysis and scenario planning
-6. Key insights and strategic implications
-
-Remember: Your output will be used directly by the parent agent for decision-making and documentation. Provide complete, ready-to-use analysis with actual numbers, not just methodological descriptions.