BMAD-METHOD/.bmad/bmb/workflows/create-module
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
..
installer-templates Major Enhancements: 2025-11-09 17:39:05 -06:00
README.md Major Enhancements: 2025-11-09 17:39:05 -06:00
brainstorm-context.md Major Enhancements: 2025-11-09 17:39:05 -06:00
checklist.md removed some bad formatting that was injected previously 2025-11-11 17:30:43 -06:00
instructions.md feat(workflows): Implement intelligent file discovery protocol and Phase 4 BMGD workflows 2025-11-12 19:18:38 -06:00
module-structure.md remaining bad character removal 2025-11-11 20:10:33 -06:00
workflow.yaml Major Enhancements: 2025-11-09 17:39:05 -06:00

README.md

Create Module Workflow

Interactive scaffolding system creating complete BMad modules with agents, workflows, tasks, and installation infrastructure.

Table of Contents

Quick Start

# Basic invocation
workflow create-module

# With module brief input
workflow create-module --input module-brief-{name}-{date}.md

# Via BMad Builder
*create-module

Workflow Phases

Phase 1: Concept Definition

  • Define module purpose and audience
  • Establish module code (kebab-case) and name
  • Choose category (Domain, Creative, Technical, Business, Personal)
  • Plan component architecture

Module Brief Integration:

  • Auto-detects existing briefs
  • Uses as pre-populated blueprint
  • Accelerates planning phase

Phase 2: Architecture Planning

  • Create directory hierarchy
  • Setup configuration system
  • Define installer structure
  • Establish component folders

Phase 3: Component Creation

  • Optional first agent creation
  • Optional first workflow creation
  • Component placeholder generation
  • Integration validation

Phase 4: Installation Setup

  • Create install-config.yaml
  • Configure deployment questions
  • Setup installer logic
  • Post-install messaging

Phase 5: Documentation

  • Generate comprehensive README
  • Create development roadmap
  • Provide quick commands
  • Document next steps

Output Structure

Generated Directory

.bmad/{module-code}/
├── agents/              # Agent definitions
├── workflows/           # Workflow processes
├── tasks/              # Reusable tasks
├── templates/          # Document templates
├── data/               # Module data files
├── _module-installer/  # Installation logic
│   ├── install-config.yaml
│   └── installer.js
├── README.md           # Module documentation
├── TODO.md            # Development roadmap
└── config.yaml        # Runtime configuration

Configuration Files

install-config.yaml - Installation questions

questions:
  - id: user_name
    prompt: 'Your name?'
    default: 'User'
  - id: output_folder
    prompt: 'Output location?'
    default: './output'

config.yaml - Generated from user answers during install

user_name: 'John Doe'
output_folder: './my-output'

Module Components

Agents

  • Full module agents with workflows
  • Expert agents with sidecars
  • Simple utility agents

Workflows

  • Multi-step guided processes
  • Configuration-driven
  • Web bundle support

Tasks

  • Reusable operations
  • Agent-agnostic
  • Modular components

Templates

  • Document structures
  • Output formats
  • Report templates

Best Practices

Planning

  1. Use module-brief workflow first - Creates comprehensive blueprint
  2. Define clear scope - Avoid feature creep
  3. Plan component interactions - Map agent/workflow relationships

Structure

  1. Follow conventions - Use established patterns
  2. Keep components focused - Single responsibility
  3. Document thoroughly - Clear README and inline docs

Development

  1. Start with core agent - Build primary functionality first
  2. Create key workflows - Essential processes before edge cases
  3. Test incrementally - Validate as you build

Installation

  1. Minimal config questions - Only essential settings
  2. Smart defaults - Sensible out-of-box experience
  3. Clear post-install - Guide users to first steps

Integration Points

With Other Workflows

  • module-brief - Strategic planning input
  • create-agent - Agent component creation
  • create-workflow - Workflow building
  • redoc - Documentation maintenance

With BMad Core

  • Uses core framework capabilities
  • Integrates with module system
  • Follows BMad conventions

Examples

Domain-Specific Module

Category: Domain-Specific
Code: legal-advisor
Components:
- Contract Review Agent
- Compliance Workflow
- Legal Templates

Creative Module

Category: Creative
Code: story-builder
Components:
- Narrative Agent
- Plot Workflow
- Character Templates

Technical Module

Category: Technical
Code: api-tester
Components:
- Test Runner Agent
- API Validation Workflow
- Test Report Templates

Workflow Files

create-module/
├── workflow.yaml          # Configuration
├── instructions.md        # Step guide
├── checklist.md          # Validation
├── module-structure.md   # Architecture
├── installer-templates/  # Install files
└── README.md            # This file