bmad-method 5.1.2 → 6.0.0-alpha.0

package/src/modules/bmm/workflows/1-analysis/game-brief/template.md

@@ -0,0 +1,205 @@
+# Game Brief: {{game_name}}
+
+**Date:** {{date}}
+**Author:** {{user_name}}
+**Status:** Draft for GDD Development
+
+---
+
+## Executive Summary
+
+{{executive_summary}}
+
+---
+
+## Game Vision
+
+### Core Concept
+
+{{core_concept}}
+
+### Elevator Pitch
+
+{{elevator_pitch}}
+
+### Vision Statement
+
+{{vision_statement}}
+
+---
+
+## Target Market
+
+### Primary Audience
+
+{{primary_audience}}
+
+### Secondary Audience
+
+{{secondary_audience}}
+
+### Market Context
+
+{{market_context}}
+
+---
+
+## Game Fundamentals
+
+### Core Gameplay Pillars
+
+{{core_gameplay_pillars}}
+
+### Primary Mechanics
+
+{{primary_mechanics}}
+
+### Player Experience Goals
+
+{{player_experience_goals}}
+
+---
+
+## Scope and Constraints
+
+### Target Platforms
+
+{{target_platforms}}
+
+### Development Timeline
+
+{{development_timeline}}
+
+### Budget Considerations
+
+{{budget_considerations}}
+
+### Team Resources
+
+{{team_resources}}
+
+### Technical Constraints
+
+{{technical_constraints}}
+
+---
+
+## Reference Framework
+
+### Inspiration Games
+
+{{inspiration_games}}
+
+### Competitive Analysis
+
+{{competitive_analysis}}
+
+### Key Differentiators
+
+{{key_differentiators}}
+
+---
+
+## Content Framework
+
+### World & Setting
+
+{{world_setting}}
+
+### Narrative Approach
+
+{{narrative_approach}}
+
+### Content Volume
+
+{{content_volume}}
+
+---
+
+## Art & Audio Direction
+
+### Visual Style
+
+{{visual_style}}
+
+### Audio Style
+
+{{audio_style}}
+
+### Production Approach
+
+{{production_approach}}
+
+---
+
+## Risk Assessment
+
+### Key Risks
+
+{{key_risks}}
+
+### Technical Challenges
+
+{{technical_challenges}}
+
+### Market Risks
+
+{{market_risks}}
+
+### Mitigation Strategies
+
+{{mitigation_strategies}}
+
+---
+
+## Success Criteria
+
+### MVP Definition
+
+{{mvp_definition}}
+
+### Success Metrics
+
+{{success_metrics}}
+
+### Launch Goals
+
+{{launch_goals}}
+
+---
+
+## Next Steps
+
+### Immediate Actions
+
+{{immediate_actions}}
+
+### Research Needs
+
+{{research_needs}}
+
+### Open Questions
+
+{{open_questions}}
+
+---
+
+## Appendices
+
+### A. Research Summary
+
+{{research_summary}}
+
+### B. Stakeholder Input
+
+{{stakeholder_input}}
+
+### C. References
+
+{{references}}
+
+---
+
+_This Game Brief serves as the foundational input for Game Design Document (GDD) creation._
+
+_Next Steps: Use the `workflow gdd` command to create detailed game design documentation._

package/src/modules/bmm/workflows/1-analysis/game-brief/workflow.yaml

@@ -0,0 +1,34 @@
+# Game Brief - Interactive Workflow Configuration
+name: game-brief
+description: "Interactive game brief creation workflow that guides users through defining their game vision with multiple input sources and conversational collaboration"
+author: "BMad"
+
+# Critical variables
+config_source: "{project-root}/bmad/bmm/config.yaml"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+date: system-generated
+
+# Optional input documents
+recommended_inputs:
+  - market_research: "Market research document (optional)"
+  - brainstorming_results: "Brainstorming session outputs (optional)"
+  - competitive_analysis: "Competitive game analysis (optional)"
+  - initial_ideas: "Initial game ideas or notes (optional)"
+  - reference_games: "List of inspiration games (optional)"
+
+# Module path and component files
+installed_path: "{project-root}/bmad/bmm/workflows/1-analysis/game-brief"
+template: "{installed_path}/template.md"
+instructions: "{installed_path}/instructions.md"
+validation: "{installed_path}/checklist.md"
+
+# Output configuration
+default_output_file: "{output_folder}/game-brief-{{game_name}}-{{date}}.md"
+
+# Required tools
+required_tools: []
+
+# Workflow settings
+autonomous: false # This is an interactive workflow requiring user collaboration
+brief_format: "comprehensive" # Options: "comprehensive" (full detail) or "executive" (3-page limit)

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

@@ -0,0 +1,180 @@
+# Product Brief Workflow
+
+## Overview
+
+Interactive product brief creation workflow that guides users through defining their product vision with multiple input sources and conversational collaboration. Supports both structured interactive mode and rapid "YOLO" mode for quick draft generation.
+
+## Key Features
+
+- **Dual Mode Operation** - Interactive step-by-step or rapid draft generation
+- **Multi-Input Support** - Integrates market research, competitive analysis, and brainstorming results
+- **Conversational Design** - Guides users through strategic thinking with probing questions
+- **Executive Summary Generation** - Creates compelling summaries for stakeholder communication
+- **Comprehensive Coverage** - Addresses all critical product planning dimensions
+- **Stakeholder Ready** - Generates professional briefs suitable for PM handoff
+
+## Usage
+
+### Basic Invocation
+
+```bash
+workflow product-brief
+```
+
+### With Input Documents
+
+```bash
+# With market research
+workflow product-brief --input market-research.md
+
+# With multiple inputs
+workflow product-brief --input market-research.md --input competitive-analysis.md
+```
+
+### Configuration
+
+- **brief_format**: "comprehensive" (full detail) or "executive" (3-page limit)
+- **autonomous**: false (requires user collaboration)
+- **output_folder**: Location for generated brief
+
+## Workflow Structure
+
+### Files Included
+
+```
+product-brief/
+├── workflow.yaml           # Configuration and metadata
+├── instructions.md         # Interactive workflow steps
+├── template.md            # Product brief document structure
+├── checklist.md           # Validation criteria
+└── README.md              # This file
+```
+
+## Workflow Process
+
+### Phase 1: Initialization and Context (Steps 0-2)
+
+- **Project Setup**: Captures project name and basic context
+- **Input Gathering**: Collects and analyzes available documents
+- **Mode Selection**: Chooses interactive or YOLO collaboration approach
+- **Context Extraction**: Identifies core problems and opportunities
+
+### Phase 2: Interactive Development (Steps 3-12) - Interactive Mode
+
+- **Problem Definition**: Deep dive into user pain points and market gaps
+- **Solution Articulation**: Develops clear value proposition and approach
+- **User Segmentation**: Defines primary and secondary target audiences
+- **Success Metrics**: Establishes measurable goals and KPIs
+- **MVP Scoping**: Ruthlessly defines minimum viable features
+- **Financial Planning**: Assesses ROI and strategic alignment
+- **Technical Context**: Captures platform and technology considerations
+- **Risk Assessment**: Identifies constraints, assumptions, and unknowns
+
+### Phase 3: Rapid Generation (Steps 3-4) - YOLO Mode
+
+- **Complete Draft**: Generates full brief based on initial context
+- **Iterative Refinement**: User-guided section improvements
+- **Quality Validation**: Ensures completeness and consistency
+
+### Phase 4: Finalization (Steps 13-15)
+
+- **Executive Summary**: Creates compelling overview for stakeholders
+- **Supporting Materials**: Compiles research summaries and references
+- **Final Review**: Quality check and handoff preparation
+
+## Output
+
+### Generated Files
+
+- **Primary output**: product-brief-{project_name}-{date}.md
+- **Supporting files**: Research summaries and stakeholder input documentation
+
+### Output Structure
+
+1. **Executive Summary** - High-level product concept and value proposition
+2. **Problem Statement** - Detailed problem analysis with evidence
+3. **Proposed Solution** - Core approach and key differentiators
+4. **Target Users** - Primary and secondary user segments with personas
+5. **Goals & Success Metrics** - Business objectives and measurable KPIs
+6. **MVP Scope** - Must-have features and out-of-scope items
+7. **Post-MVP Vision** - Phase 2 features and long-term roadmap
+8. **Financial Impact** - Investment requirements and ROI projections
+9. **Strategic Alignment** - Connection to company OKRs and initiatives
+10. **Technical Considerations** - Platform requirements and preferences
+11. **Constraints & Assumptions** - Resource limits and key assumptions
+12. **Risks & Open Questions** - Risk assessment and research needs
+13. **Supporting Materials** - Research summaries and references
+
+## Requirements
+
+No special requirements - designed to work with or without existing documentation.
+
+## Best Practices
+
+### Before Starting
+
+1. **Gather Available Research**: Collect any market research, competitive analysis, or user feedback
+2. **Define Stakeholder Audience**: Know who will use this brief for decision-making
+3. **Set Time Boundaries**: Interactive mode requires 60-90 minutes for quality results
+
+### During Execution
+
+1. **Be Specific**: Avoid generic statements - provide concrete examples and data
+2. **Think Strategically**: Focus on "why" and "what" rather than "how"
+3. **Challenge Assumptions**: Use the conversation to test and refine your thinking
+4. **Scope Ruthlessly**: Resist feature creep in MVP definition
+
+### After Completion
+
+1. **Validate with Checklist**: Use included criteria to ensure completeness
+2. **Stakeholder Review**: Share executive summary first, then full brief
+3. **Iterate Based on Feedback**: Product briefs should evolve with new insights
+
+## Troubleshooting
+
+### Common Issues
+
+**Issue**: Brief lacks specificity or contains vague statements
+
+- **Solution**: Restart problem definition with concrete examples and measurable impacts
+- **Check**: Ensure each section answers "so what?" and provides actionable insights
+
+**Issue**: MVP scope is too large or undefined
+
+- **Solution**: Use the "what's the minimum to validate core hypothesis?" filter
+- **Check**: Verify that each MVP feature is truly essential for initial value delivery
+
+**Issue**: Missing strategic context or business justification
+
+- **Solution**: Return to financial impact and strategic alignment sections
+- **Check**: Ensure connection to company goals and clear ROI potential
+
+## Customization
+
+To customize this workflow:
+
+1. **Modify Questions**: Update instructions.md to add industry-specific or company-specific prompts
+2. **Adjust Template**: Customize template.md sections for organizational brief standards
+3. **Add Validation**: Extend checklist.md with company-specific quality criteria
+4. **Configure Modes**: Adjust brief_format settings for different output styles
+
+## Version History
+
+- **v6.0.0** - Interactive conversational design with dual modes
+  - Interactive and YOLO mode support
+  - Multi-input document integration
+  - Executive summary generation
+  - Strategic alignment focus
+
+## Support
+
+For issues or questions:
+
+- Review the workflow creation guide at `/bmad/bmb/workflows/build-workflow/workflow-creation-guide.md`
+- Validate output using `checklist.md`
+- Consider running market research workflow first if lacking business context
+- Consult BMAD documentation for product planning methodology
+
+---
+
+_Part of the BMad Method v6 - BMM (Method) Module_

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

@@ -0,0 +1,115 @@
+# 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 & 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 & 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)