This comprehensive update transforms the Product Brief and PRD workflows from rigid template-filling exercises into adaptive, context-aware discovery processes. Changes span workflow instructions, templates, agent configurations, and supporting infrastructure. ## Product Brief Workflow (96% audit compliance) ### Intent-Driven Facilitation - Transform from linear Q&A to natural conversational discovery - Adaptive questioning based on project context (hobby/startup/enterprise) - Real-time document building instead of end-of-session generation - Skill-level aware facilitation (expert/intermediate/beginner) - Context detection from user responses to guide exploration depth ### Living Document Approach - Continuous template updates throughout conversation - Progressive refinement vs batch generation - Template-output tags aligned with discovery flow - Better variable mapping between instructions and template ### Enhanced Discovery Areas - Problem exploration with context-appropriate probing - Solution vision shaping based on user's mental model - User understanding through storytelling vs demographics - Success metrics tailored to project type - Ruthless MVP scope management with feature prioritization ### Template Improvements - Added context-aware conditional sections - Better organization of optional vs required content - Clearer structure for different project types - Improved reference material handling ## PRD Workflow (improved from 65% to 85%+ compliance) ### Critical Fixes - Add missing `date: system-generated` config variable - Fix status file extension mismatch (.yaml not .md) - Remove 38% bloat (unused technical_decisions variables) - Add explicit template-output tags for runtime variables ### Scale-Adaptive Intelligence - Project type detection (API/Web App/Mobile/SaaS/etc) - Domain complexity mapping (14 domain types) - Automatic requirement tailoring based on detected context - CSV-driven project type and domain knowledge base ### Separated Epic Planning - Move epic/story breakdown to dedicated child workflow - Create create-epics-and-stories workflow for Phase 2 - Cleaner separation: PRD defines WHAT, epics define HOW - Updated PM agent menu with new workflow triggers ### Enhanced Requirements Coverage - Project-type specific requirement sections (endpoints, auth, platform) - Domain-specific considerations (healthcare compliance, fintech security) - UX principles with interaction patterns - Non-functional requirements with integration needs - Technical preferences capture ### Template Restructuring - Separate PRD template from epic planning - Context-aware conditional sections - Better scale level indicators (L0-L4) - Improved reference document handling - Clearer success criteria sections ## Architecture Workflow Updates ### Template Enhancements - Add domain complexity context support - Better integration with PRD outputs - Improved technical decision capture - Enhanced system architecture sections ### Instruction Improvements - Reference new domain-research workflow - Better handling of PRD inputs - Clearer architectural decision framework ## Agent Configuration Updates ### BMad Master Agent - Fix workflow invocation instructions - Better fuzzy matching guidance - Clearer menu handler documentation - Remove workflow invention warnings ### PM Agent - Add create-prd trigger (renamed from 'prd') - Add create-epics-and-stories workflow trigger - Add validate-prd workflow trigger with checklist - Better workflow status integration ### Game Designer Agent - Rename triggers for consistency (create-game-brief, create-gdd) - Align with PM agent naming conventions ## New Supporting Infrastructure ### Domain Research Workflow - New discovery workflow for domain-specific research - Complements product brief for complex domains - Web research integration for domain insights ### Create Epics and Stories Workflow - Dedicated epic/story breakdown process - Separates planning (PRD) from decomposition - Better Epic → Story → Task hierarchy - Acceptance criteria generation ### Data Files - project-types.csv: 12 project type definitions with requirements - domain-complexity.csv: 14 domain types with complexity indicators ## Quality Improvements ### Validation & Compliance - Product Brief: 96% BMAD v6 compliance (EXCELLENT rating) - PRD: Improved from 65% to ~85% after critical fixes - Zero bloat in Product Brief (0%) - Reduced PRD bloat from 38% to ~15% ### Template Variable Mapping - All template variables explicitly populated via template-output tags - Runtime variables properly tracked - Config variables consistently used - Better separation of concerns ### Web Bundle Configuration - Complete web_bundle sections for all workflows - Proper child workflow references - Data file inclusions (CSV files) - Correct bmad/-relative paths ## Breaking Changes ### File Removals - Delete src/modules/bmm/workflows/2-plan-workflows/prd/epics-template.md (replaced by create-epics-and-stories child workflow) ### Workflow Trigger Changes - PM agent: 'prd' → 'create-prd' - PM agent: 'gdd' → 'create-gdd' - New: 'create-epics-and-stories' - New: 'validate-prd' ## Impact This update significantly improves the BMM module's ability to: - Adapt to different project types and scales - Guide users through discovery naturally vs mechanically - Generate higher quality planning documents - Support complex domains with specialized knowledge - Scale from Level 0 quick changes to Level 4 enterprise projects The workflows now feel like collaborative discovery sessions with an expert consultant rather than form-filling exercises. |
||
|---|---|---|
| .. | ||
| _module-installer | ||
| agents | ||
| sub-modules/claude-code | ||
| tasks | ||
| teams | ||
| testarch | ||
| workflows | ||
| README.md | ||
README.md
BMM - BMad Method Module
Core orchestration system for AI-driven agile development, providing comprehensive lifecycle management through specialized agents and workflows.
Table of Contents
- Essential Reading
- Module Structure
- Quick Start
- Key Concepts
- Scale Levels
- Story Lifecycle
- Best Practices
Essential Reading
📖 BMM v6 Workflows Guide - Required reading before using BMM. Explains the revolutionary workflow system and component integration.
Module Structure
🤖 Agents
Core Development Roles:
- PM - Product Manager for planning and requirements
- Analyst - Business analysis and research
- Architect - Technical architecture and design
- SM - Scrum Master for sprint and story management
- DEV - Developer for implementation
- TEA - Test Architect for quality assurance
- UX - User experience design
Game Development (Optional):
- Game Designer - Creative vision and GDD creation
- Game Developer - Game-specific implementation
- Game Architect - Game systems and infrastructure
📋 Workflows
Four-phase methodology adapting to project complexity:
1. Analysis (Optional)
brainstorm-project- Project ideationresearch- Market/technical researchproduct-brief- Product strategy
2. Planning (Required)
prd- Scale-adaptive planning- Routes to appropriate documentation level
3. Solutioning (Level 3-4)
architecture- System designtech-spec- Epic technical specifications
4. Implementation (Iterative)
create-story- Draft storiesstory-context- Inject expertisedev-story- Implementcode-review- Validate quality
👥 Teams
Pre-configured agent groups for coordinated complex tasks.
📝 Tasks
Atomic work units composing into larger workflows.
🏗️ Test Architecture
TEA Guide - Comprehensive testing strategy across 9 specialized workflows.
Quick Start
- Load PM agent in your IDE
- Wait for menu to appear
- Run workflow:
*prd
IDE Instructions:
Key Concepts
Scale Levels
BMM automatically adapts complexity:
| Level | Stories | Documentation |
|---|---|---|
| 0 | Single change | Minimal |
| 1 | 1-10 | Light PRD |
| 2 | 5-15 | Focused PRD |
| 3 | 12-40 | Full architecture |
| 4 | 40+ | Enterprise scale |
Story Lifecycle
Four-state machine tracked in status file:
BACKLOG → TODO → IN PROGRESS → DONE
- BACKLOG - Ordered stories to draft
- TODO - Ready for SM drafting
- IN PROGRESS - Approved for DEV
- DONE - Completed with metrics
Just-In-Time Design
Technical specifications created per epic during implementation, enabling learning and adaptation.
Context Injection
Dynamic technical guidance generated for each story, providing exact expertise when needed.
Best Practices
- Start with workflows - Let process guide you
- Respect scale - Don't over-document small projects
- Trust the process - Methodology carefully designed
- Use status file - Single source of truth for stories
Related Documentation
- Workflows Guide - Complete workflow reference
- Test Architect Guide - Testing strategy
- IDE Setup - Environment configuration
For complete BMad Method workflow system details, see the BMM Workflows README.