bmad-method 6.0.0-alpha.12 → 6.0.0-alpha.14

package/src/modules/bmm/workflows/1-analysis/domain-research/template.md

@@ -1,180 +0,0 @@
-# Domain Brief - {project_name}
-
-Generated: {date}
-Domain: {primary_domain}
-Complexity: {complexity_level}
-
-## Executive Summary
-
-{brief_overview_of_domain_research_findings}
-
-## Domain Overview
-
-### Industry Context
-
-{domain_overview}
-
-### Regulatory Landscape
-
-{regulatory_environment}
-
-### Key Stakeholders
-
-{stakeholder_analysis}
-
-## Critical Concerns
-
-### Compliance Requirements
-
-{concern_mapping}
-
-### Technical Constraints
-
-{technical_limitations_from_domain}
-
-### Safety/Risk Considerations
-
-{safety_risk_factors}
-
-## Regulatory Requirements
-
-{regulatory_requirements}
-
-## Industry Standards
-
-{industry_standards}
-
-## Practical Implications
-
-### Architecture Impact
-
-{architecture_implications}
-
-### Development Impact
-
-{development_implications}
-
-### Timeline Impact
-
-{timeline_implications}
-
-### Cost Impact
-
-{cost_implications}
-
-## Domain Patterns
-
-### Established Patterns
-
-{domain_patterns}
-
-### Innovation Opportunities
-
-{innovation_notes}
-
-## Risk Assessment
-
-### Identified Risks
-
-{risk_assessment}
-
-### Mitigation Strategies
-
-{mitigation_approaches}
-
-## Validation Strategy
-
-### Compliance Validation
-
-{compliance_validation_approach}
-
-### Technical Validation
-
-{technical_validation_approach}
-
-### Domain Expert Validation
-
-{expert_validation_approach}
-
-## Key Decisions
-
-{key_decisions}
-
-## Recommendations
-
-### Must Have (Critical)
-
-{critical_requirements}
-
-### Should Have (Important)
-
-{important_requirements}
-
-### Consider (Nice-to-Have)
-
-{optional_enhancements}
-
-### Development Sequence
-
-{recommended_sequence}
-
-### Required Expertise
-
-{expertise_needed}
-
-## PRD Integration Guide
-
-### Summary for PRD
-
-{summary_for_prd}
-
-### Requirements to Incorporate
-
-- {requirement_1}
-- {requirement_2}
-- {requirement_3}
-
-### Architecture Considerations
-
-- {architecture_consideration_1}
-- {architecture_consideration_2}
-
-### Development Considerations
-
-- {development_consideration_1}
-- {development_consideration_2}
-
-## References
-
-### Regulations Researched
-
-- {regulation_1_with_link}
-- {regulation_2_with_link}
-
-### Standards Referenced
-
-- {standard_1_with_link}
-- {standard_2_with_link}
-
-### Additional Resources
-
-- {resource_1}
-- {resource_2}
-
-## Appendix
-
-### Research Notes
-
-{detailed_research_notes}
-
-### Conversation Highlights
-
-{key_discussion_points_with_user}
-
-### Open Questions
-
-{questions_requiring_further_research}
-
----
-
-_This domain brief was created through collaborative research between {user_name} and the AI facilitator. It should be referenced during PRD creation and updated as new domain insights emerge._

package/src/modules/bmm/workflows/1-analysis/domain-research/workflow.yaml

@@ -1,56 +0,0 @@
-# Domain Research Workflow Configuration
-name: domain-research
-description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
-author: "BMad"
-
-# Critical variables from config
-config_source: "{project-root}/{bmad_folder}/bmm/config.yaml"
-output_folder: "{config_source}:output_folder"
-user_name: "{config_source}:user_name"
-communication_language: "{config_source}:communication_language"
-document_output_language: "{config_source}:document_output_language"
-user_skill_level: "{config_source}:user_skill_level"
-date: system-generated
-
-# Module path and component files
-installed_path: "{project-root}/{bmad_folder}/bmm/workflows/1-analysis/domain-research"
-instructions: "{installed_path}/instructions.md"
-template: "{installed_path}/template.md"
-
-# Optional knowledge base (if exists)
-domain_knowledge_base: "{installed_path}/domain-knowledge-base.md"
-
-# Output configuration
-default_output_file: "{output_folder}/domain-brief.md"
-
-standalone: true
-
-# Web bundle configuration for standalone deployment
-web_bundle:
-  name: "domain-research"
-  description: "Collaborative exploration of domain-specific requirements, regulations, and patterns for complex projects"
-  author: "BMad"
-
-  # Core workflow files ({bmad_folder}/-relative paths)
-  instructions: "{bmad_folder}/bmm/workflows/1-analysis/domain-research/instructions.md"
-  template: "{bmad_folder}/bmm/workflows/1-analysis/domain-research/template.md"
-
-  # Default configuration values (can be overridden during bundle setup)
-  defaults:
-    user_name: "User"
-    communication_language: "English"
-    document_output_language: "English"
-    user_skill_level: "intermediate"
-    output_folder: "./output"
-
-  # Input/output configuration for web deployment
-  default_output_file: "{output_folder}/domain-brief.md"
-
-  # Complete file list - ALL files this workflow depends on
-  web_bundle_files:
-    # Core workflow files
-    - "{bmad_folder}/bmm/workflows/1-analysis/domain-research/instructions.md"
-    - "{bmad_folder}/bmm/workflows/1-analysis/domain-research/template.md"
-
-    # Task dependencies (referenced in instructions.md)
-    - "{bmad_folder}/core/tasks/workflow.xml"

package/src/modules/bmm/workflows/1-analysis/product-brief/checklist.md

@@ -1,115 +0,0 @@
-# Product Brief Validation Checklist
-
-## Document Structure
-
-- [ ] All required sections are present (Executive Summary through Appendices)
-- [ ] No placeholder text remains (e.g., [TODO], [NEEDS CONFIRMATION], {{variable}})
-- [ ] Document follows the standard brief template format
-- [ ] Sections are properly numbered and formatted with headers
-- [ ] Cross-references between sections are accurate
-
-## Executive Summary Quality
-
-- [ ] Product concept is explained in 1-2 clear sentences
-- [ ] Primary problem is clearly identified
-- [ ] Target market is specifically named (not generic)
-- [ ] Value proposition is compelling and differentiated
-- [ ] Summary accurately reflects the full document content
-
-## Problem Statement
-
-- [ ] Current state pain points are specific and measurable
-- [ ] Impact is quantified where possible (time, money, opportunities)
-- [ ] Explanation of why existing solutions fall short is provided
-- [ ] Urgency for solving the problem now is justified
-- [ ] Problem is validated with evidence or data points
-
-## Solution Definition
-
-- [ ] Core approach is clearly explained without implementation details
-- [ ] Key differentiators from existing solutions are identified
-- [ ] Explanation of why this will succeed is compelling
-- [ ] Solution aligns directly with stated problems
-- [ ] Vision paints a clear picture of the user experience
-
-## Target Users
-
-- [ ] Primary user segment has specific demographic/firmographic profile
-- [ ] User behaviors and current workflows are documented
-- [ ] Specific pain points are tied to user segments
-- [ ] User goals are clearly articulated
-- [ ] Secondary segment (if applicable) is equally detailed
-- [ ] Avoids generic personas like "busy professionals"
-
-## Goals and Metrics
-
-- [ ] Business objectives include measurable outcomes with targets
-- [ ] User success metrics focus on behaviors, not features
-- [ ] 3-5 KPIs are defined with clear definitions
-- [ ] All goals follow SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound)
-- [ ] Success metrics align with problem statement
-
-## MVP Scope
-
-- [ ] Core features list contains only true must-haves
-- [ ] Each core feature includes rationale for why it's essential
-- [ ] Out of scope section explicitly lists deferred features
-- [ ] MVP success criteria are specific and measurable
-- [ ] Scope is genuinely minimal and viable
-- [ ] No feature creep evident in "must-have" list
-
-## Technical Considerations
-
-- [ ] Target platforms are specified (web/mobile/desktop)
-- [ ] Browser/OS support requirements are documented
-- [ ] Performance requirements are defined if applicable
-- [ ] Accessibility requirements are noted
-- [ ] Technology preferences are marked as preferences, not decisions
-- [ ] Integration requirements with existing systems are identified
-
-## Constraints and Assumptions
-
-- [ ] Budget constraints are documented if known
-- [ ] Timeline or deadline pressures are specified
-- [ ] Team/resource limitations are acknowledged
-- [ ] Technical constraints are clearly stated
-- [ ] Key assumptions are listed and testable
-- [ ] Assumptions will be validated during development
-
-## Risk Assessment (if included)
-
-- [ ] Key risks include potential impact descriptions
-- [ ] Open questions are specific and answerable
-- [ ] Research areas are identified with clear objectives
-- [ ] Risk mitigation strategies are suggested where applicable
-
-## Overall Quality
-
-- [ ] Language is clear and free of jargon
-- [ ] Terminology is used consistently throughout
-- [ ] Document is ready for handoff to Product Manager
-- [ ] All [PM-TODO] items are clearly marked if present
-- [ ] References and source documents are properly cited
-
-## Completeness Check
-
-- [ ] Document provides sufficient detail for PRD creation
-- [ ] All user inputs have been incorporated
-- [ ] Market research findings are reflected if provided
-- [ ] Competitive analysis insights are included if available
-- [ ] Brief aligns with overall product strategy
-
-## Final Validation
-
-### Critical Issues Found:
-
-- [ ] None identified
-
-### Minor Issues to Address:
-
-- [ ] List any minor issues here
-
-### Ready for PM Handoff:
-
-- [ ] Yes, brief is complete and validated
-- [ ] No, requires additional work (specify above)