Created two comprehensive guides for v6 features:
**docs/agent-customization-guide.md**
- Complete guide for customizing agent names, personas, memories, and behaviors
- Update-safe customization via bmad/_cfg/agents/ configuration files
- Real-world examples (TDD setup, multilingual agents, custom workflows)
- Troubleshooting and best practices
**docs/web-bundles-gemini-gpt-guide.md**
- Comprehensive guide for using BMad agents in Gemini Gems and Custom GPTs
- Critical setup rules with exact configuration text required
- Cost-saving strategy: web planning → local implementation (60-80% savings)
- Platform comparison (Gemini Gems strongly recommended over Custom GPTs)
- Complete workflow examples showing full planning-to-implementation cycle
- Team bundle guidance (Gemini 2.5 Pro+ only)
**README.md updates**
- Added prominent links in v6 Core Enhancements section
- Created new "Customization & Sharing" documentation category
- Web Bundles feature highlighted with direct guide link
**Unified output folder structure across all modules:**
**Before (confusing):**
- output_folder: Main docs
- game_design_docs: Separate design folder
- tech_docs: Separate technical folder
- dev_ephemeral_location: Separate ephemeral folder outside docs
**After (simplified):**
- output_folder: Single location for ALL AI-generated artifacts (default: "docs")
- Clearer prompt: "Where should AI Generated Artifacts be saved?"
- sprint_artifacts: Phase 4 ephemeral content now WITHIN output_folder
- BMM: {output_folder}/stories (stories, context, reports)
- BMGD: {output_folder}/sprint-artifacts
- No longer in separate {bmad_folder}-ephemeral location
**Benefits:**
- One clear location for all planning artifacts (PRD, Architecture, UX, etc.)
- Phase 4 ephemeral items logically grouped within output folder
- Eliminated confusing separate folder proliferation
- sprint_artifacts now configurable per module
**Files changed:**
- src/core/_module-installer/install-config.yaml
- src/modules/bmm/_module-installer/install-config.yaml
- src/modules/bmgd/_module-installer/install-config.yaml
**Also cleaned up BMGD config:**
- Renamed: specified_framework → primary_platform (clearer naming)
- Removed: unused data_path variable
Replaced old "project_level" (0-4) system with new "selected_track" terminology:
- **quick-flow**: Bug fixes and small features (replaces Level 0-1)
- **bmad-method**: Full planning track (replaces Level 2-3)
- **enterprise-bmad-method**: Extended planning (replaces Level 4)
**Core workflow updates:**
- solutioning-gate-check: Complete rewrite of validation logic for track-based artifacts
- architecture: Updated context detection, error handling, and messaging for tracks
- workflow-init: Updated artifact detection patterns for track-based paths
- All workflow status paths updated (method-greenfield, method-brownfield, enterprise-*)
Unified variable naming conventions across all workflows:
- {output_folder} → {output-folder} (hyphenated format)
- {dev_ephemeral_location} → {sprint_artifacts} (clearer purpose)
- Hardcoded status file paths → {workflow_status_file} variable
Fixed corrupted variable patterns throughout workflow files:
- {output*folder} → {output-folder}
- {ephemeral*location} → {sprint_artifacts}
- \_prd* → *prd* (escaped underscore artifacts)
- **\*\***\_\_\_**\*\*** → proper field placeholders
Affected patterns included malformed glob patterns, template variables, and markdown formatting artifacts from previous edits.
**Architecture workflow (create-architecture):**
- Fixed: "Decision Architecture" → "Create Architecture" (consistent naming)
- Improved PRD not found handling with exit/continue options
- Better user guidance when running standalone vs. within workflow path
- Removed hardcoded Level checks, now track-aware
- Enhanced validation checklist formatting (□ → - [])
- Typo fixes: "mulitple" → "multiple"
**Solutioning gate check:**
- Complete validation logic rewrite for track-based system
- Removed Level-specific artifact expectations
- Simplified document discovery (track determines what exists)
- Better analysis prompts and user feedback
**Workflow-init:**
- Updated artifact detection patterns for new folder structure
- Fixed corrupt glob patterns throughout
- Better sprint_artifacts location detection
- Improved workflow path assignment logic
**Various workflows:**
- Consistent variable naming across 40+ workflow files
- Improved error messages and user guidance
- Better markdown formatting (checkboxes, lists)
- Removed redundant validation criteria files (now inline)
Removed duplicate BMGD 4-production workflows (12 workflows):
- code-review, correct-course, create-story, dev-story
- epic-tech-context, retrospective, sprint-planning
- story-context, story-done, story-ready
**Why:** BMGD now uses shared BMM Phase 4 implementation workflows
**Benefit:** Single source of truth, no duplication to maintain
Also removed:
- validation-criteria.yaml (validation now inline in instructions)
- architecture-patterns.yaml references (patterns now managed differently)
- AUDIT-REPORT.md files (stale audit artifacts)
**BMB workflows:**
- Updated checklists for workflow and module creation
- Improved agent architecture documentation
- Minor instruction clarifications
**Core brainstorming workflow:**
- Updated README with usage examples
- Enhanced instructions and template clarity
- Better integration with other modules
**BMM installer:**
- Updated for track-based system
- sprint_artifacts configuration
**Tech Writer agent:**
- Minor configuration update for documentation workflows
Removed 200+ files that should not be in repository:
- Installed agent markdown files (analyst, architect, dev, pm, sm, tea, etc.)
- Complete workflow instruction copies
- Documentation duplicates (quick-start, agents-guide, workflows-*)
- Test architecture knowledge base (22 files, 14,000+ lines)
- Configuration files (config.yaml, team definitions)
These are generated during installation and should not be version controlled.
Removed 21 pre-generated XML bundles:
- BMM agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer)
- BMGD agents (game-architect, game-designer, game-dev, game-scrum-master)
- CIS agents (brainstorming-coach, creative-problem-solver, etc.)
- Team bundles (team-fullstack, team-gamedev, creative-squad)
**Why:** Users should generate fresh bundles via `npm run bundle` to get latest changes and customizations.
- **2 new documentation files** (comprehensive guides)
- **98 source files modified** (299 insertions, 6,567 deletions)
- **3 installer config files simplified** (major folder structure improvement)
- **200+ .bmad/ artifacts removed** (should not be in repo)
- **21 web-bundle files removed** (users regenerate as needed)
- **12 duplicate workflows removed** (BMGD consolidation)
- **40+ workflows updated** (track system, variable standardization, corruption fixes)
|
||
|---|---|---|
| .. | ||
| README.md | ||
| checklist.md | ||
| instructions.md | ||
| template.md | ||
| workflow.yaml | ||
README.md
Module Brief Workflow
Overview
The Module Brief workflow creates comprehensive blueprints for building new BMAD modules using strategic analysis and creative vision. It serves as the essential planning phase that transforms initial ideas into detailed, actionable specifications ready for implementation with the create-module workflow.
Key Features
- Strategic Module Planning - Comprehensive analysis from concept to implementation roadmap
- Multi-Mode Operation - Interactive, Express, and YOLO modes for different planning needs
- Creative Vision Development - Guided process for innovative module concepts and unique value propositions
- Architecture Design - Detailed agent and workflow ecosystem planning with interaction models
- User Journey Mapping - Scenario-based validation ensuring practical usability
- Technical Planning - Infrastructure requirements, dependencies, and complexity assessment
- Risk Assessment - Proactive identification of challenges with mitigation strategies
- Implementation Roadmap - Phased development plan with clear deliverables and timelines
Usage
Basic Invocation
workflow module-brief
With Brainstorming Input
# If you have brainstorming results from previous sessions
workflow module-brief --input brainstorming-session-2024-09-26.md
Express Mode
# For quick essential planning only
workflow module-brief --mode express
Configuration
The workflow uses standard BMB configuration:
- output_folder: Where the module brief will be saved
- user_name: Brief author information
- communication_language: Language for brief generation
- date: Automatic timestamp for versioning
Workflow Structure
Files Included
module-brief/
├── workflow.yaml # Configuration and metadata
├── instructions.md # Step-by-step execution guide
├── template.md # Module brief document structure
├── checklist.md # Validation criteria
└── README.md # This file
Workflow Process
Phase 1: Foundation and Context (Steps 1-3)
Mode Selection and Input Gathering
- Choose operational mode (Interactive, Express, YOLO)
- Check for and optionally load existing brainstorming results
- Gather background context and inspiration sources
Module Vision Development
- Define core problem the module solves
- Identify target user audience and use cases
- Establish unique value proposition and differentiators
- Explore creative themes and personality concepts
Module Identity Establishment
- Generate module code (kebab-case) with multiple options
- Create compelling, memorable module name
- Select appropriate category (Domain-Specific, Creative, Technical, Business, Personal)
- Define optional personality theme for consistent agent character
Phase 2: Architecture Planning (Steps 4-5)
Agent Architecture Design
- Plan agent team composition and roles
- Define agent archetypes (Orchestrator, Specialist, Helper, Creator, Analyzer)
- Specify personality traits and communication styles
- Map key capabilities and signature commands
Workflow Ecosystem Design
- Categorize workflows by purpose and complexity:
- Core Workflows: Essential value-delivery functions (2-3)
- Feature Workflows: Specialized capabilities (3-5)
- Utility Workflows: Supporting operations (1-3)
- Define input-process-output flows for each workflow
- Assess complexity levels and implementation priorities
Phase 3: Validation and User Experience (Steps 6-7)
User Journey Mapping
- Create detailed user scenarios and stories
- Map step-by-step usage flows through the module
- Validate end-to-end functionality and value delivery
- Identify potential friction points and optimization opportunities
Technical Planning and Requirements
- Assess data requirements and storage needs
- Map integration points with other modules and external systems
- Evaluate technical complexity and resource requirements
- Document dependencies and infrastructure needs
Phase 4: Success Planning (Steps 8-9)
Success Metrics Definition
- Establish module success criteria and performance indicators
- Define quality standards and reliability requirements
- Create user experience goals and feedback mechanisms
- Set measurable outcomes for module effectiveness
Development Roadmap Creation
- Design phased approach with MVP, Enhancement, and Polish phases
- Define deliverables and timelines for each phase
- Prioritize features and capabilities by value and complexity
- Create clear milestones and success checkpoints
Phase 5: Enhancement and Risk Management (Steps 10-12)
Creative Features and Special Touches (Optional)
- Design easter eggs and delightful user interactions
- Plan module lore and thematic consistency
- Add personality quirks and creative responses
- Develop backstories and universe building
Risk Assessment and Mitigation
- Identify technical, usability, and scope risks
- Develop mitigation strategies for each risk category
- Plan contingency approaches for potential challenges
- Document decision points and alternative paths
Final Review and Export Preparation
- Comprehensive review of all brief sections
- Validation against quality and completeness criteria
- Preparation for seamless handoff to create-module workflow
- Export readiness confirmation with actionable specifications
Output
Generated Files
- Module Brief Document: Comprehensive planning document at
{output_folder}/module-brief-{module_code}-{date}.md - Strategic Specifications: Ready-to-implement blueprint for create-module workflow
Output Structure
The module brief contains detailed specifications across multiple sections:
- Executive Summary - Vision, category, complexity, target users
- Module Identity - Core concept, value proposition, personality theme
- Agent Architecture - Agent roster, roles, interaction models
- Workflow Ecosystem - Core, feature, and utility workflow specifications
- User Scenarios - Primary use cases, secondary scenarios, user journey
- Technical Planning - Data requirements, integrations, dependencies
- Success Metrics - Success criteria, quality standards, performance targets
- Development Roadmap - Phased implementation plan with deliverables
- Creative Features - Special touches, easter eggs, module lore
- Risk Assessment - Technical, usability, scope risks with mitigation
- Implementation Notes - Priority order, design decisions, open questions
- Resources and References - Inspiration sources, similar modules, technical references
Requirements
- Creative Vision - Initial module concept or problem domain
- Strategic Thinking - Ability to plan architecture and user experience
- Brainstorming Results (optional) - Previous ideation sessions enhance planning quality
Best Practices
Before Starting
- Gather Inspiration - Research similar tools, modules, and solutions in your domain
- Run Brainstorming Session - Use ideation techniques to generate initial concepts
- Define Success Criteria - Know what "successful module" means for your context
During Execution
- Think User-First - Always consider the end user experience and value delivery
- Be Specific - Provide concrete examples and detailed specifications rather than abstractions
- Validate Early - Use user scenarios to test if the module concept actually works
- Plan Iteratively - Start with MVP and build complexity through phases
After Completion
- Use as Blueprint - Feed the brief directly into create-module workflow for implementation
- Review with Stakeholders - Validate assumptions and gather feedback before building
- Update as Needed - Treat as living document that evolves with implementation learnings
- Reference During Development - Use as north star for design decisions and scope management
Troubleshooting
Common Issues
Issue: Stuck on module concept or vision
- Solution: Use creative prompts provided in the workflow
- Check: Review existing modules for inspiration and patterns
Issue: Agent or workflow architecture too complex
- Solution: Focus on MVP first, plan enhancement phases for additional complexity
- Check: Validate each component against user scenarios
Issue: Technical requirements unclear
- Solution: Research similar modules and their implementation approaches
- Check: Consult with technical stakeholders early in planning
Issue: Scope creep during planning
- Solution: Use phased roadmap to defer non-essential features
- Check: Regularly validate against core user scenarios and success criteria
Customization
To customize this workflow:
- Modify Template Structure - Update template.md to add new sections or reorganize content
- Extend Creative Prompts - Add domain-specific ideation techniques in instructions.md
- Add Planning Tools - Integrate additional analysis frameworks or planning methodologies
- Customize Validation - Enhance checklist.md with specific quality criteria for your context
Version History
- v1.0.0 - Initial release
- Comprehensive strategic module planning
- Multi-mode operation (Interactive, Express, YOLO)
- Creative vision and architecture design tools
- User journey mapping and validation
- Risk assessment and mitigation planning
Support
For issues or questions:
- Review the workflow creation guide at
/{bmad_folder}/bmb/workflows/create-workflow/workflow-creation-guide.md - Study existing module examples in
/{bmad_folder}/for patterns and inspiration - Validate output using
checklist.md - Consult module structure guide at
create-module/module-structure.md
Part of the BMad Method v6 - BMB (Builder) Module