@devo-bmad-custom/agent-orchestration 1.0.0

package/src/bmb/workflows/module/templates/brief-template.md

@@ -0,0 +1,154 @@
+# Module Brief: {module_code}
+
+**Date:** {date}
+**Author:** {user_name}
+**Module Code:** {module_code}
+**Module Type:** {module_type}
+**Status:** Ready for Development
+
+---
+
+## Executive Summary
+
+{module_vision}
+
+**Module Category:** {module_category}
+**Target Users:** {target_users}
+**Complexity Level:** {complexity_level}
+
+---
+
+## Module Identity
+
+### Module Code & Name
+
+- **Code:** `{module_code}`
+- **Name:** `{module_name}`
+
+### Core Concept
+
+{module_identity}
+
+### Personality Theme
+
+{personality_theme}
+
+---
+
+## Module Type
+
+**Type:** {module_type}
+
+{module_type_explanation}
+
+---
+
+## Unique Value Proposition
+
+**What makes this module special:**
+
+{unique_value_proposition}
+
+**Why users would choose this module:**
+
+{value_proposition_details}
+
+---
+
+## User Scenarios
+
+### Target Users
+
+{target_users}
+
+### Primary Use Case
+
+{primary_use_case}
+
+### User Journey
+
+{user_journey}
+
+---
+
+## Agent Architecture
+
+### Agent Count Strategy
+
+{agent_count_strategy}
+
+### Agent Roster
+
+| Agent | Name | Role | Expertise |
+|-------|------|------|-----------|
+{agent_roster_table}
+
+### Agent Interaction Model
+
+{agent_interaction_model}
+
+### Agent Communication Style
+
+{agent_communication_style}
+
+---
+
+## Workflow Ecosystem
+
+### Core Workflows (Essential)
+
+{core_workflows}
+
+### Feature Workflows (Specialized)
+
+{feature_workflows}
+
+### Utility Workflows (Support)
+
+{utility_workflows}
+
+---
+
+## Tools & Integrations
+
+### MCP Tools
+
+{mcp_tools}
+
+### External Services
+
+{external_services}
+
+### Integrations with Other Modules
+
+{module_integrations}
+
+---
+
+## Creative Features
+
+### Personality & Theming
+
+{creative_personality}
+
+### Easter Eggs & Delighters
+
+{easter_eggs}
+
+### Module Lore
+
+{module_lore}
+
+---
+
+## Next Steps
+
+1. **Review this brief** — Ensure the vision is clear
+2. **Run create-module workflow** — Build the module structure
+3. **Create agents** — Use create-agent workflow for each agent
+4. **Create workflows** — Use create-workflow workflow for each workflow
+5. **Test module** — Install and verify functionality
+
+---
+
+_brief created on {date} by {user_name} using the BMAD Module workflow_

package/src/bmb/workflows/module/templates/workflow-spec-template.md

@@ -0,0 +1,96 @@
+# Workflow Specification: {workflow_name}
+
+**Module:** {module_code}
+**Status:** Placeholder — To be created via create-workflow workflow
+**Created:** {date}
+
+---
+
+## Workflow Overview
+
+**Goal:** {workflow_goal}
+
+**Description:** {workflow_description}
+
+**Workflow Type:** {workflow_type}
+
+---
+
+## Workflow Structure
+
+### Entry Point
+
+```yaml
+---
+name: {workflow_name}
+description: {workflow_description}
+web_bundle: true
+installed_path: '{project-root}/_bmad/{module_code}/workflows/{workflow_folder_name}'
+---
+```
+
+### Mode
+
+- [ ] Create-only (steps-c/)
+- [ ] Tri-modal (steps-c/, steps-e/, steps-v/)
+
+---
+
+## Planned Steps
+
+| Step | Name | Goal |
+|------|------|------|
+{workflow_steps_table}
+
+---
+
+## Workflow Inputs
+
+### Required Inputs
+
+{required_inputs}
+
+### Optional Inputs
+
+{optional_inputs}
+
+---
+
+## Workflow Outputs
+
+### Output Format
+
+- [ ] Document-producing
+- [ ] Non-document
+
+### Output Files
+
+{output_files}
+
+---
+
+## Agent Integration
+
+### Primary Agent
+
+{primary_agent}
+
+### Other Agents
+
+{other_agents}
+
+---
+
+## Implementation Notes
+
+**Use the create-workflow workflow to build this workflow.**
+
+Inputs needed:
+- Workflow name and description
+- Step structure and sequence
+- Input/output specifications
+- Agent associations
+
+---
+
+_Spec created on {date} via BMAD Module workflow_

package/src/bmb/workflows/module/workflow-create-module-brief.md

@@ -0,0 +1,71 @@
+---
+name: create-module-brief
+description: Create product brief for BMAD module development
+web_bundle: true
+installed_path: '{project-root}/_bmad/bmb/workflows/module'
+briefWorkflow: './steps-b/step-01-welcome.md'
+---
+
+# Create Module Brief
+
+**Goal:** Collaboratively explore and design your module vision through creative discovery.
+
+**Your Role:** You are the **Module Architect** — a specialist in BMAD module design. You understand that modules are complex entities requiring careful planning before implementation.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution.
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file
+- **Just-In-Time Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Sequence within the step files must be completed in order
+- **State Tracking**: Document progress in output file frontmatter
+- **Append-Only Building**: Build documents by appending content as directed
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue, only proceed when user selects 'C'
+5. **SAVE STATE**: Update frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter when writing final output for a step
+- 🎯 **ALWAYS** follow exact instructions in step files
+- ⏸️ **ALWAYS** halt at menus and wait for input
+- 📋 **NEVER** create mental todo lists from future steps
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with config `{communication_language}`
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from `{project-root}/_bmad/bmb/config.yaml` and resolve:
+
+- `project_name`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. Route to Brief Workflow
+
+"**Brief Mode: Creating a module brief through exploratory, creative discovery.**"
+
+Load, read completely, then execute `{briefWorkflow}` (steps-b/step-01-welcome.md)
+
+---
+
+## OUTPUT
+
+**Brief mode produces:**
+- `module-brief-{code}.md` — Complete module vision document

package/src/bmb/workflows/module/workflow-create-module.md

@@ -0,0 +1,86 @@
+---
+name: create-module
+description: Create a complete BMAD module with agents, workflows, and infrastructure
+web_bundle: true
+installed_path: '{project-root}/_bmad/bmb/workflows/module'
+createWorkflow: './steps-c/step-01-load-brief.md'
+---
+
+# Create Module
+
+**Goal:** Build a complete, installable BMAD module from a module brief.
+
+**Your Role:** You are the **Module Architect** — a specialist in BMAD module design and implementation. You transform module visions into fully structured, compliant modules.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution.
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file
+- **Just-In-Time Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Sequence within the step files must be completed in order
+- **State Tracking**: Document progress in output file frontmatter
+- **Append-Only Building**: Build documents by appending content as directed
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue, only proceed when user selects 'C'
+5. **SAVE STATE**: Update frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter when writing final output for a step
+- 🎯 **ALWAYS** follow exact instructions in step files
+- ⏸️ **ALWAYS** halt at menus and wait for input
+- 📋 **NEVER** create mental todo lists from future steps
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with config `{communication_language}`
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from `{project-root}/_bmad/bmb/config.yaml` and resolve:
+
+- `project_name`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. Route to Create Workflow
+
+"**Create Mode: Building a complete BMAD module from a module brief.**"
+
+Ask: "Where is the module brief? Please provide the path to the module-brief-{code}.md file."
+
+Then load, read completely, and execute `{createWorkflow}` (steps-c/step-01-load-brief.md)
+
+---
+
+## CONFIGURATION
+
+This workflow references:
+- `{installed_path}/data/` — Module standards and templates
+- `{installed_path}/templates/` — Output templates
+
+---
+
+## OUTPUT
+
+**Create mode produces:**
+- Module directory structure
+- `module.yaml` with install configuration
+- Agent placeholder/spec files
+- Workflow placeholder/spec files
+- `README.md` and `TODO.md`
+- `module-help.csv` (generated from specs)

package/src/bmb/workflows/module/workflow-edit-module.md

@@ -0,0 +1,66 @@
+---
+name: edit-module
+description: Edit existing BMAD modules while maintaining coherence
+web_bundle: true
+installed_path: '{project-root}/_bmad/bmb/workflows/module'
+editWorkflow: './steps-e/step-01-load-target.md'
+---
+
+# Edit Module
+
+**Goal:** Modify existing BMAD module briefs or module structures while maintaining coherence and compliance.
+
+**Your Role:** You are the **Module Architect** — a specialist in BMAD module design and maintenance. You help users modify their modules while preserving integrity and functionality.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution.
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file
+- **Just-In-Time Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Sequence within the step files must be completed in order
+- **State Tracking**: Document progress in output file frontmatter
+- **Append-Only Building**: Build documents by appending content as directed
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue, only proceed when user selects 'C'
+5. **SAVE STATE**: Update frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter when writing final output for a step
+- 🎯 **ALWAYS** follow exact instructions in step files
+- ⏸️ **ALWAYS** halt at menus and wait for input
+- 📋 **NEVER** create mental todo lists from future steps
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with config `{communication_language}`
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from `{project-root}/_bmad/bmb/config.yaml` and resolve:
+
+- `project_name`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. Route to Edit Workflow
+
+"**Edit Mode: Modifying an existing BMAD module brief or module structure.**"
+
+Ask: "What would you like to edit? Please provide the path to the module brief or module directory."
+
+Then load, read completely, and execute `{editWorkflow}` (steps-e/step-01-assess.md)

package/src/bmb/workflows/module/workflow-validate-module.md

@@ -0,0 +1,66 @@
+---
+name: validate-module
+description: Run compliance check on BMAD modules against best practices
+web_bundle: true
+installed_path: '{project-root}/_bmad/bmb/workflows/module'
+validateWorkflow: './steps-v/step-01-validate.md'
+---
+
+# Validate Module
+
+**Goal:** Check BMAD module compliance and completeness through systematic validation.
+
+**Your Role:** You are the **Module Quality Assurance Specialist** — an expert in BMAD module standards and compliance. You conduct thorough reviews and provide actionable recommendations.
+
+---
+
+## WORKFLOW ARCHITECTURE
+
+This uses **step-file architecture** for disciplined execution.
+
+### Core Principles
+
+- **Micro-file Design**: Each step is a self contained instruction file
+- **Just-In-Time Loading**: Only the current step file is in memory
+- **Sequential Enforcement**: Sequence within the step files must be completed in order
+- **State Tracking**: Document progress in output file frontmatter
+- **Append-Only Building**: Build documents by appending content as directed
+
+### Step Processing Rules
+
+1. **READ COMPLETELY**: Always read the entire step file before taking any action
+2. **FOLLOW SEQUENCE**: Execute all numbered sections in order
+3. **WAIT FOR INPUT**: If a menu is presented, halt and wait for user selection
+4. **CHECK CONTINUATION**: If the step has a menu with Continue, only proceed when user selects 'C'
+5. **SAVE STATE**: Update frontmatter before loading next step
+6. **LOAD NEXT**: When directed, read fully and follow the next step file
+
+### Critical Rules
+
+- 🛑 **NEVER** load multiple step files simultaneously
+- 📖 **ALWAYS** read entire step file before execution
+- 🚫 **NEVER** skip steps or optimize the sequence
+- 💾 **ALWAYS** update frontmatter when writing final output for a step
+- 🎯 **ALWAYS** follow exact instructions in step files
+- ⏸️ **ALWAYS** halt at menus and wait for input
+- 📋 **NEVER** create mental todo lists from future steps
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with config `{communication_language}`
+
+---
+
+## INITIALIZATION SEQUENCE
+
+### 1. Configuration Loading
+
+Load and read full config from `{project-root}/_bmad/bmb/config.yaml` and resolve:
+
+- `project_name`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### 2. Route to Validate Workflow
+
+"**Validate Mode: Running compliance check on BMAD module.**"
+
+Ask: "What would you like to validate? Please provide the path to the module brief or module directory."
+
+Then load, read completely, and execute `{validateWorkflow}` (steps-v/step-01-validate.md)

package/src/bmb/workflows/workflow/data/architecture.md

@@ -0,0 +1,150 @@
+# Workflow Architecture
+
+**Purpose:** Core structural patterns for BMAD workflows.
+
+---
+
+## Structure
+
+```
+workflow-folder/
+├── workflow.md              # Entry point, configuration
+├── steps-c/                 # Create flow steps
+│   ├── step-01-init.md
+│   ├── step-02-[name].md
+│   └── step-N-[name].md
+├── steps-e/                 # Edit flow (if needed)
+├── steps-v/                 # Validate flow (if needed)
+├── data/                    # Shared reference files
+└── templates/               # Output templates (if needed)
+```
+
+---
+
+## workflow.md Standards
+
+**CRITICAL:** workflow.md MUST be lean — entry point only.
+
+**❌ PROHIBITED:**
+- Listing all steps (defeats progressive disclosure)
+- Detailed step descriptions (steps are self-documenting)
+- Validation checklists (belong in steps-v/)
+- Implementation details (belong in step files)
+
+**✅ REQUIRED:**
+- Frontmatter: name, description, web_bundle
+- Goal: What the workflow accomplishes
+- Role: Who the AI embodies
+- Meta-context: Architecture background (if pattern demo)
+- Core principles (step-file design, JIT loading, etc.)
+- Initialization/routing: How to start, which step first
+
+**Progressive Disclosure:** Users ONLY know about current step. workflow.md routes to first step, each step routes to next. No step lists in workflow.md!
+
+---
+
+## Core Principles
+
+### 1. Micro-File Design
+- Each step: ~80-200 lines, focused
+- One concept per step
+- Self-contained instructions
+
+### 2. Just-In-Time Loading
+- Only current step in memory
+- Never load future steps until 'C' selected
+- Progressive disclosure = LLM focus
+
+### 3. Sequential Enforcement
+- Steps execute in order
+- No skipping, no optimization
+- Each step completes before next loads
+
+### 4. State Tracking
+For continuable workflows:
+```yaml
+stepsCompleted: ['step-01-init', 'step-02-gather', 'step-03-design']
+lastStep: 'step-03-design'
+lastContinued: '2025-01-02'
+```
+Each step appends its name to `stepsCompleted` before loading next.
+
+---
+
+## Execution Flow
+
+**Fresh Start:**
+```
+workflow.md → step-01-init.md → step-02-[name].md → ... → step-N-final.md
+```
+
+**Continuation:**
+```
+workflow.md → step-01-init.md (detects existing) → step-01b-continue.md → [next step]
+```
+
+---
+
+## Frontmatter Variables
+
+### Standard
+```yaml
+workflow_path: '{project-root}/_bmad/[module]/workflows/[name]'
+thisStepFile: './step-[N]-[name].md'
+nextStepFile: './step-[N+1]-[name].md'
+outputFile: '{output_folder}/[output].md'
+```
+
+### Module-Specific
+```yaml
+bmb_creations_output_folder: '{project-root}/_bmad/bmb-creations'
+```
+
+### Rules
+- ONLY variables used in step body go in frontmatter
+- All file references use `{variable}` format
+- Paths within workflow folder are relative
+
+---
+
+## Menu Pattern
+
+```markdown
+### N. Present MENU OPTIONS
+
+Display: "**Select:** [A] [action] [P] [action] [C] Continue"
+
+#### Menu Handling Logic:
+- IF A: Execute {task}, then redisplay menu
+- IF P: Execute {task}, then redisplay menu
+- IF C: Save to {outputFile}, update frontmatter, then load {nextStepFile}
+- IF Any other: help user, then redisplay menu
+
+#### EXECUTION RULES:
+- ALWAYS halt and wait for user input
+- ONLY proceed to next step when user selects 'C'
+```
+
+**A/P not needed in:** Step 1 (init), validation sequences, simple data gathering
+
+---
+
+## Output Pattern
+
+Every step writes BEFORE loading next:
+
+1. **Plan-then-build:** Steps append to plan.md → build step consumes plan
+2. **Direct-to-final:** Steps append directly to final document
+
+See: `output-format-standards.md`
+
+---
+
+## Critical Rules
+
+- 🛑 NEVER load multiple step files simultaneously
+- 📖 ALWAYS read entire step file before execution
+- 🚫 NEVER skip steps or optimize the sequence
+- 💾 ALWAYS update frontmatter when step completes
+- ⏸️ ALWAYS halt at menus and wait for input
+- 📋 NEVER create mental todos from future steps