bmad-method 6.0.0-alpha.3 → 6.0.0-alpha.5

package/src/modules/bmm/workflows/1-analysis/brainstorm-project/README.md

@@ -1,113 +0,0 @@
-# Project Brainstorming Workflow
-
-Structured ideation for software projects exploring problem spaces, architectures, and innovative solutions beyond traditional requirements gathering.
-
-## Table of Contents
-
-- [Purpose](#purpose)
-- [Usage](#usage)
-- [Process](#process)
-- [Inputs & Outputs](#inputs--outputs)
-- [Integration](#integration)
-
-## Purpose
-
-Generate multiple solution approaches for software projects through:
-
-- Parallel ideation tracks (architecture, UX, integration, value delivery)
-- Technical-business alignment from inception
-- Hidden assumption discovery
-- Innovation beyond obvious solutions
-
-## Usage
-
-```bash
-# Run brainstorming session
-bmad bmm *brainstorm-project
-
-# Or via Analyst agent
-*brainstorm-project
-```
-
-## Process
-
-### 1. Context Capture
-
-- Business objectives and constraints
-- Technical environment
-- Stakeholder needs
-- Success criteria
-
-### 2. Parallel Ideation
-
-- **Architecture Track**: Technical approaches with trade-offs
-- **UX Track**: Interface paradigms and user journeys
-- **Integration Track**: System connection patterns
-- **Value Track**: Feature prioritization and delivery
-
-### 3. Solution Synthesis
-
-- Evaluate feasibility and impact
-- Align with strategic objectives
-- Surface hidden assumptions
-- Generate recommendations
-
-## Inputs & Outputs
-
-### Inputs
-
-| Input             | Type     | Purpose                                       |
-| ----------------- | -------- | --------------------------------------------- |
-| Project Context   | Document | Business objectives, environment, constraints |
-| Problem Statement | Optional | Core challenge or opportunity                 |
-
-### Outputs
-
-| Output                   | Content                                     |
-| ------------------------ | ------------------------------------------- |
-| Architecture Proposals   | Multiple approaches with trade-off analysis |
-| Value Framework          | Prioritized features aligned to objectives  |
-| Risk Analysis            | Dependencies, challenges, opportunities     |
-| Strategic Recommendation | Synthesized direction with rationale        |
-
-## Integration
-
-### Workflow Chain
-
-1. **brainstorm-project** ← Current step
-2. research (optional deep dive)
-3. product-brief (strategic document)
-4. Phase 2 planning (PRD/tech-spec)
-
-### Feed Into
-
-- Product Brief development
-- Architecture decisions
-- PRD requirements
-- Epic prioritization
-
-## Best Practices
-
-1. **Prepare context** - Gather business and technical background
-2. **Think broadly** - Explore non-obvious approaches
-3. **Document assumptions** - Capture implicit beliefs
-4. **Consider constraints** - Technical, organizational, resource
-5. **Focus on value** - Align to business objectives
-
-## Configuration
-
-```yaml
-# bmad/bmm/config.yaml
-output_folder: ./output
-project_name: Your Project
-```
-
-## Related Workflows
-
-- [Research](../research/README.md) - Deep investigation
-- [Product Brief](../product-brief/README.md) - Strategic planning
-- [PRD](../../2-plan-workflows/prd/README.md) - Requirements document
-
----
-
-Part of BMad Method v6 - Phase 1 Analysis workflows

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

@@ -1,221 +0,0 @@
-# Game Brief Workflow
-
-## Overview
-
-The Game Brief workflow is the starting point for game projects in the BMad Method. It's a lightweight, interactive brainstorming and planning session that captures your game vision before diving into detailed Game Design Documents (GDD).
-
-## Purpose
-
-**Game Brief answers:**
-
-- What game are you making?
-- Who is it for?
-- What makes it unique?
-- Is it feasible?
-
-**This is NOT:**
-
-- A full Game Design Document
-- A technical specification
-- A production plan
-- A detailed content outline
-
-## When to Use This Workflow
-
-Use the game-brief workflow when:
-
-- Starting a new game project from scratch
-- Exploring a game idea before committing
-- Pitching a concept to team/stakeholders
-- Validating market fit and feasibility
-- Preparing input for the GDD workflow
-
-Skip if:
-
-- You already have a complete GDD
-- Continuing an existing project
-- Prototyping without planning needs
-
-## Workflow Structure
-
-### Interactive Mode (Recommended)
-
-Work through each section collaboratively:
-
-1. Game Vision (concept, pitch, vision statement)
-2. Target Market (audience, competition, positioning)
-3. Game Fundamentals (pillars, mechanics, experience goals)
-4. Scope and Constraints (platforms, timeline, budget, team)
-5. Reference Framework (inspiration, competitors, differentiators)
-6. Content Framework (world, narrative, volume)
-7. Art and Audio Direction (visual and audio style)
-8. Risk Assessment (risks, challenges, mitigation)
-9. Success Criteria (MVP, metrics, launch goals)
-10. Next Steps (immediate actions, research, questions)
-
-### YOLO Mode
-
-AI generates complete draft, then you refine sections iteratively.
-
-## Key Features
-
-### Optional Inputs
-
-The workflow can incorporate:
-
-- Market research
-- Brainstorming results
-- Competitive analysis
-- Design notes
-- Reference game lists
-
-### Realistic Scoping
-
-The workflow actively helps you:
-
-- Identify scope vs. resource mismatches
-- Assess technical feasibility
-- Recognize market risks
-- Plan mitigation strategies
-
-### Clear Handoff
-
-Output is designed to feed directly into:
-
-- GDD workflow (2-plan phase)
-- Prototyping decisions
-- Team discussions
-- Stakeholder presentations
-
-## Output
-
-**game-brief-{game_name}-{date}.md** containing:
-
-- Executive summary
-- Complete game vision
-- Target market analysis
-- Core gameplay definition
-- Scope and constraints
-- Reference framework
-- Art/audio direction
-- Risk assessment
-- Success criteria
-- Next steps
-
-## Integration with BMad Method
-
-```
-1-analysis/game-brief     (You are here)
-    ↓
-2-plan-workflows/gdd               (Game Design Document)
-    ↓
-2-plan-workflows/narrative         (Optional: Story-heavy games)
-    ↓
-3-solutioning            (Technical architecture, engine selection)
-    ↓
-4-dev-stories            (Implementation stories)
-```
-
-## Comparison: Game Brief vs. GDD
-
-| Aspect              | Game Brief                  | GDD                       |
-| ------------------- | --------------------------- | ------------------------- |
-| **Purpose**         | Validate concept            | Design for implementation |
-| **Detail Level**    | High-level vision           | Detailed specifications   |
-| **Time Investment** | 1-2 hours                   | 4-10 hours                |
-| **Audience**        | Self, team, stakeholders    | Development team          |
-| **Scope**           | Concept validation          | Implementation roadmap    |
-| **Format**          | Conversational, exploratory | Structured, comprehensive |
-| **Output**          | 3-5 pages                   | 10-30+ pages              |
-
-## Comparison: Game Brief vs. Product Brief
-
-| Aspect            | Game Brief                   | Product Brief                     |
-| ----------------- | ---------------------------- | --------------------------------- |
-| **Focus**         | Player experience, fun, feel | User problems, features, value    |
-| **Metrics**       | Engagement, retention, fun   | Revenue, conversion, satisfaction |
-| **Core Elements** | Gameplay pillars, mechanics  | Problem/solution, user segments   |
-| **References**    | Other games                  | Competitors, market               |
-| **Vision**        | Emotional experience         | Business outcomes                 |
-
-## Example Use Case
-
-### Scenario: Indie Roguelike Card Game
-
-**Starting Point:**
-"I want to make a roguelike card game with a twist"
-
-**After Game Brief:**
-
-- **Core Concept:** "A roguelike card battler where you play as emotions battling inner demons"
-- **Target Audience:** Core gamers who love Slay the Spire, interested in mental health themes
-- **Differentiator:** Emotional narrative system where deck composition affects story
-- **MVP Scope:** 3 characters, 80 cards, 30 enemy types, 3 bosses, 6-hour first run
-- **Platform:** PC (Steam) first, mobile later
-- **Timeline:** 12 months with 2-person team
-- **Key Risk:** Emotional theme might alienate hardcore roguelike fans
-- **Mitigation:** Prototype early, test with target audience, offer "mechanical-only" mode
-
-**Next Steps:**
-
-1. Build card combat prototype (2 weeks)
-2. Test emotional resonance with players
-3. Proceed to GDD workflow if prototype validates
-
-## Tips for Success
-
-### Be Honest About Scope
-
-The most common game dev failure is scope mismatch. Use this workflow to reality-check:
-
-- Can your team actually build this?
-- Is the timeline realistic?
-- Do you have budget for assets?
-
-### Focus on Player Experience
-
-Don't think about code or implementation. Think about:
-
-- What will players DO?
-- How will they FEEL?
-- Why will they CARE?
-
-### Validate Early
-
-The brief identifies assumptions and risks. Don't skip to GDD without:
-
-- Prototyping risky mechanics
-- Testing with target audience
-- Validating market interest
-
-### Use References Wisely
-
-"Like X but with Y" is a starting point, not a differentiator. Push beyond:
-
-- What specifically from reference games?
-- What are you explicitly NOT doing?
-- What's genuinely new?
-
-## FAQ
-
-**Q: Is this required before GDD?**
-A: No, but highly recommended for new projects. You can start directly with GDD if you have a clear vision.
-
-**Q: Can I use this for game jams?**
-A: Yes, but use YOLO mode for speed. Focus on vision, mechanics, and MVP scope.
-
-**Q: What if my game concept changes?**
-A: Revisit and update the brief. It's a living document during early development.
-
-**Q: How detailed should content volume estimates be?**
-A: Rough orders of magnitude are fine. "~50 enemies" not "47 enemies with 3 variants each."
-
-**Q: Should I complete this alone or with my team?**
-A: Involve your team! Collaborative briefs catch blind spots and build shared vision.
-
-## Related Workflows
-
-- **Product Brief** (`1-analysis/product-brief`): For software products, not games
-- **GDD** (`2-plan-workflows/gdd`): Next step after game brief
-- **Narrative Design** (`2-plan-workflows/narrative`): For story-heavy games after GDD
-- **Solutioning** (`3-solutioning`): Technical architecture after planning

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

@@ -1,180 +0,0 @@
-# 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 and 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 and Assumptions** - Resource limits and key assumptions
-12. **Risks and 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/create-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_