docs updated
This commit is contained in:
Brian Madison
218
bmad/bmb/workflows/create-module/README.md
Normal file
218
bmad/bmb/workflows/create-module/README.md
Normal file
@@ -0,0 +1,218 @@
|
||||
# Build Module Workflow
|
||||
|
||||
## Overview
|
||||
|
||||
The Build Module workflow is an interactive scaffolding system that creates complete BMAD modules with agents, workflows, tasks, and installation infrastructure. It serves as the primary tool for building new modules in the BMAD ecosystem, guiding users through the entire module creation process from concept to deployment-ready structure.
|
||||
|
||||
## Key Features
|
||||
|
||||
- **Interactive Module Planning** - Collaborative session to define module concept, scope, and architecture
|
||||
- **Intelligent Scaffolding** - Automatic creation of proper directory structures and configuration files
|
||||
- **Component Integration** - Seamless integration with create-agent and create-workflow workflows
|
||||
- **Installation Infrastructure** - Complete installer setup with configuration templates
|
||||
- **Module Brief Integration** - Can use existing module briefs as blueprints for accelerated development
|
||||
- **Validation and Documentation** - Built-in validation checks and comprehensive README generation
|
||||
|
||||
## Usage
|
||||
|
||||
### Basic Invocation
|
||||
|
||||
```bash
|
||||
workflow create-module
|
||||
```
|
||||
|
||||
### With Module Brief Input
|
||||
|
||||
```bash
|
||||
# If you have a module brief from the module-brief workflow
|
||||
workflow create-module --input module-brief-my-module-2024-09-26.md
|
||||
```
|
||||
|
||||
### Configuration
|
||||
|
||||
The workflow loads critical variables from the BMB configuration:
|
||||
|
||||
- **output_folder**: Where the module will be created
|
||||
- **user_name**: Module author information
|
||||
- **date**: Automatic timestamp for versioning
|
||||
|
||||
## Workflow Structure
|
||||
|
||||
### Files Included
|
||||
|
||||
```
|
||||
create-module/
|
||||
├── workflow.yaml # Configuration and metadata
|
||||
├── instructions.md # Step-by-step execution guide
|
||||
├── checklist.md # Validation criteria
|
||||
├── module-structure.md # Module architecture guide
|
||||
├── installer-templates/ # Installation templates
|
||||
│ ├── install-config.yaml
|
||||
│ └── installer.js
|
||||
└── README.md # This file
|
||||
```
|
||||
|
||||
## Workflow Process
|
||||
|
||||
### Phase 1: Concept Definition (Steps 1-2)
|
||||
|
||||
**Module Vision and Identity**
|
||||
|
||||
- Define module concept, purpose, and target audience
|
||||
- Establish module code (kebab-case) and friendly name
|
||||
- Choose module category (Domain-Specific, Creative, Technical, Business, Personal)
|
||||
- Plan component architecture with agent and workflow specifications
|
||||
|
||||
**Module Brief Integration**
|
||||
|
||||
- Automatically detects existing module briefs in output folder
|
||||
- Can load and use briefs as pre-populated blueprints
|
||||
- Accelerates planning when comprehensive brief exists
|
||||
|
||||
### Phase 2: Architecture Planning (Steps 3-4)
|
||||
|
||||
**Directory Structure Creation**
|
||||
|
||||
- Creates complete module directory hierarchy
|
||||
- Sets up agent, workflow, task, template, and data folders
|
||||
- Establishes installer directory with proper configuration
|
||||
|
||||
**Module Configuration**
|
||||
|
||||
- Generates main config.yaml with module metadata
|
||||
- Configures component counts and references
|
||||
- Sets up output and data folder specifications
|
||||
|
||||
### Phase 3: Component Creation (Steps 5-6)
|
||||
|
||||
**Interactive Component Building**
|
||||
|
||||
- Optional creation of first agent using create-agent workflow
|
||||
- Optional creation of first workflow using create-workflow workflow
|
||||
- Creates placeholders for components to be built later
|
||||
|
||||
**Workflow Integration**
|
||||
|
||||
- Seamlessly invokes sub-workflows for component creation
|
||||
- Ensures proper file placement and structure
|
||||
- Maintains module consistency across components
|
||||
|
||||
### Phase 4: Installation and Documentation (Steps 7-9)
|
||||
|
||||
**Installer Infrastructure**
|
||||
|
||||
- Creates install-module-config.yaml for deployment
|
||||
- Sets up optional installer.js for complex installation logic
|
||||
- Configures post-install messaging and instructions
|
||||
|
||||
**Comprehensive Documentation**
|
||||
|
||||
- Generates detailed README.md with usage examples
|
||||
- Creates development roadmap for remaining components
|
||||
- Provides quick commands for continued development
|
||||
|
||||
### Phase 5: Validation and Finalization (Step 10)
|
||||
|
||||
**Quality Assurance**
|
||||
|
||||
- Validates directory structure and configuration files
|
||||
- Checks component references and path consistency
|
||||
- Ensures installer configuration is deployment-ready
|
||||
- Provides comprehensive module summary and next steps
|
||||
|
||||
## Output
|
||||
|
||||
### Generated Files
|
||||
|
||||
- **Module Directory**: Complete module structure at `{project-root}/bmad/{module_code}/`
|
||||
- **Configuration Files**: config.yaml, install-module-config.yaml
|
||||
- **Documentation**: README.md, TODO.md development roadmap
|
||||
- **Component Placeholders**: Structured folders for agents, workflows, and tasks
|
||||
|
||||
### Output Structure
|
||||
|
||||
The workflow creates a complete module ready for development:
|
||||
|
||||
1. **Module Identity** - Name, code, version, and metadata
|
||||
2. **Directory Structure** - Proper BMAD module hierarchy
|
||||
3. **Configuration System** - Runtime and installation configs
|
||||
4. **Component Framework** - Ready-to-use agent and workflow scaffolding
|
||||
5. **Installation Infrastructure** - Deployment-ready installer
|
||||
6. **Documentation Suite** - README, roadmap, and development guides
|
||||
|
||||
## Requirements
|
||||
|
||||
- **Module Brief** (optional but recommended) - Use module-brief workflow first for best results
|
||||
- **BMAD Core Configuration** - Properly configured BMB config.yaml
|
||||
- **Build Tools Access** - create-agent and create-workflow workflows must be available
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Before Starting
|
||||
|
||||
1. **Create a Module Brief** - Run module-brief workflow for comprehensive planning
|
||||
2. **Review Existing Modules** - Study similar modules in `/bmad/` for patterns and inspiration
|
||||
3. **Define Clear Scope** - Have a concrete vision of what the module will accomplish
|
||||
|
||||
### During Execution
|
||||
|
||||
1. **Use Module Briefs** - Load existing briefs when prompted for accelerated development
|
||||
2. **Start Simple** - Create one core agent and workflow, then expand iteratively
|
||||
3. **Leverage Sub-workflows** - Use create-agent and create-workflow for quality components
|
||||
4. **Validate Early** - Review generated structure before proceeding to next phases
|
||||
|
||||
### After Completion
|
||||
|
||||
1. **Follow the Roadmap** - Use generated TODO.md for systematic development
|
||||
2. **Test Installation** - Validate installer with `bmad install {module_code}`
|
||||
3. **Iterate Components** - Use quick commands to add agents and workflows
|
||||
4. **Document Progress** - Update README.md as the module evolves
|
||||
|
||||
## Troubleshooting
|
||||
|
||||
### Common Issues
|
||||
|
||||
**Issue**: Module already exists at target location
|
||||
|
||||
- **Solution**: Choose a different module code or remove existing module
|
||||
- **Check**: Verify output folder permissions and available space
|
||||
|
||||
**Issue**: Sub-workflow invocation fails
|
||||
|
||||
- **Solution**: Ensure create-agent and create-workflow workflows are available
|
||||
- **Check**: Validate workflow paths in config.yaml
|
||||
|
||||
**Issue**: Installation configuration invalid
|
||||
|
||||
- **Solution**: Review install-module-config.yaml syntax and paths
|
||||
- **Check**: Ensure all referenced paths use {project-root} variables correctly
|
||||
|
||||
## Customization
|
||||
|
||||
To customize this workflow:
|
||||
|
||||
1. **Modify Instructions** - Update instructions.md to adjust scaffolding steps
|
||||
2. **Extend Templates** - Add new installer templates in installer-templates/
|
||||
3. **Update Validation** - Enhance checklist.md with additional quality checks
|
||||
4. **Add Components** - Integrate additional sub-workflows for specialized components
|
||||
|
||||
## Version History
|
||||
|
||||
- **v1.0.0** - Initial release
|
||||
- Interactive module scaffolding
|
||||
- Component integration with create-agent and create-workflow
|
||||
- Complete installation infrastructure
|
||||
- Module brief integration support
|
||||
|
||||
## Support
|
||||
|
||||
For issues or questions:
|
||||
|
||||
- Review the workflow creation guide at `/bmad/bmb/workflows/create-workflow/workflow-creation-guide.md`
|
||||
- Study module structure patterns at `module-structure.md`
|
||||
- Validate output using `checklist.md`
|
||||
- Consult existing modules in `/bmad/` for examples
|
||||
|
||||
---
|
||||
|
||||
_Part of the BMad Method v5 - BMB (Builder) Module_
|
||||
137
bmad/bmb/workflows/create-module/brainstorm-context.md
Normal file
137
bmad/bmb/workflows/create-module/brainstorm-context.md
Normal file
@@ -0,0 +1,137 @@
|
||||
# Module Brainstorming Context
|
||||
|
||||
_Context provided to brainstorming workflow when creating a new BMAD module_
|
||||
|
||||
## Session Focus
|
||||
|
||||
You are brainstorming ideas for a **complete BMAD module** - a self-contained package that extends the BMAD Method with specialized domain expertise and capabilities.
|
||||
|
||||
## What is a BMAD Module?
|
||||
|
||||
A module is a cohesive package that provides:
|
||||
|
||||
- **Domain Expertise**: Specialized knowledge in a specific area (RPG, DevOps, Content Creation, etc.)
|
||||
- **Agent Team**: Multiple AI personas with complementary skills
|
||||
- **Workflows**: Guided processes for common tasks in the domain
|
||||
- **Templates**: Document structures for consistent outputs
|
||||
- **Integration**: Components that work together seamlessly
|
||||
|
||||
## Brainstorming Goals
|
||||
|
||||
Explore and define:
|
||||
|
||||
### 1. Domain and Purpose
|
||||
|
||||
- **What domain/problem space?** (e.g., game development, marketing, personal productivity)
|
||||
- **Who is the target user?** (developers, writers, managers, hobbyists)
|
||||
- **What pain points does it solve?** (tedious tasks, missing structure, need for expertise)
|
||||
- **What makes this domain exciting?** (creativity, efficiency, empowerment)
|
||||
|
||||
### 2. Agent Team Composition
|
||||
|
||||
- **How many agents?** (typically 3-7 for a module)
|
||||
- **What roles/personas?** (architect, researcher, reviewer, specialist)
|
||||
- **How do they collaborate?** (handoffs, reviews, ensemble work)
|
||||
- **What personality theme?** (Star Trek crew, superhero team, fantasy party, professional squad)
|
||||
|
||||
### 3. Core Workflows
|
||||
|
||||
- **What documents need creating?** (plans, specs, reports, creative outputs)
|
||||
- **What processes need automation?** (analysis, generation, review, deployment)
|
||||
- **What workflows enable the vision?** (3-10 key workflows that define the module)
|
||||
|
||||
### 4. Value Proposition
|
||||
|
||||
- **What becomes easier?** (specific tasks that get 10x faster)
|
||||
- **What becomes possible?** (new capabilities previously unavailable)
|
||||
- **What becomes better?** (quality improvements, consistency gains)
|
||||
|
||||
## Creative Constraints
|
||||
|
||||
A good BMAD module should be:
|
||||
|
||||
- **Focused**: Serves a specific domain well (not generic)
|
||||
- **Complete**: Provides end-to-end capabilities for that domain
|
||||
- **Cohesive**: Agents and workflows complement each other
|
||||
- **Fun**: Personality and creativity make it enjoyable to use
|
||||
- **Practical**: Solves real problems, delivers real value
|
||||
|
||||
## Module Architecture Questions
|
||||
|
||||
1. **Module Identity**
|
||||
- Module code (kebab-case, e.g., "rpg-toolkit")
|
||||
- Module name (friendly, e.g., "RPG Toolkit")
|
||||
- Module purpose (one sentence)
|
||||
- Target audience
|
||||
|
||||
2. **Agent Lineup**
|
||||
- Agent names and roles
|
||||
- Communication styles and personalities
|
||||
- Expertise areas
|
||||
- Command sets (what each agent can do)
|
||||
|
||||
3. **Workflow Portfolio**
|
||||
- Document generation workflows
|
||||
- Action/automation workflows
|
||||
- Analysis/research workflows
|
||||
- Creative/ideation workflows
|
||||
|
||||
4. **Integration Points**
|
||||
- How agents invoke workflows
|
||||
- How workflows use templates
|
||||
- How components pass data
|
||||
- Dependencies on other modules
|
||||
|
||||
## Example Module Patterns
|
||||
|
||||
### Professional Domains
|
||||
|
||||
- **DevOps Suite**: Deploy, Monitor, Troubleshoot agents + deployment workflows
|
||||
- **Marketing Engine**: Content, SEO, Analytics agents + campaign workflows
|
||||
- **Legal Assistant**: Contract, Research, Review agents + document workflows
|
||||
|
||||
### Creative Domains
|
||||
|
||||
- **RPG Toolkit**: DM, NPC, Quest agents + adventure creation workflows
|
||||
- **Story Crafter**: Plot, Character, World agents + writing workflows
|
||||
- **Music Producer**: Composer, Arranger, Mixer agents + production workflows
|
||||
|
||||
### Personal Domains
|
||||
|
||||
- **Life Coach**: Planner, Tracker, Mentor agents + productivity workflows
|
||||
- **Learning Companion**: Tutor, Quiz, Reviewer agents + study workflows
|
||||
- **Health Guide**: Nutrition, Fitness, Wellness agents + tracking workflows
|
||||
|
||||
## Suggested Brainstorming Techniques
|
||||
|
||||
Particularly effective for module ideation:
|
||||
|
||||
1. **Domain Immersion**: Deep dive into target domain's problems
|
||||
2. **Persona Mapping**: Who needs this and what do they struggle with?
|
||||
3. **Workflow Mapping**: What processes exist today? How could they improve?
|
||||
4. **Team Building**: What personalities would make a great team?
|
||||
5. **Integration Thinking**: How do pieces connect and amplify each other?
|
||||
|
||||
## Key Questions to Answer
|
||||
|
||||
1. What domain expertise should this module embody?
|
||||
2. What would users be able to do that they can't do now?
|
||||
3. Who are the 3-7 agents and what are their personalities?
|
||||
4. What are the 5-10 core workflows?
|
||||
5. What makes this module delightful to use?
|
||||
6. How is this different from existing tools?
|
||||
7. What's the "killer feature" that makes this essential?
|
||||
|
||||
## Output Goals
|
||||
|
||||
Generate:
|
||||
|
||||
- **Module concept**: Clear vision and purpose
|
||||
- **Agent roster**: Names, roles, personalities for each agent
|
||||
- **Workflow list**: Core workflows with brief descriptions
|
||||
- **Unique angle**: What makes this module special
|
||||
- **Use cases**: 3-5 concrete scenarios where this module shines
|
||||
|
||||
---
|
||||
|
||||
_This focused context helps create cohesive, valuable BMAD modules_
|
||||
245
bmad/bmb/workflows/create-module/checklist.md
Normal file
245
bmad/bmb/workflows/create-module/checklist.md
Normal file
@@ -0,0 +1,245 @@
|
||||
# Build Module Validation Checklist
|
||||
|
||||
## Module Identity and Metadata
|
||||
|
||||
### Basic Information
|
||||
|
||||
- [ ] Module code follows kebab-case convention (e.g., "rpg-toolkit")
|
||||
- [ ] Module name is descriptive and title-cased
|
||||
- [ ] Module purpose is clearly defined (1-2 sentences)
|
||||
- [ ] Target audience is identified
|
||||
- [ ] Version number follows semantic versioning (e.g., "1.0.0")
|
||||
- [ ] Author information is present
|
||||
|
||||
### Naming Consistency
|
||||
|
||||
- [ ] Module code used consistently throughout all files
|
||||
- [ ] No naming conflicts with existing modules
|
||||
- [ ] All paths use consistent module code references
|
||||
|
||||
## Directory Structure
|
||||
|
||||
### Source Directories (bmad/{module-code}/)
|
||||
|
||||
- [ ] `/agents` directory created (even if empty)
|
||||
- [ ] `/workflows` directory created (even if empty)
|
||||
- [ ] `/tasks` directory exists (if tasks planned)
|
||||
- [ ] `/templates` directory exists (if templates used)
|
||||
- [ ] `/data` directory exists (if data files needed)
|
||||
- [ ] `config.yaml` present in module root
|
||||
- [ ] `README.md` present with documentation
|
||||
|
||||
### Runtime Directories (bmad/{module-code}/)
|
||||
|
||||
- [ ] `/_module-installer` directory created
|
||||
- [ ] `/data` directory for user data
|
||||
- [ ] `/agents` directory for overrides
|
||||
- [ ] `/workflows` directory for instances
|
||||
- [ ] Runtime `config.yaml` present
|
||||
|
||||
## Component Planning
|
||||
|
||||
### Agents
|
||||
|
||||
- [ ] At least one agent defined or planned
|
||||
- [ ] Agent purposes are distinct and clear
|
||||
- [ ] Agent types (Simple/Expert/Module) identified
|
||||
- [ ] No significant overlap between agents
|
||||
- [ ] Primary agent is identified
|
||||
|
||||
### Workflows
|
||||
|
||||
- [ ] At least one workflow defined or planned
|
||||
- [ ] Workflow purposes are clear
|
||||
- [ ] Workflow types identified (Document/Action/Interactive)
|
||||
- [ ] Primary workflow is identified
|
||||
- [ ] Workflow complexity is appropriate
|
||||
|
||||
### Tasks (if applicable)
|
||||
|
||||
- [ ] Tasks have single, clear purposes
|
||||
- [ ] Tasks don't duplicate workflow functionality
|
||||
- [ ] Task files follow naming conventions
|
||||
|
||||
## Configuration Files
|
||||
|
||||
### Module config.yaml
|
||||
|
||||
- [ ] All required fields present (name, code, version, author)
|
||||
- [ ] Component lists accurate (agents, workflows, tasks)
|
||||
- [ ] Paths use proper variables ({project-root}, etc.)
|
||||
- [ ] Output folders configured
|
||||
- [ ] Custom settings documented
|
||||
|
||||
### Install Configuration
|
||||
|
||||
- [ ] `install-module-config.yaml` exists in `_module-installer`
|
||||
- [ ] Installation steps defined
|
||||
- [ ] Directory creation steps present
|
||||
- [ ] File copy operations specified
|
||||
- [ ] Module registration included
|
||||
- [ ] Post-install message defined
|
||||
|
||||
## Installation Infrastructure
|
||||
|
||||
### Installer Files
|
||||
|
||||
- [ ] Install configuration validates against schema
|
||||
- [ ] All source paths exist or are marked as templates
|
||||
- [ ] Destination paths use correct variables
|
||||
- [ ] Optional vs required steps clearly marked
|
||||
|
||||
### installer.js (if present)
|
||||
|
||||
- [ ] Main `installModule` function exists
|
||||
- [ ] Error handling implemented
|
||||
- [ ] Console logging for user feedback
|
||||
- [ ] Exports correct function names
|
||||
- [ ] Placeholder code replaced with actual logic (or logged as TODO)
|
||||
|
||||
### External Assets (if any)
|
||||
|
||||
- [ ] Asset files exist in assets directory
|
||||
- [ ] Copy destinations are valid
|
||||
- [ ] Permissions requirements documented
|
||||
|
||||
## Documentation
|
||||
|
||||
### README.md
|
||||
|
||||
- [ ] Module overview section present
|
||||
- [ ] Installation instructions included
|
||||
- [ ] Component listing with descriptions
|
||||
- [ ] Quick start guide provided
|
||||
- [ ] Configuration options documented
|
||||
- [ ] At least one usage example
|
||||
- [ ] Directory structure shown
|
||||
- [ ] Author and date information
|
||||
|
||||
### Component Documentation
|
||||
|
||||
- [ ] Each agent has purpose documentation
|
||||
- [ ] Each workflow has description
|
||||
- [ ] Tasks are documented (if present)
|
||||
- [ ] Examples demonstrate typical usage
|
||||
|
||||
### Development Roadmap
|
||||
|
||||
- [ ] TODO.md or roadmap section exists
|
||||
- [ ] Planned components listed
|
||||
- [ ] Development phases identified
|
||||
- [ ] Quick commands for adding components
|
||||
|
||||
## Integration
|
||||
|
||||
### Cross-component References
|
||||
|
||||
- [ ] Agents reference correct workflow paths
|
||||
- [ ] Workflows reference correct task paths
|
||||
- [ ] All internal paths use module variables
|
||||
- [ ] External dependencies declared
|
||||
|
||||
### Module Boundaries
|
||||
|
||||
- [ ] Module scope is well-defined
|
||||
- [ ] No feature creep into other domains
|
||||
- [ ] Clear separation from other modules
|
||||
|
||||
## Quality Checks
|
||||
|
||||
### Completeness
|
||||
|
||||
- [ ] At least one functional component (not all placeholders)
|
||||
- [ ] Core functionality is implementable
|
||||
- [ ] Module provides clear value
|
||||
|
||||
### Consistency
|
||||
|
||||
- [ ] Formatting consistent across files
|
||||
- [ ] Variable naming follows conventions
|
||||
- [ ] Communication style appropriate for domain
|
||||
|
||||
### Scalability
|
||||
|
||||
- [ ] Structure supports future growth
|
||||
- [ ] Component organization is logical
|
||||
- [ ] No hard-coded limits
|
||||
|
||||
## Testing and Validation
|
||||
|
||||
### Structural Validation
|
||||
|
||||
- [ ] YAML files parse without errors
|
||||
- [ ] JSON files (if any) are valid
|
||||
- [ ] XML files (if any) are well-formed
|
||||
- [ ] No syntax errors in JavaScript files
|
||||
|
||||
### Path Validation
|
||||
|
||||
- [ ] All referenced paths exist or are clearly marked as TODO
|
||||
- [ ] Variable substitutions are correct
|
||||
- [ ] No absolute paths (unless intentional)
|
||||
|
||||
### Installation Testing
|
||||
|
||||
- [ ] Installation steps can be simulated
|
||||
- [ ] No circular dependencies
|
||||
- [ ] Uninstall process defined (if complex)
|
||||
|
||||
## Final Checks
|
||||
|
||||
### Ready for Use
|
||||
|
||||
- [ ] Module can be installed without errors
|
||||
- [ ] At least one component is functional
|
||||
- [ ] User can understand how to get started
|
||||
- [ ] Next steps are clear
|
||||
|
||||
### Professional Quality
|
||||
|
||||
- [ ] No placeholder text remains (unless marked TODO)
|
||||
- [ ] No obvious typos or grammar issues
|
||||
- [ ] Professional tone throughout
|
||||
- [ ] Contact/support information provided
|
||||
|
||||
## Issues Found
|
||||
|
||||
### Critical Issues
|
||||
|
||||
<!-- List any issues that MUST be fixed before module can be used -->
|
||||
|
||||
### Warnings
|
||||
|
||||
<!-- List any issues that should be addressed but won't prevent basic usage -->
|
||||
|
||||
### Improvements
|
||||
|
||||
<!-- List any optional enhancements that would improve the module -->
|
||||
|
||||
### Missing Components
|
||||
|
||||
<!-- List any planned components not yet implemented -->
|
||||
|
||||
## Module Complexity Assessment
|
||||
|
||||
### Complexity Rating
|
||||
|
||||
- [ ] Simple (1-2 agents, 2-3 workflows)
|
||||
- [ ] Standard (3-5 agents, 5-10 workflows)
|
||||
- [ ] Complex (5+ agents, 10+ workflows)
|
||||
|
||||
### Readiness Level
|
||||
|
||||
- [ ] Prototype (Basic structure, mostly placeholders)
|
||||
- [ ] Alpha (Core functionality works)
|
||||
- [ ] Beta (Most features complete, needs testing)
|
||||
- [ ] Release (Full functionality, documented)
|
||||
|
||||
## Sign-off
|
||||
|
||||
**Module Name:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
|
||||
**Module Code:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
|
||||
**Version:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
|
||||
**Validated By:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
|
||||
**Date:** \***\*\*\*\*\***\_\_\***\*\*\*\*\***
|
||||
**Status:** ⬜ Pass / ⬜ Pass with Issues / ⬜ Fail
|
||||
@@ -0,0 +1,132 @@
|
||||
# {{MODULE_NAME}} Installation Configuration Template
|
||||
# This file defines how the module gets installed into a BMAD system
|
||||
|
||||
module_name: "{{MODULE_NAME}}"
|
||||
module_code: "{{MODULE_CODE}}"
|
||||
author: "{{AUTHOR}}"
|
||||
installation_date: "{{DATE}}"
|
||||
bmad_version_required: "6.0.0"
|
||||
|
||||
# Module metadata
|
||||
metadata:
|
||||
description: "{{MODULE_DESCRIPTION}}"
|
||||
category: "{{MODULE_CATEGORY}}"
|
||||
tags: ["{{MODULE_TAGS}}"]
|
||||
homepage: "{{MODULE_HOMEPAGE}}"
|
||||
license: "{{MODULE_LICENSE}}"
|
||||
|
||||
# Pre-installation checks
|
||||
pre_install_checks:
|
||||
- name: "Check BMAD version"
|
||||
type: "version_check"
|
||||
minimum: "6.0.0"
|
||||
|
||||
- name: "Check dependencies"
|
||||
type: "module_check"
|
||||
required_modules: [] # List any required modules
|
||||
|
||||
- name: "Check disk space"
|
||||
type: "disk_check"
|
||||
required_mb: 50
|
||||
|
||||
# Installation steps
|
||||
install_steps:
|
||||
- name: "Create module directories"
|
||||
action: "mkdir"
|
||||
paths:
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}"
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}/data"
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}/agents"
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}/workflows"
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}/config"
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}/logs"
|
||||
|
||||
- name: "Copy module configuration"
|
||||
action: "copy"
|
||||
files:
|
||||
- source: "config.yaml"
|
||||
dest: "{project-root}/bmad/{{MODULE_CODE}}/config.yaml"
|
||||
|
||||
- name: "Copy default data files"
|
||||
action: "copy"
|
||||
optional: true
|
||||
files:
|
||||
- source: "data/*"
|
||||
dest: "{project-root}/bmad/{{MODULE_CODE}}/data/"
|
||||
|
||||
- name: "Register module in manifest"
|
||||
action: "register"
|
||||
manifest_path: "{project-root}/bmad/_cfg/manifest.yaml"
|
||||
entry:
|
||||
module: "{{MODULE_CODE}}"
|
||||
status: "active"
|
||||
path: "{project-root}/bmad/{{MODULE_CODE}}"
|
||||
|
||||
- name: "Setup agent shortcuts"
|
||||
action: "create_shortcuts"
|
||||
agents: "{{AGENT_LIST}}"
|
||||
|
||||
- name: "Initialize module database"
|
||||
action: "exec"
|
||||
optional: true
|
||||
script: "installer.js"
|
||||
function: "initDatabase"
|
||||
|
||||
# External assets to install
|
||||
external_assets:
|
||||
- description: "Module documentation"
|
||||
source: "assets/docs/*"
|
||||
dest: "{project-root}/docs/{{MODULE_CODE}}/"
|
||||
|
||||
- description: "Example configurations"
|
||||
source: "assets/examples/*"
|
||||
dest: "{project-root}/examples/{{MODULE_CODE}}/"
|
||||
optional: true
|
||||
|
||||
# Module configuration defaults
|
||||
default_config:
|
||||
output_folder: "{project-root}/output/{{MODULE_CODE}}"
|
||||
data_folder: "{project-root}/bmad/{{MODULE_CODE}}/data"
|
||||
log_level: "info"
|
||||
auto_save: true
|
||||
# {{CUSTOM_CONFIG}}
|
||||
|
||||
# Post-installation setup
|
||||
post_install:
|
||||
- name: "Run initial setup"
|
||||
action: "workflow"
|
||||
workflow: "{{MODULE_CODE}}-setup"
|
||||
optional: true
|
||||
|
||||
- name: "Generate sample data"
|
||||
action: "exec"
|
||||
script: "installer.js"
|
||||
function: "generateSamples"
|
||||
optional: true
|
||||
|
||||
- name: "Verify installation"
|
||||
action: "test"
|
||||
test_command: "bmad test {{MODULE_CODE}}"
|
||||
|
||||
# Post-installation message
|
||||
post_install_message: |
|
||||
✅ {{MODULE_NAME}} has been installed successfully!
|
||||
|
||||
🚀 Quick Start:
|
||||
1. Load the main agent: `agent {{PRIMARY_AGENT}}`
|
||||
2. View available commands: `*help`
|
||||
3. Run the main workflow: `workflow {{PRIMARY_WORKFLOW}}`
|
||||
|
||||
📚 Documentation: {project-root}/docs/{{MODULE_CODE}}/README.md
|
||||
💡 Examples: {project-root}/examples/{{MODULE_CODE}}/
|
||||
|
||||
{{CUSTOM_MESSAGE}}
|
||||
|
||||
# Uninstall configuration
|
||||
uninstall:
|
||||
preserve_user_data: true
|
||||
remove_paths:
|
||||
- "{project-root}/bmad/{{MODULE_CODE}}"
|
||||
- "{project-root}/docs/{{MODULE_CODE}}"
|
||||
backup_before_remove: true
|
||||
unregister_from_manifest: true
|
||||
@@ -0,0 +1,231 @@
|
||||
/* eslint-disable unicorn/prefer-module, unicorn/prefer-node-protocol */
|
||||
/**
|
||||
* {{MODULE_NAME}} Module Installer
|
||||
* Custom installation logic for complex module setup
|
||||
*
|
||||
* This is a template - replace {{VARIABLES}} with actual values
|
||||
*/
|
||||
|
||||
// const fs = require('fs'); // Uncomment when implementing file operations
|
||||
const path = require('path');
|
||||
|
||||
/**
|
||||
* Main installation function
|
||||
* Called by BMAD installer when processing the module
|
||||
*/
|
||||
async function installModule(config) {
|
||||
console.log('🚀 Installing {{MODULE_NAME}} module...');
|
||||
console.log(` Version: ${config.version}`);
|
||||
console.log(` Module Code: ${config.module_code}`);
|
||||
|
||||
try {
|
||||
// Step 1: Validate environment
|
||||
await validateEnvironment(config);
|
||||
|
||||
// Step 2: Setup custom configurations
|
||||
await setupConfigurations(config);
|
||||
|
||||
// Step 3: Initialize module-specific features
|
||||
await initializeFeatures(config);
|
||||
|
||||
// Step 4: Run post-install tasks
|
||||
await runPostInstallTasks(config);
|
||||
|
||||
console.log('✅ {{MODULE_NAME}} module installed successfully!');
|
||||
return {
|
||||
success: true,
|
||||
message: 'Module installed and configured',
|
||||
};
|
||||
} catch (error) {
|
||||
console.error('❌ Installation failed:', error.message);
|
||||
return {
|
||||
success: false,
|
||||
error: error.message,
|
||||
};
|
||||
}
|
||||
}
|
||||
|
||||
/**
|
||||
* Validate that the environment meets module requirements
|
||||
*/
|
||||
async function validateEnvironment(config) {
|
||||
console.log(' Validating environment...');
|
||||
|
||||
// TODO: Add environment checks
|
||||
// Examples:
|
||||
// - Check for required tools/binaries
|
||||
// - Verify permissions
|
||||
// - Check network connectivity
|
||||
// - Validate API keys
|
||||
|
||||
// Placeholder validation
|
||||
if (!config.project_root) {
|
||||
throw new Error('Project root not defined');
|
||||
}
|
||||
|
||||
console.log(' ✓ Environment validated');
|
||||
}
|
||||
|
||||
/**
|
||||
* Setup module-specific configurations
|
||||
*/
|
||||
async function setupConfigurations(config) {
|
||||
console.log(' Setting up configurations...');
|
||||
|
||||
// TODO: Add configuration setup
|
||||
// Examples:
|
||||
// - Create config files
|
||||
// - Setup environment variables
|
||||
// - Configure external services
|
||||
// - Initialize settings
|
||||
|
||||
// Placeholder configuration
|
||||
const configPath = path.join(config.project_root, 'bmad', config.module_code, 'config.json');
|
||||
|
||||
// Example of module config that would be created
|
||||
// const moduleConfig = {
|
||||
// installed: new Date().toISOString(),
|
||||
// settings: {
|
||||
// // Add default settings
|
||||
// }
|
||||
// };
|
||||
|
||||
// Note: This is a placeholder - actual implementation would write the file
|
||||
console.log(` ✓ Would create config at: ${configPath}`);
|
||||
console.log(' ✓ Configurations complete');
|
||||
}
|
||||
|
||||
/**
|
||||
* Initialize module-specific features
|
||||
*/
|
||||
async function initializeFeatures(config) {
|
||||
console.log(' Initializing features...');
|
||||
|
||||
// TODO: Add feature initialization
|
||||
// Examples:
|
||||
// - Create database schemas
|
||||
// - Setup cron jobs
|
||||
// - Initialize caches
|
||||
// - Register webhooks
|
||||
// - Setup file watchers
|
||||
|
||||
// Module-specific initialization based on type
|
||||
switch (config.module_category) {
|
||||
case 'data': {
|
||||
await initializeDataFeatures(config);
|
||||
break;
|
||||
}
|
||||
case 'automation': {
|
||||
await initializeAutomationFeatures(config);
|
||||
break;
|
||||
}
|
||||
case 'integration': {
|
||||
await initializeIntegrationFeatures(config);
|
||||
break;
|
||||
}
|
||||
default: {
|
||||
console.log(' - Using standard initialization');
|
||||
}
|
||||
}
|
||||
|
||||
console.log(' ✓ Features initialized');
|
||||
}
|
||||
|
||||
/**
|
||||
* Initialize data-related features
|
||||
*/
|
||||
async function initializeDataFeatures(/* config */) {
|
||||
console.log(' - Setting up data storage...');
|
||||
// TODO: Setup databases, data folders, etc.
|
||||
}
|
||||
|
||||
/**
|
||||
* Initialize automation features
|
||||
*/
|
||||
async function initializeAutomationFeatures(/* config */) {
|
||||
console.log(' - Setting up automation hooks...');
|
||||
// TODO: Setup triggers, watchers, schedulers
|
||||
}
|
||||
|
||||
/**
|
||||
* Initialize integration features
|
||||
*/
|
||||
async function initializeIntegrationFeatures(/* config */) {
|
||||
console.log(' - Setting up integrations...');
|
||||
// TODO: Configure APIs, webhooks, external services
|
||||
}
|
||||
|
||||
/**
|
||||
* Run post-installation tasks
|
||||
*/
|
||||
async function runPostInstallTasks(/* config */) {
|
||||
console.log(' Running post-install tasks...');
|
||||
|
||||
// TODO: Add post-install tasks
|
||||
// Examples:
|
||||
// - Generate sample data
|
||||
// - Run initial workflows
|
||||
// - Send notifications
|
||||
// - Update registries
|
||||
|
||||
console.log(' ✓ Post-install tasks complete');
|
||||
}
|
||||
|
||||
/**
|
||||
* Initialize database for the module (optional)
|
||||
*/
|
||||
async function initDatabase(/* config */) {
|
||||
console.log(' Initializing database...');
|
||||
|
||||
// TODO: Add database initialization
|
||||
// This function can be called from install-module-config.yaml
|
||||
|
||||
console.log(' ✓ Database initialized');
|
||||
}
|
||||
|
||||
/**
|
||||
* Generate sample data for the module (optional)
|
||||
*/
|
||||
async function generateSamples(config) {
|
||||
console.log(' Generating sample data...');
|
||||
|
||||
// TODO: Create sample files, data, configurations
|
||||
// This helps users understand how to use the module
|
||||
|
||||
const samplesPath = path.join(config.project_root, 'examples', config.module_code);
|
||||
|
||||
console.log(` - Would create samples at: ${samplesPath}`);
|
||||
console.log(' ✓ Samples generated');
|
||||
}
|
||||
|
||||
/**
|
||||
* Uninstall the module (cleanup)
|
||||
*/
|
||||
async function uninstallModule(/* config */) {
|
||||
console.log('🗑️ Uninstalling {{MODULE_NAME}} module...');
|
||||
|
||||
try {
|
||||
// TODO: Add cleanup logic
|
||||
// - Remove configurations
|
||||
// - Clean up databases
|
||||
// - Unregister services
|
||||
// - Backup user data
|
||||
|
||||
console.log('✅ Module uninstalled successfully');
|
||||
return { success: true };
|
||||
} catch (error) {
|
||||
console.error('❌ Uninstall failed:', error.message);
|
||||
return {
|
||||
success: false,
|
||||
error: error.message,
|
||||
};
|
||||
}
|
||||
}
|
||||
|
||||
// Export functions for BMAD installer
|
||||
module.exports = {
|
||||
installModule,
|
||||
initDatabase,
|
||||
generateSamples,
|
||||
uninstallModule,
|
||||
};
|
||||
509
bmad/bmb/workflows/create-module/instructions.md
Normal file
509
bmad/bmb/workflows/create-module/instructions.md
Normal file
@@ -0,0 +1,509 @@
|
||||
# Build Module - Interactive Module Builder Instructions
|
||||
|
||||
<critical>The workflow execution engine is governed by: {project_root}/bmad/core/tasks/workflow.md</critical>
|
||||
<critical>You MUST have already loaded and processed: {project_root}/bmad/bmb/workflows/create-module/workflow.yaml</critical>
|
||||
<critical>Study existing modules in: {project_root}/bmad/ for patterns</critical>
|
||||
|
||||
<workflow>
|
||||
|
||||
<step n="-1" goal="Optional brainstorming for module ideas" optional="true">
|
||||
<ask>Do you want to brainstorm module ideas first? [y/n]</ask>
|
||||
|
||||
If yes:
|
||||
<action>Invoke brainstorming workflow: {brainstorming-workflow}</action>
|
||||
<action>Pass context data: {brainstorming_context}</action>
|
||||
<action>Wait for brainstorming session completion</action>
|
||||
<action>Use brainstorming output to inform module concept, agent lineup, and workflow portfolio</action>
|
||||
|
||||
If no, proceed to check for module brief.
|
||||
|
||||
<template-output>brainstorming_results</template-output>
|
||||
</step>
|
||||
|
||||
<step n="0" goal="Check for module brief" optional="true">
|
||||
<ask>Do you have a module brief or should we create one? [have/create/skip]</ask>
|
||||
|
||||
If create:
|
||||
<action>Invoke module-brief workflow: {project-root}/bmad/bmb/workflows/module-brief/workflow.yaml</action>
|
||||
<action>Wait for module brief completion</action>
|
||||
<action>Load the module brief to use as blueprint</action>
|
||||
|
||||
If have:
|
||||
<ask>Provide path to module brief document</ask>
|
||||
<action>Load the module brief and use it to pre-populate all planning sections</action>
|
||||
|
||||
If skip, proceed directly to module definition.
|
||||
|
||||
<template-output>module_brief</template-output>
|
||||
</step>
|
||||
|
||||
<step n="1" goal="Define module concept and scope">
|
||||
<critical>Load and study the complete module structure guide</critical>
|
||||
<action>Load module structure guide: {module_structure_guide}</action>
|
||||
<action>Understand module types (Simple/Standard/Complex)</action>
|
||||
<action>Review directory structures and component guidelines</action>
|
||||
<action>Study the installation infrastructure patterns</action>
|
||||
|
||||
Ask the user about their module vision:
|
||||
|
||||
**Module Identity:**
|
||||
|
||||
1. **Module code** (kebab-case, e.g., "rpg-toolkit", "data-viz", "team-collab")
|
||||
2. **Module name** (friendly name, e.g., "RPG Toolkit", "Data Visualization Suite")
|
||||
3. **Module purpose** (1-2 sentences describing what it does)
|
||||
4. **Target audience** (who will use this module?)
|
||||
|
||||
**Module Theme Examples:**
|
||||
|
||||
- **Domain-Specific:** Legal, Medical, Finance, Education
|
||||
- **Creative:** RPG/Gaming, Story Writing, Music Production
|
||||
- **Technical:** DevOps, Testing, Architecture, Security
|
||||
- **Business:** Project Management, Marketing, Sales
|
||||
- **Personal:** Journaling, Learning, Productivity
|
||||
|
||||
<critical>Check {src_impact} variable to determine output location:</critical>
|
||||
|
||||
- If {src_impact} = true: Module will be created at {src_output_folder}
|
||||
- If {src_impact} = false: Module will be created at {default_output_folder}
|
||||
|
||||
Store module identity for scaffolding.
|
||||
|
||||
<template-output>module_identity</template-output>
|
||||
</step>
|
||||
|
||||
<step n="2" goal="Plan module components">
|
||||
Gather the module's component architecture:
|
||||
|
||||
**Agents Planning:**
|
||||
Ask: How many agents will this module have? (typically 1-5)
|
||||
|
||||
For each agent, gather:
|
||||
|
||||
- Agent name and purpose
|
||||
- Will it be Simple, Expert, or Module type?
|
||||
- Key commands it should have
|
||||
- Create now or placeholder for later?
|
||||
|
||||
Example for RPG module:
|
||||
|
||||
1. DM Agent - Dungeon Master assistant (Module type)
|
||||
2. NPC Agent - Character simulation (Expert type)
|
||||
3. Story Writer Agent - Adventure creation (Module type)
|
||||
|
||||
**Workflows Planning:**
|
||||
Ask: How many workflows? (typically 2-10)
|
||||
|
||||
For each workflow, gather:
|
||||
|
||||
- Workflow name and purpose
|
||||
- Document, Action, or Interactive type?
|
||||
- Complexity (simple/complex)
|
||||
- Create now or placeholder?
|
||||
|
||||
Example workflows:
|
||||
|
||||
1. adventure-plan - Create full adventure (Document)
|
||||
2. random-encounter - Quick encounter generator (Action)
|
||||
3. npc-generator - Create NPCs on the fly (Interactive)
|
||||
4. treasure-generator - Loot tables (Action)
|
||||
|
||||
**Tasks Planning (optional):**
|
||||
Ask: Any special tasks that don't warrant full workflows?
|
||||
|
||||
For each task:
|
||||
|
||||
- Task name and purpose
|
||||
- Standalone or supporting?
|
||||
|
||||
<template-output>module_components</template-output>
|
||||
</step>
|
||||
|
||||
<step n="3" goal="Create module directory structure">
|
||||
<critical>Determine base module path based on {src_impact}:</critical>
|
||||
- If {src_impact} = true: Use {src_output_folder}
|
||||
- If {src_impact} = false: Use {default_output_folder}
|
||||
|
||||
<action>Create base module directories at the determined path:</action>
|
||||
|
||||
```
|
||||
{{module_code}}/
|
||||
├── agents/ # Agent definitions
|
||||
├── workflows/ # Workflow folders
|
||||
├── tasks/ # Task files (if any)
|
||||
├── templates/ # Shared templates
|
||||
├── data/ # Module data files
|
||||
├── config.yaml # Module configuration
|
||||
└── README.md # Module documentation
|
||||
```
|
||||
|
||||
<action>Create installer directory:</action>
|
||||
|
||||
```
|
||||
{{module_code}}/
|
||||
├── _module-installer/
|
||||
│ ├── install-module-config.yaml
|
||||
│ ├── installer.js (optional)
|
||||
│ └── assets/ # Files to copy during install
|
||||
├── config.yaml # Runtime configuration
|
||||
├── agents/ # Agent configs (optional)
|
||||
├── workflows/ # Workflow instances
|
||||
└── data/ # User data directory
|
||||
```
|
||||
|
||||
<template-output>directory_structure</template-output>
|
||||
</step>
|
||||
|
||||
<step n="4" goal="Generate module configuration">
|
||||
Create the main module config.yaml:
|
||||
|
||||
```yaml
|
||||
# {{module_name}} Module Configuration
|
||||
module_name: {{module_name}}
|
||||
module_code: {{module_code}}
|
||||
author: {{user_name}}
|
||||
description: {{module_purpose}}
|
||||
|
||||
# Module paths
|
||||
module_root: "{project-root}/bmad/{{module_code}}"
|
||||
installer_path: "{project-root}/bmad/{{module_code}}"
|
||||
|
||||
# Component counts
|
||||
agents:
|
||||
count: {{agent_count}}
|
||||
list: {{agent_list}}
|
||||
|
||||
workflows:
|
||||
count: {{workflow_count}}
|
||||
list: {{workflow_list}}
|
||||
|
||||
tasks:
|
||||
count: {{task_count}}
|
||||
list: {{task_list}}
|
||||
|
||||
# Module-specific settings
|
||||
{{custom_settings}}
|
||||
|
||||
# Output configuration
|
||||
output_folder: "{project-root}/docs/{{module_code}}"
|
||||
data_folder: "{{determined_module_path}}/data"
|
||||
```
|
||||
|
||||
<critical>Determine save location based on {src_impact}:</critical>
|
||||
|
||||
- If {src_impact} = true: Save to {src_output_folder}/config.yaml
|
||||
- If {src_impact} = false: Save to {default_output_folder}/config.yaml
|
||||
|
||||
<template-output>module_config</template-output>
|
||||
</step>
|
||||
|
||||
<step n="5" goal="Create first agent" optional="true">
|
||||
Ask: **Create your first agent now? [Yes/no]**
|
||||
|
||||
If yes:
|
||||
<invoke-workflow input="{{module_components}}">
|
||||
{agent_builder}
|
||||
</invoke-workflow>
|
||||
|
||||
Guide them to create the primary agent for the module.
|
||||
<critical>Ensure it's saved to the correct location based on {src_impact}:</critical>
|
||||
|
||||
- If {src_impact} = true: {src_output_folder}/agents/
|
||||
- If {src_impact} = false: {default_output_folder}/agents/
|
||||
|
||||
If no, create placeholder:
|
||||
|
||||
```md
|
||||
# {{primary_agent_name}} Agent
|
||||
|
||||
<!-- TODO: Create using create-agent workflow -->
|
||||
<!-- Purpose: {{agent_purpose}} -->
|
||||
<!-- Type: {{agent_type}} -->
|
||||
```
|
||||
|
||||
<template-output>first_agent</template-output>
|
||||
</step>
|
||||
|
||||
<step n="6" goal="Create first workflow" optional="true">
|
||||
Ask: **Create your first workflow now? [Yes/no]**
|
||||
|
||||
If yes:
|
||||
<invoke-workflow input="{{module_components}}">
|
||||
{workflow_builder}
|
||||
</invoke-workflow>
|
||||
|
||||
Guide them to create the primary workflow.
|
||||
<critical>Ensure it's saved to the correct location based on {src_impact}:</critical>
|
||||
|
||||
- If {src_impact} = true: {src_output_folder}/workflows/
|
||||
- If {src_impact} = false: {default_output_folder}/workflows/
|
||||
|
||||
If no, create placeholder structure:
|
||||
|
||||
```
|
||||
workflows/{{workflow_name}}/
|
||||
├── workflow.yaml # TODO: Configure
|
||||
├── instructions.md # TODO: Add steps
|
||||
└── template.md # TODO: If document workflow
|
||||
```
|
||||
|
||||
<template-output>first_workflow</template-output>
|
||||
</step>
|
||||
|
||||
<step n="7" goal="Setup module installer">
|
||||
<action>Load installer templates from: {installer_templates}</action>
|
||||
|
||||
Create install-module-config.yaml:
|
||||
|
||||
```yaml
|
||||
# {{module_name}} Installation Configuration
|
||||
module_name: { { module_name } }
|
||||
module_code: { { module_code } }
|
||||
installation_date: { { date } }
|
||||
|
||||
# Installation steps
|
||||
install_steps:
|
||||
- name: 'Create directories'
|
||||
action: 'mkdir'
|
||||
paths:
|
||||
- '{project-root}/bmad/{{module_code}}'
|
||||
- '{project-root}/bmad/{{module_code}}/data'
|
||||
- '{project-root}/bmad/{{module_code}}/agents'
|
||||
|
||||
- name: 'Copy configuration'
|
||||
action: 'copy'
|
||||
source: '{installer_path}/config.yaml'
|
||||
dest: '{project-root}/bmad/{{module_code}}/config.yaml'
|
||||
|
||||
- name: 'Register module'
|
||||
action: 'register'
|
||||
manifest: '{project-root}/bmad/_cfg/manifest.yaml'
|
||||
|
||||
# External assets (if any)
|
||||
external_assets:
|
||||
- description: '{{asset_description}}'
|
||||
source: 'assets/{{filename}}'
|
||||
dest: '{{destination_path}}'
|
||||
|
||||
# Post-install message
|
||||
post_install_message: |
|
||||
{{module_name}} has been installed successfully!
|
||||
|
||||
To get started:
|
||||
1. Load any {{module_code}} agent
|
||||
2. Use *help to see available commands
|
||||
3. Check README.md for full documentation
|
||||
```
|
||||
|
||||
Create installer.js stub (optional):
|
||||
|
||||
```javascript
|
||||
// {{module_name}} Module Installer
|
||||
// This is a placeholder for complex installation logic
|
||||
|
||||
function installModule(config) {
|
||||
console.log('Installing {{module_name}} module...');
|
||||
|
||||
// TODO: Add any complex installation logic here
|
||||
// Examples:
|
||||
// - Database setup
|
||||
// - API key configuration
|
||||
// - External service registration
|
||||
// - File system preparation
|
||||
|
||||
console.log('{{module_name}} module installed successfully!');
|
||||
return true;
|
||||
}
|
||||
|
||||
module.exports = { installModule };
|
||||
```
|
||||
|
||||
<template-output>installer_config</template-output>
|
||||
</step>
|
||||
|
||||
<step n="8" goal="Create module documentation">
|
||||
Generate comprehensive README.md:
|
||||
|
||||
````markdown
|
||||
# {{module_name}}
|
||||
|
||||
{{module_purpose}}
|
||||
|
||||
## Overview
|
||||
|
||||
This module provides:
|
||||
{{component_summary}}
|
||||
|
||||
## Installation
|
||||
|
||||
```bash
|
||||
bmad install {{module_code}}
|
||||
```
|
||||
````
|
||||
|
||||
## Components
|
||||
|
||||
### Agents ({{agent_count}})
|
||||
|
||||
{{agent_documentation}}
|
||||
|
||||
### Workflows ({{workflow_count}})
|
||||
|
||||
{{workflow_documentation}}
|
||||
|
||||
### Tasks ({{task_count}})
|
||||
|
||||
{{task_documentation}}
|
||||
|
||||
## Quick Start
|
||||
|
||||
1. **Load the main agent:**
|
||||
|
||||
```
|
||||
agent {{primary_agent}}
|
||||
```
|
||||
|
||||
2. **View available commands:**
|
||||
|
||||
```
|
||||
*help
|
||||
```
|
||||
|
||||
3. **Run the main workflow:**
|
||||
```
|
||||
workflow {{primary_workflow}}
|
||||
```
|
||||
|
||||
## Module Structure
|
||||
|
||||
```
|
||||
{{directory_tree}}
|
||||
```
|
||||
|
||||
## Configuration
|
||||
|
||||
The module can be configured in `bmad/{{module_code}}/config.yaml`
|
||||
|
||||
Key settings:
|
||||
{{configuration_options}}
|
||||
|
||||
## Examples
|
||||
|
||||
### Example 1: {{example_use_case}}
|
||||
|
||||
{{example_walkthrough}}
|
||||
|
||||
## Development Roadmap
|
||||
|
||||
- [ ] {{roadmap_item_1}}
|
||||
- [ ] {{roadmap_item_2}}
|
||||
- [ ] {{roadmap_item_3}}
|
||||
|
||||
## Contributing
|
||||
|
||||
To extend this module:
|
||||
|
||||
1. Add new agents using `create-agent` workflow
|
||||
2. Add new workflows using `create-workflow` workflow
|
||||
3. Submit improvements via pull request
|
||||
|
||||
## Author
|
||||
|
||||
Created by {{user_name}} on {{date}}
|
||||
|
||||
````
|
||||
|
||||
<template-output>module_readme</template-output>
|
||||
</step>
|
||||
|
||||
<step n="9" goal="Generate component roadmap">
|
||||
Create a development roadmap for remaining components:
|
||||
|
||||
**TODO.md file:**
|
||||
```markdown
|
||||
# {{module_name}} Development Roadmap
|
||||
|
||||
## Phase 1: Core Components
|
||||
{{phase1_tasks}}
|
||||
|
||||
## Phase 2: Enhanced Features
|
||||
{{phase2_tasks}}
|
||||
|
||||
## Phase 3: Polish and Integration
|
||||
{{phase3_tasks}}
|
||||
|
||||
## Quick Commands
|
||||
|
||||
Create new agent:
|
||||
````
|
||||
|
||||
workflow create-agent
|
||||
|
||||
```
|
||||
|
||||
Create new workflow:
|
||||
```
|
||||
|
||||
workflow create-workflow
|
||||
|
||||
```
|
||||
|
||||
## Notes
|
||||
{{development_notes}}
|
||||
```
|
||||
|
||||
Ask if user wants to:
|
||||
|
||||
1. Continue building more components now
|
||||
2. Save roadmap for later development
|
||||
3. Test what's been built so far
|
||||
|
||||
<template-output>development_roadmap</template-output>
|
||||
</step>
|
||||
|
||||
<step n="10" goal="Validate and finalize module">
|
||||
Run validation checks:
|
||||
|
||||
1. **Structure validation:**
|
||||
- All required directories created
|
||||
- Config files properly formatted
|
||||
- Installer configuration valid
|
||||
|
||||
2. **Component validation:**
|
||||
- At least one agent or workflow exists (or planned)
|
||||
- All references use correct paths
|
||||
- Module code consistent throughout
|
||||
|
||||
3. **Documentation validation:**
|
||||
- README.md complete
|
||||
- Installation instructions clear
|
||||
- Examples provided
|
||||
|
||||
Show summary:
|
||||
|
||||
```
|
||||
✅ Module: {{module_name}} ({{module_code}})
|
||||
📁 Location:
|
||||
- If {src_impact} = true: {src_output_folder}
|
||||
- If {src_impact} = false: {default_output_folder}
|
||||
👥 Agents: {{agent_count}} ({{agents_created}} created, {{agents_planned}} planned)
|
||||
📋 Workflows: {{workflow_count}} ({{workflows_created}} created, {{workflows_planned}} planned)
|
||||
📝 Tasks: {{task_count}}
|
||||
📦 Installer: Ready at same location
|
||||
```
|
||||
|
||||
Next steps:
|
||||
|
||||
1. Complete remaining components using roadmap
|
||||
2. Test module with: `bmad install {{module_code}}`
|
||||
3. Share module or integrate with existing system
|
||||
|
||||
Ask: Would you like to:
|
||||
|
||||
- Create another component now?
|
||||
- Test the module installation?
|
||||
- Exit and continue later?
|
||||
|
||||
<template-output>module_summary</template-output>
|
||||
</step>
|
||||
|
||||
</workflow>
|
||||
310
bmad/bmb/workflows/create-module/module-structure.md
Normal file
310
bmad/bmb/workflows/create-module/module-structure.md
Normal file
@@ -0,0 +1,310 @@
|
||||
# BMAD Module Structure Guide
|
||||
|
||||
## What is a Module?
|
||||
|
||||
A BMAD module is a self-contained package of agents, workflows, tasks, and resources that work together to provide specialized functionality. Think of it as an expansion pack for the BMAD Method.
|
||||
|
||||
## Module Architecture
|
||||
|
||||
### Core Structure
|
||||
|
||||
```
|
||||
project-root/
|
||||
├── bmad/{module-code}/ # Source code
|
||||
│ ├── agents/ # Agent definitions
|
||||
│ ├── workflows/ # Workflow folders
|
||||
│ ├── tasks/ # Task files
|
||||
│ ├── templates/ # Shared templates
|
||||
│ ├── data/ # Static data
|
||||
│ ├── config.yaml # Module config
|
||||
│ └── README.md # Documentation
|
||||
│
|
||||
└── bmad/{module-code}/ # Runtime instance
|
||||
├── _module-installer/ # Installation files
|
||||
│ ├── install-module-config.yaml
|
||||
│ ├── installer.js # Optional
|
||||
│ └── assets/ # Install assets
|
||||
├── config.yaml # User config
|
||||
├── agents/ # Agent overrides
|
||||
├── workflows/ # Workflow instances
|
||||
└── data/ # User data
|
||||
|
||||
```
|
||||
|
||||
## Module Types by Complexity
|
||||
|
||||
### Simple Module (1-2 agents, 2-3 workflows)
|
||||
|
||||
Perfect for focused, single-purpose tools.
|
||||
|
||||
**Example: Code Review Module**
|
||||
|
||||
- 1 Reviewer Agent
|
||||
- 2 Workflows: quick-review, deep-review
|
||||
- Clear, narrow scope
|
||||
|
||||
### Standard Module (3-5 agents, 5-10 workflows)
|
||||
|
||||
Comprehensive solution for a domain.
|
||||
|
||||
**Example: Project Management Module**
|
||||
|
||||
- PM Agent, Scrum Master Agent, Analyst Agent
|
||||
- Workflows: sprint-planning, retrospective, roadmap, user-stories
|
||||
- Integrated component ecosystem
|
||||
|
||||
### Complex Module (5+ agents, 10+ workflows)
|
||||
|
||||
Full platform or framework.
|
||||
|
||||
**Example: RPG Toolkit Module**
|
||||
|
||||
- DM Agent, NPC Agent, Monster Agent, Loot Agent, Map Agent
|
||||
- 15+ workflows for every aspect of game management
|
||||
- Multiple interconnected systems
|
||||
|
||||
## Module Naming Conventions
|
||||
|
||||
### Module Code (kebab-case)
|
||||
|
||||
- `data-viz` - Data Visualization
|
||||
- `team-collab` - Team Collaboration
|
||||
- `rpg-toolkit` - RPG Toolkit
|
||||
- `legal-assist` - Legal Assistant
|
||||
|
||||
### Module Name (Title Case)
|
||||
|
||||
- "Data Visualization Suite"
|
||||
- "Team Collaboration Platform"
|
||||
- "RPG Game Master Toolkit"
|
||||
- "Legal Document Assistant"
|
||||
|
||||
## Component Guidelines
|
||||
|
||||
### Agents per Module
|
||||
|
||||
**Recommended Distribution:**
|
||||
|
||||
- **Primary Agent (1)**: The main interface/orchestrator
|
||||
- **Specialist Agents (2-4)**: Domain-specific experts
|
||||
- **Utility Agents (0-2)**: Helper/support functions
|
||||
|
||||
**Anti-patterns to Avoid:**
|
||||
|
||||
- Too many overlapping agents
|
||||
- Agents that could be combined
|
||||
- Agents without clear purpose
|
||||
|
||||
### Workflows per Module
|
||||
|
||||
**Categories:**
|
||||
|
||||
- **Core Workflows (2-3)**: Essential functionality
|
||||
- **Feature Workflows (3-5)**: Specific capabilities
|
||||
- **Utility Workflows (2-3)**: Supporting operations
|
||||
- **Admin Workflows (0-2)**: Maintenance/config
|
||||
|
||||
**Workflow Complexity Guide:**
|
||||
|
||||
- Simple: 3-5 steps, single output
|
||||
- Standard: 5-10 steps, multiple outputs
|
||||
- Complex: 10+ steps, conditional logic, sub-workflows
|
||||
|
||||
### Tasks per Module
|
||||
|
||||
Tasks should be used for:
|
||||
|
||||
- Single-operation utilities
|
||||
- Shared subroutines
|
||||
- Quick actions that don't warrant workflows
|
||||
|
||||
## Module Dependencies
|
||||
|
||||
### Internal Dependencies
|
||||
|
||||
- Agents can reference module workflows
|
||||
- Workflows can invoke module tasks
|
||||
- Tasks can use module templates
|
||||
|
||||
### External Dependencies
|
||||
|
||||
- Reference other modules via full paths
|
||||
- Declare dependencies in config.yaml
|
||||
- Version compatibility notes
|
||||
|
||||
## Installation Infrastructure
|
||||
|
||||
### Required: install-module-config.yaml
|
||||
|
||||
```yaml
|
||||
module_name: 'Module Name'
|
||||
module_code: 'module-code'
|
||||
|
||||
install_steps:
|
||||
- name: 'Create directories'
|
||||
action: 'mkdir'
|
||||
paths: [...]
|
||||
|
||||
- name: 'Copy files'
|
||||
action: 'copy'
|
||||
mappings: [...]
|
||||
|
||||
- name: 'Register module'
|
||||
action: 'register'
|
||||
```
|
||||
|
||||
### Optional: installer.js
|
||||
|
||||
For complex installations requiring:
|
||||
|
||||
- Database setup
|
||||
- API configuration
|
||||
- System integration
|
||||
- Permission management
|
||||
|
||||
### Optional: External Assets
|
||||
|
||||
Files that get copied outside the module:
|
||||
|
||||
- System configurations
|
||||
- User templates
|
||||
- Shared resources
|
||||
- Integration scripts
|
||||
|
||||
## Module Lifecycle
|
||||
|
||||
### Development Phases
|
||||
|
||||
1. **Planning Phase**
|
||||
- Define scope and purpose
|
||||
- Identify components
|
||||
- Design architecture
|
||||
|
||||
2. **Scaffolding Phase**
|
||||
- Create directory structure
|
||||
- Generate configurations
|
||||
- Setup installer
|
||||
|
||||
3. **Building Phase**
|
||||
- Create agents incrementally
|
||||
- Build workflows progressively
|
||||
- Add tasks as needed
|
||||
|
||||
4. **Testing Phase**
|
||||
- Test individual components
|
||||
- Verify integration
|
||||
- Validate installation
|
||||
|
||||
5. **Deployment Phase**
|
||||
- Package module
|
||||
- Document usage
|
||||
- Distribute/share
|
||||
|
||||
## Best Practices
|
||||
|
||||
### Module Cohesion
|
||||
|
||||
- All components should relate to module theme
|
||||
- Clear boundaries between modules
|
||||
- No feature creep
|
||||
|
||||
### Progressive Enhancement
|
||||
|
||||
- Start with MVP (1 agent, 2 workflows)
|
||||
- Add components based on usage
|
||||
- Refactor as patterns emerge
|
||||
|
||||
### Documentation Standards
|
||||
|
||||
- Every module needs README.md
|
||||
- Each agent needs purpose statement
|
||||
- Workflows need clear descriptions
|
||||
- Include examples and quickstart
|
||||
|
||||
### Naming Consistency
|
||||
|
||||
- Use module code prefix for uniqueness
|
||||
- Consistent naming patterns within module
|
||||
- Clear, descriptive names
|
||||
|
||||
## Example Modules
|
||||
|
||||
### Example 1: Personal Productivity
|
||||
|
||||
```
|
||||
productivity/
|
||||
├── agents/
|
||||
│ ├── task-manager.md # GTD methodology
|
||||
│ └── focus-coach.md # Pomodoro timer
|
||||
├── workflows/
|
||||
│ ├── daily-planning/ # Morning routine
|
||||
│ ├── weekly-review/ # Week retrospective
|
||||
│ └── project-setup/ # New project init
|
||||
└── config.yaml
|
||||
```
|
||||
|
||||
### Example 2: Content Creation
|
||||
|
||||
```
|
||||
content/
|
||||
├── agents/
|
||||
│ ├── writer.md # Blog/article writer
|
||||
│ ├── editor.md # Copy editor
|
||||
│ └── seo-optimizer.md # SEO specialist
|
||||
├── workflows/
|
||||
│ ├── blog-post/ # Full blog creation
|
||||
│ ├── social-media/ # Social content
|
||||
│ ├── email-campaign/ # Email sequence
|
||||
│ └── content-calendar/ # Planning
|
||||
└── templates/
|
||||
├── blog-template.md
|
||||
└── email-template.md
|
||||
```
|
||||
|
||||
### Example 3: DevOps Automation
|
||||
|
||||
```
|
||||
devops/
|
||||
├── agents/
|
||||
│ ├── deploy-master.md # Deployment orchestrator
|
||||
│ ├── monitor.md # System monitoring
|
||||
│ ├── incident-responder.md # Incident management
|
||||
│ └── infra-architect.md # Infrastructure design
|
||||
├── workflows/
|
||||
│ ├── ci-cd-setup/ # Pipeline creation
|
||||
│ ├── deploy-app/ # Application deployment
|
||||
│ ├── rollback/ # Emergency rollback
|
||||
│ ├── health-check/ # System verification
|
||||
│ └── incident-response/ # Incident handling
|
||||
├── tasks/
|
||||
│ ├── check-status.md # Quick status check
|
||||
│ └── notify-team.md # Team notifications
|
||||
└── data/
|
||||
└── runbooks/ # Operational guides
|
||||
```
|
||||
|
||||
## Module Evolution Pattern
|
||||
|
||||
```
|
||||
Simple Module → Standard Module → Complex Module → Module Suite
|
||||
(MVP) (Enhanced) (Complete) (Ecosystem)
|
||||
```
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
1. **Over-engineering**: Starting too complex
|
||||
2. **Under-planning**: No clear architecture
|
||||
3. **Poor boundaries**: Module does too much
|
||||
4. **Weak integration**: Components don't work together
|
||||
5. **Missing docs**: No clear usage guide
|
||||
|
||||
## Success Metrics
|
||||
|
||||
A well-designed module has:
|
||||
|
||||
- ✅ Clear, focused purpose
|
||||
- ✅ Cohesive components
|
||||
- ✅ Smooth installation
|
||||
- ✅ Comprehensive docs
|
||||
- ✅ Room for growth
|
||||
- ✅ Happy users!
|
||||
45
bmad/bmb/workflows/create-module/workflow.yaml
Normal file
45
bmad/bmb/workflows/create-module/workflow.yaml
Normal file
@@ -0,0 +1,45 @@
|
||||
# Build Module Workflow Configuration
|
||||
name: create-module
|
||||
description: "Interactive workflow to build complete BMAD modules with agents, workflows, tasks, and installation infrastructure"
|
||||
author: "BMad"
|
||||
|
||||
# Critical variables load from config_source
|
||||
config_source: "{project-root}/bmad/bmb/config.yaml"
|
||||
output_folder: "{config_source}:output_folder"
|
||||
src_impact: "{config_source}:src_impact"
|
||||
communication_language: "{config_source}:communication_language"
|
||||
user_name: "{config_source}:user_name"
|
||||
date: system-generated
|
||||
|
||||
# Reference guides for module building
|
||||
module_structure_guide: "{installed_path}/module-structure.md"
|
||||
installer_templates: "{installed_path}/installer-templates/"
|
||||
|
||||
# Use existing build workflows
|
||||
agent_builder: "{project-root}/bmad/bmb/workflows/create-agent/workflow.yaml"
|
||||
workflow_builder: "{project-root}/bmad/bmb/workflows/create-workflow/workflow.yaml"
|
||||
brainstorming_workflow: "{project-root}/bmad/cis/workflows/brainstorming/workflow.yaml"
|
||||
brainstorming_context: "{installed_path}/brainstorm-context.md"
|
||||
|
||||
# Optional docs that help understand module patterns
|
||||
recommended_inputs:
|
||||
- module_brief: "{output_folder}/module-brief-*.md"
|
||||
- brainstorming_results: "{output_folder}/brainstorming-*.md"
|
||||
- bmm_module: "{project-root}/bmad/bmm/"
|
||||
- cis_module: "{project-root}/bmad/cis/"
|
||||
- existing_agents: "{project-root}/bmad/*/agents/"
|
||||
- existing_workflows: "{project-root}/bmad/*/workflows/"
|
||||
|
||||
# Module path and component files
|
||||
installed_path: "{project-root}/bmad/bmb/workflows/create-module"
|
||||
template: false # This is an interactive scaffolding workflow
|
||||
instructions: "{installed_path}/instructions.md"
|
||||
validation: "{installed_path}/checklist.md"
|
||||
|
||||
# Output configuration - creates entire module structure
|
||||
# If src_impact=true: Save to src/modules/{{module_code}}
|
||||
# If src_impact=false: Save to output_folder/{{module_code}}
|
||||
default_output_folder: "{output_folder}/{{module_code}}"
|
||||
src_output_folder: "{project-root}/src/modules/{{module_code}}"
|
||||
installer_output_folder: "{output_folder}/{{module_code}}"
|
||||
src_installer_output_folder: "{project-root}/src/modules/{{module_code}}"
|
||||
Reference in New Issue
Block a user