Files
BMAD-METHOD/src/modules/bmb
Brian Madison 2d99833b9e feat: Add documentation guides, simplify folder structure, and major workflow refactoring
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)
2025-11-11 17:30:43 -06:00
..
2025-11-09 17:39:05 -06:00
2025-11-09 17:39:05 -06:00
2025-10-30 11:26:15 -05:00

BMB - BMad Builder Module

Specialized tools and workflows for creating, customizing, and extending BMad components including agents, workflows, and complete modules.

Table of Contents

Module Structure

🤖 Agents

BMad Builder - Master builder agent orchestrating all creation workflows with deep knowledge of BMad architecture and conventions.

📋 Workflows

Comprehensive suite for building and maintaining BMad components.

Core Workflows

Creation Workflows

create-agent - Build BMad agents

  • Interactive persona development
  • Command structure design
  • YAML source compilation to .md

create-workflow - Design workflows

  • Structured multi-step processes
  • Configuration validation
  • Web bundle support

create-module - Build complete modules

  • Full module infrastructure
  • Agent and workflow integration
  • Installation automation

module-brief - Strategic planning

  • Module blueprint creation
  • Vision and architecture
  • Comprehensive analysis

Editing Workflows

edit-agent - Modify existing agents

  • Persona refinement
  • Command updates
  • Best practice compliance

edit-workflow - Update workflows

  • Structure maintenance
  • Configuration updates
  • Documentation sync

edit-module - Module enhancement

  • Component modifications
  • Dependency management
  • Version control

Maintenance Workflows

convert-legacy - Migration tool

  • v4 to v6 conversion
  • Structure compliance
  • Convention updates

audit-workflow - Quality validation

  • Structure verification
  • Config standards check
  • Bloat detection
  • Web bundle completeness

redoc - Auto-documentation

  • Reverse-tree approach
  • Technical writer quality
  • Convention compliance

Agent Types

BMB creates three agent architectures:

Full Module Agent

  • Complete persona and role definition
  • Command structure with fuzzy matching
  • Workflow integration
  • Module-specific capabilities

Hybrid Agent

  • Shared core capabilities
  • Module-specific extensions
  • Cross-module compatibility

Standalone Agent

  • Independent operation
  • Minimal dependencies
  • Specialized single purpose

Quick Start

  1. Load BMad Builder agent in your IDE
  2. Choose creation type:
    *create-agent     # New agent
    *create-workflow  # New workflow
    *create-module    # Complete module
    
  3. Follow interactive prompts

Example: Creating an Agent

User: I need a code review agent
Builder: *create-agent

[Interactive session begins]
- Brainstorming phase (optional)
- Persona development
- Command structure
- Integration points

Use Cases

Custom Development Teams

Build specialized agents for:

  • Domain expertise (legal, medical, finance)
  • Company processes
  • Tool integrations
  • Automation tasks

Workflow Extensions

Create workflows for:

  • Compliance requirements
  • Quality gates
  • Deployment pipelines
  • Custom methodologies

Complete Solutions

Package modules for:

  • Industry verticals
  • Technology stacks
  • Business processes
  • Educational frameworks

Best Practices

  1. Study existing patterns - Review BMM/CIS implementations
  2. Follow conventions - Use established structures
  3. Document thoroughly - Clear instructions essential
  4. Test iteratively - Validate during creation
  5. Consider reusability - Build modular components

Integration

BMB components integrate with:

  • BMad Core - Framework foundation
  • BMM - Extend development capabilities
  • CIS - Leverage creative workflows
  • Custom Modules - Your domain solutions

BMB empowers you to extend BMad Method for your specific needs while maintaining framework consistency and power.