ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/.bmad/bmb
History
Brian Madison 48cf5c8056 feat(workflows): Implement intelligent file discovery protocol and Phase 4 BMGD workflows 
## Core Workflow Engine Enhancements

### discover_inputs Protocol (MAJOR)
- Added reusable `discover_inputs` protocol to workflow.xml for intelligent file loading
- Supports three loading strategies:
  - FULL_LOAD: Load all shards for PRD, Architecture, UX (changed pattern from /index.md to /*/*.md)
  - SELECTIVE_LOAD: Load specific shard via template variable (e.g., epic-{{epic_num}}.md)
  - INDEX_GUIDED: Load index, analyze TOC, intelligently load relevant docs (with "DO NOT BE LAZY" mandate)
- Auto-discovers whole vs sharded documents with proper fallback
- Provides transparent reporting of loaded content with file counts
- Invoked via <invoke-protocol name="discover_inputs" /> tag in workflow instructions

### Advanced Elicitation Improvements
- Renamed adv-elicit.xml to advanced-elicitation.xml for clarity
- Updated all references across agents and commands

### Shard Document Tool Enhancement
- Added Step 6: Handle Original Document with three options:
  - [d] Delete - Remove original (recommended, prevents confusion)
  - [m] Move to archive - Backup original to archive folder
  - [k] Keep - Warning about defeating sharding purpose
- Prevents issue where both whole and sharded versions exist, confusing discover_inputs protocol

## BMM Module - Input File Pattern Standardization

### Phase 1 - Analysis (1 workflow)
- product-brief: Added load_strategy (FULL_LOAD for research/brainstorming, INDEX_GUIDED for document_project)
- Updated instructions.md to use invoke-protocol, replaced manual fuzzy matching

### Phase 2 - Planning (4 workflows)
- prd: Added load_strategy, updated instructions to reference {product_brief_content}, {research_content}
- create-ux-design: Added load_strategy, removed fuzzy matching from instructions
- tech-spec: Added load_strategy for brownfield context discovery
- All epics patterns updated to support SELECTIVE_LOAD for specific epic shards

### Phase 3 - Solutioning (2 workflows)
- architecture: Added load_strategy, updated instructions to use pre-loaded {prd_content}, {epics_content}, {ux_design_content}
- solutioning-gate-check: Added load_strategy, replaced manual discovery with protocol invocation

### Phase 4 - Implementation (8 workflows)
- code-review: Added load_strategy, fixed sharded patterns to /*/*.md, added step 1.5 for protocol
- correct-course: Added complete input_file_patterns section (was missing), added step 0.5
- create-story: Added load_strategy, updated to SELECTIVE_LOAD for epics, added step 1.5
- dev-story: Added complete input_file_patterns section (was missing), added step 0.5
- epic-tech-context: Added load_strategy, updated PRD extraction to use {prd_content}, added step 1.5
- retrospective: Added load_strategy for architecture/prd (FULL_LOAD), epics (SELECTIVE_LOAD), added step 0.5
- sprint-planning: Fixed sharded pattern to load ALL epics (/*/*.md), added step 0.5
- story-context: Added load_strategy, updated doc collection to reference pre-loaded content, added step 1.5

### Sprint Artifacts Path Corrections
- story-done: Added missing sprint_artifacts variable, fixed sprint_status path from {context_dir} to {sprint_artifacts}
- story-ready: Added missing sprint_artifacts variable
- story-context: Fixed undefined {context_dir} -> {sprint_artifacts}
- correct-course: Added sprint_artifacts and sprint_status variables

## BMGD Module - Phase 4 Production Workflows (NEW)

Added complete Phase 4 implementation workflows for game development:
- code-review: Senior developer review for completed game features
- correct-course: Sprint change management for game projects
- create-story: Story generation for game mechanics/features
- dev-story: Feature implementation workflow
- epic-tech-context: Technical spec generation per game epic
- retrospective: Epic completion review and lessons learned
- sprint-planning: Game development sprint status tracking
- story-context: Dynamic context assembly for game stories
- story-done: Story completion workflow
- story-ready: Story readiness workflow

All BMGD workflows follow BMM patterns with game-specific adaptations.

## Agent Updates

### BMM Agents
- Updated all 7 BMM agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer)
- Standardized web bundle configurations

### BMGD Agents
- Updated 4 game development agents (game-architect, game-designer, game-dev, game-scrum-master)
- Aligned with BMM agent structure

### CIS Agents
- Updated 5 creative intelligence agents for consistency

## Documentation & Configuration

- Updated CHANGELOG.md with Phase 4 workflow additions
- Updated files-manifest.csv and task-manifest.csv
- Updated .claude commands for all agents
- Fixed formatting issues from previous commits

## Breaking Changes

NONE - All changes are backward compatible. Workflows without input_file_patterns continue to work.
Workflows with input_file_patterns now benefit from intelligent auto-loading.

## Migration Notes

Existing workflows can gradually adopt discover_inputs protocol by:
1. Adding load_strategy to existing input_file_patterns in workflow.yaml
2. Adding <invoke-protocol name="discover_inputs" /> step in instructions.md
3. Replacing manual file loading with references to {pattern_name_content} variables
 		2025-11-12 19:18:38 -06:00
..
agents Major Enhancements: 2025-11-09 17:39:05 -06:00
workflows feat(workflows): Implement intelligent file discovery protocol and Phase 4 BMGD workflows 2025-11-12 19:18:38 -06:00
README.md Major Enhancements: 2025-11-09 17:39:05 -06:00
config.yaml Major Enhancements: 2025-11-09 17:39:05 -06:00

README.md

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

Related Documentation

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