BMAD-METHOD/.bmad/bmb/workflows/create-module
Brian Madison 7eb52520fa Major Enhancements:
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
  - Default installation location changed to .bmad (hidden directory) for cleaner project root organization

    Web Bundle Improvements:

    - All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
    - Advanced elicitation capabilities integrated into standalone agents
    - All bundles enhanced with party mode agent manifests
    - Added default-party.csv files to bmm, bmgd, and cis module teams
    - The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
    - New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)

    Phase 4 Workflow Updates (In Progress):

    - Initiated shift to separate phase 4 implementation artifacts from documentation
        - Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
        - Installer questions and configuration added for artifact path selection
        - Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates

    Additional Changes:

    - New agent and action command header models for standardization
    - Enhanced web-bundle-activation-steps fragment
    - Updated web-bundler.js to support new structure
    - VS Code settings updated for new .bmad directory
    - Party mode instructions and workflow enhanced for better orchestration

   IDE Installer Updates:

    - Show version number of installer in cli
    - improved Installer UX
    - Gemini TOML Improved to have clear loading instructions with @ commands
    - All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
2025-11-09 17:39:05 -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 Major Enhancements: 2025-11-09 17:39:05 -06:00
instructions.md Major Enhancements: 2025-11-09 17:39:05 -06:00
module-structure.md Major Enhancements: 2025-11-09 17:39:05 -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