@devo-bmad-custom/agent-orchestration 1.0.2 → 1.0.4

package/src/bmb/workflows/module/steps-v/step-02-file-structure.md

@@ -1,93 +1,93 @@
----
-name: 'step-02-file-structure'
-description: 'Validate file structure compliance'
-
-nextStepFile: './step-03-module-yaml.md'
-moduleStandardsFile: '../data/module-standards.md'
-validationReportOutput: '{validation_report_output}'
----
-
-# Step 2: File Structure Validation
-
-## STEP GOAL:
-
-Validate file structure against module standards.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — checking structure
-- ✅ Reference standards, ensure compliance
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Standards
-
-Load `{moduleStandardsFile}` for reference.
-
-### 2. Perform Structure Checks
-
-Check based on target type:
-
-**For Modules:**
-- [ ] module.yaml exists
-- [ ] README.md exists
-- [ ] agents/ folder exists (if agents specified)
-- [ ] workflows/ folder exists (if workflows specified)
-
-**For Briefs:**
-- [ ] Brief file exists
-- [ ] Required sections present
-
-**For Agent Specs:**
-- [ ] All expected spec files exist
-
-**For Workflow Specs:**
-- [ ] All expected spec files exist
-
-### 3. Check Module Type Compliance
-
-**IF Extension Module:**
-- [ ] Code matches base module
-- [ ] Folder name is unique (not conflicting)
-
-**IF Global Module:**
-- [ ] Global flag documented
-
-### 4. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## File Structure Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Checks:**
-{list each check with result}
-
-**Issues Found:**
-{any structural problems}
-```
-
-### 5. Auto-Proceed
-
-"**✓ File structure check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All structure checks performed
-✅ Results recorded
-✅ Auto-proceeds to next validation
+---
+name: 'step-02-file-structure'
+description: 'Validate file structure compliance'
+
+nextStepFile: './step-03-module-yaml.md'
+moduleStandardsFile: '../data/module-standards.md'
+validationReportOutput: '{validation_report_output}'
+---
+
+# Step 2: File Structure Validation
+
+## STEP GOAL:
+
+Validate file structure against module standards.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 📖 CRITICAL: Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Quality Assurance** — checking structure
+- ✅ Reference standards, ensure compliance
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Standards
+
+Load `{moduleStandardsFile}` for reference.
+
+### 2. Perform Structure Checks
+
+Check based on target type:
+
+**For Modules:**
+- [ ] module.yaml exists
+- [ ] README.md exists
+- [ ] agents/ folder exists (if agents specified)
+- [ ] workflows/ folder exists (if workflows specified)
+
+**For Briefs:**
+- [ ] Brief file exists
+- [ ] Required sections present
+
+**For Agent Specs:**
+- [ ] All expected spec files exist
+
+**For Workflow Specs:**
+- [ ] All expected spec files exist
+
+### 3. Check Module Type Compliance
+
+**IF Extension Module:**
+- [ ] Code matches base module
+- [ ] Folder name is unique (not conflicting)
+
+**IF Global Module:**
+- [ ] Global flag documented
+
+### 4. Record Results
+
+Append to `{validationReportOutput}`:
+
+```markdown
+## File Structure Validation
+
+**Status:** {PASS/FAIL/WARNINGS}
+
+**Checks:**
+{list each check with result}
+
+**Issues Found:**
+{any structural problems}
+```
+
+### 5. Auto-Proceed
+
+"**✓ File structure check complete.**"
+
+Proceeding to next validation...
+
+Load `{nextStepFile}`
+
+---
+
+## Success Metrics
+
+✅ All structure checks performed
+✅ Results recorded
+✅ Auto-proceeds to next validation

package/src/bmb/workflows/module/steps-v/step-03-module-yaml.md

@@ -1,99 +1,99 @@
----
-name: 'step-03-module-yaml'
-description: 'Validate module.yaml against conventions'
-
-nextStepFile: './step-04-agent-specs.md'
-moduleYamlConventionsFile: '../data/module-yaml-conventions.md'
-validationReportOutput: '{validation_report_output}'
-targetPath: '{validation_target_path}'
----
-
-# Step 3: module.yaml Validation
-
-## STEP GOAL:
-
-Validate module.yaml formatting and conventions.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — checking configuration
-- ✅ Ensure proper YAML syntax
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load module.yaml
-
-Read `{targetPath}/module.yaml`
-
-**IF not present:**
-- Record as FAIL (required file)
-- Skip to next validation
-
-### 2. Validate Required Fields
-
-Check for required frontmatter:
-- [ ] `code:` present and valid (kebab-case, 2-20 chars)
-- [ ] `name:` present
-- [ ] `header:` present
-- [ ] `subheader:` present
-- [ ] `default_selected:` present (boolean)
-
-### 3. Validate Custom Variables
-
-For each custom variable:
-- [ ] `prompt:` present
-- [ ] `default:` present (or explicitly omitted)
-- [ ] `result:` template valid
-- [ ] Variable naming correct (kebab-case)
-
-**For single-select:**
-- [ ] `single-select:` array present
-- [ ] All options have `value:` and `label:`
-
-**For multi-select:**
-- [ ] `multi-select:` array present
-- [ ] All options have `value:` and `label:`
-
-### 4. Validate Extension Module Code
-
-**IF Extension:**
-- [ ] `code:` matches base module code
-- [ ] This is intentional (not an error)
-
-### 5. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## module.yaml Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Required Fields:** {status}
-**Custom Variables:** {count} variables
-**Issues Found:**
-{list any issues}
-```
-
-### 6. Auto-Proceed
-
-"**✓ module.yaml check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All module.yaml checks performed
-✅ Results recorded
-✅ Auto-proceeds to next validation
+---
+name: 'step-03-module-yaml'
+description: 'Validate module.yaml against conventions'
+
+nextStepFile: './step-04-agent-specs.md'
+moduleYamlConventionsFile: '../data/module-yaml-conventions.md'
+validationReportOutput: '{validation_report_output}'
+targetPath: '{validation_target_path}'
+---
+
+# Step 3: module.yaml Validation
+
+## STEP GOAL:
+
+Validate module.yaml formatting and conventions.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 📖 CRITICAL: Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Quality Assurance** — checking configuration
+- ✅ Ensure proper YAML syntax
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load module.yaml
+
+Read `{targetPath}/module.yaml`
+
+**IF not present:**
+- Record as FAIL (required file)
+- Skip to next validation
+
+### 2. Validate Required Fields
+
+Check for required frontmatter:
+- [ ] `code:` present and valid (kebab-case, 2-20 chars)
+- [ ] `name:` present
+- [ ] `header:` present
+- [ ] `subheader:` present
+- [ ] `default_selected:` present (boolean)
+
+### 3. Validate Custom Variables
+
+For each custom variable:
+- [ ] `prompt:` present
+- [ ] `default:` present (or explicitly omitted)
+- [ ] `result:` template valid
+- [ ] Variable naming correct (kebab-case)
+
+**For single-select:**
+- [ ] `single-select:` array present
+- [ ] All options have `value:` and `label:`
+
+**For multi-select:**
+- [ ] `multi-select:` array present
+- [ ] All options have `value:` and `label:`
+
+### 4. Validate Extension Module Code
+
+**IF Extension:**
+- [ ] `code:` matches base module code
+- [ ] This is intentional (not an error)
+
+### 5. Record Results
+
+Append to `{validationReportOutput}`:
+
+```markdown
+## module.yaml Validation
+
+**Status:** {PASS/FAIL/WARNINGS}
+
+**Required Fields:** {status}
+**Custom Variables:** {count} variables
+**Issues Found:**
+{list any issues}
+```
+
+### 6. Auto-Proceed
+
+"**✓ module.yaml check complete.**"
+
+Proceeding to next validation...
+
+Load `{nextStepFile}`
+
+---
+
+## Success Metrics
+
+✅ All module.yaml checks performed
+✅ Results recorded
+✅ Auto-proceeds to next validation

package/src/bmb/workflows/module/steps-v/step-04-agent-specs.md

@@ -1,152 +1,152 @@
----
-name: 'step-04-agent-specs'
-description: 'Validate agent specifications and built agents'
-
-nextStepFile: './step-05-workflow-specs.md'
-agentSpecTemplate: '../data/agent-spec-template.md'
-agentArchitectureFile: '../data/agent-architecture.md'
-agentValidationWorkflow: '{project-root}/_bmad/bmb/workflows/agent/steps-v/step-01-validate.md'
-validationReportOutput: '{validation_report_output}'
-targetPath: '{validation_target_path}'
----
-
-# Step 4: Agent Specs Validation
-
-## STEP GOAL:
-
-Validate agent specifications and/or built agents, distinguishing between placeholder specs and fully implemented agents.
-
-## MANDATORY EXECUTION RULES:
-
-### Universal Rules:
-- 📖 CRITICAL: Read the complete step file before taking any action
-- ✅ Speak in `{communication_language}`
-
-### Role Reinforcement:
-- ✅ You are the **Quality Assurance** — dual-mode checking
-- ✅ Specs are expected, built agents are great
-- ✅ Track status of each agent
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Agent Files
-
-Find all agent files in `{targetPath}/agents/`:
-- `.spec.md` files (placeholder specs)
-- `.agent.yaml` files (built agents)
-
-### 2. Categorize Agents
-
-For each agent found, determine status:
-
-**Built Agents (.agent.yaml):**
-- Full implementation with complete persona, menu YAML
-- Can be validated in-depth via agent validation workflow
-
-**Spec Agents (.spec.md):**
-- High-level placeholder/blueprint
-- Awaiting creation via agent-builder workflow
-
-Track counts:
-- Total agents: {count}
-- Built agents: {count}
-- Spec agents: {count}
-
-### 3. Validate Spec Agents (.spec.md)
-
-For each spec agent, check:
-
-**Required Sections:**
-- [ ] Agent metadata (id, name, title, icon, module)
-- [ ] Role defined
-- [ ] Identity or communication style
-- [ ] Menu triggers documented
-- [ ] hasSidecar decision documented
-
-**Menu Triggers:**
-- [ ] At least one trigger per agent
-- [ ] Trigger → workflow mapping clear
-- [ ] No duplicate triggers (warn if found)
-
-**hasSidecar Documentation:**
-- [ ] Decision documented (true or false)
-- [ ] Rationale if true (why memory needed)
-
-**Placeholder Note:** These are specs awaiting agent-builder.
-
-### 4. Validate Built Agents (.agent.yaml)
-
-For each built agent, check:
-
-**Frontmatter Completeness:**
-- [ ] agent.metadata exists
-- [ ] agent.persona exists
-- [ ] agent.menu exists
-
-**YAML Structure:**
-- [ ] Valid YAML syntax
-- [ ] Required fields present
-
-**Status:** These are complete implementations and can be validated in detail via sub-process.
-
-### 5. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## Agent Specs Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Agent Summary:**
-- Total Agents: {count}
-- Built Agents: {count} {list}
-- Spec Agents: {count} {list}
-
-**Built Agents:**
-{for each built agent}
-- **{name}**: {status} - Ready for detailed validation via agent workflow
-
-**Spec Agents:**
-{for each spec agent}
-- **{name}**: {status} - Placeholder awaiting agent-builder
-
-**Issues Found:**
-{list any issues}
-
-**Recommendations:**
-{if specs exist}
-- Use `bmad:bmb:agents:agent-builder` to create {spec agent names}
-- After building agents, re-run validation to verify compliance
-{endif}
-```
-
-### 6. Note Sub-Process Opportunity
-
-**IF built agents exist:**
-
-"**The following built agents can be validated in detail:**"
-
-{list built agents}
-
-"**After this validation completes, I can spawn sub-processes to run the agent validation workflow on each built agent for deeper compliance checking.**"
-
-### 7. Auto-Proceed
-
-"**✓ Agent specs check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All agent files checked
-✅ Status tracked (spec vs built)
-✅ hasSidecar decisions validated
-✅ Recommendations for specs documented
-✅ Sub-process opportunity noted
+---
+name: 'step-04-agent-specs'
+description: 'Validate agent specifications and built agents'
+
+nextStepFile: './step-05-workflow-specs.md'
+agentSpecTemplate: '../data/agent-spec-template.md'
+agentArchitectureFile: '../data/agent-architecture.md'
+agentValidationWorkflow: '{project-root}/_bmad/bmb/workflows/agent/steps-v/step-01-validate.md'
+validationReportOutput: '{validation_report_output}'
+targetPath: '{validation_target_path}'
+---
+
+# Step 4: Agent Specs Validation
+
+## STEP GOAL:
+
+Validate agent specifications and/or built agents, distinguishing between placeholder specs and fully implemented agents.
+
+## MANDATORY EXECUTION RULES:
+
+### Universal Rules:
+- 📖 CRITICAL: Read the complete step file before taking any action
+- ✅ Speak in `{communication_language}`
+
+### Role Reinforcement:
+- ✅ You are the **Quality Assurance** — dual-mode checking
+- ✅ Specs are expected, built agents are great
+- ✅ Track status of each agent
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Agent Files
+
+Find all agent files in `{targetPath}/agents/`:
+- `.spec.md` files (placeholder specs)
+- `.agent.yaml` files (built agents)
+
+### 2. Categorize Agents
+
+For each agent found, determine status:
+
+**Built Agents (.agent.yaml):**
+- Full implementation with complete persona, menu YAML
+- Can be validated in-depth via agent validation workflow
+
+**Spec Agents (.spec.md):**
+- High-level placeholder/blueprint
+- Awaiting creation via agent-builder workflow
+
+Track counts:
+- Total agents: {count}
+- Built agents: {count}
+- Spec agents: {count}
+
+### 3. Validate Spec Agents (.spec.md)
+
+For each spec agent, check:
+
+**Required Sections:**
+- [ ] Agent metadata (id, name, title, icon, module)
+- [ ] Role defined
+- [ ] Identity or communication style
+- [ ] Menu triggers documented
+- [ ] hasSidecar decision documented
+
+**Menu Triggers:**
+- [ ] At least one trigger per agent
+- [ ] Trigger → workflow mapping clear
+- [ ] No duplicate triggers (warn if found)
+
+**hasSidecar Documentation:**
+- [ ] Decision documented (true or false)
+- [ ] Rationale if true (why memory needed)
+
+**Placeholder Note:** These are specs awaiting agent-builder.
+
+### 4. Validate Built Agents (.agent.yaml)
+
+For each built agent, check:
+
+**Frontmatter Completeness:**
+- [ ] agent.metadata exists
+- [ ] agent.persona exists
+- [ ] agent.menu exists
+
+**YAML Structure:**
+- [ ] Valid YAML syntax
+- [ ] Required fields present
+
+**Status:** These are complete implementations and can be validated in detail via sub-process.
+
+### 5. Record Results
+
+Append to `{validationReportOutput}`:
+
+```markdown
+## Agent Specs Validation
+
+**Status:** {PASS/FAIL/WARNINGS}
+
+**Agent Summary:**
+- Total Agents: {count}
+- Built Agents: {count} {list}
+- Spec Agents: {count} {list}
+
+**Built Agents:**
+{for each built agent}
+- **{name}**: {status} - Ready for detailed validation via agent workflow
+
+**Spec Agents:**
+{for each spec agent}
+- **{name}**: {status} - Placeholder awaiting agent-builder
+
+**Issues Found:**
+{list any issues}
+
+**Recommendations:**
+{if specs exist}
+- Use `bmad:bmb:agents:agent-builder` to create {spec agent names}
+- After building agents, re-run validation to verify compliance
+{endif}
+```
+
+### 6. Note Sub-Process Opportunity
+
+**IF built agents exist:**
+
+"**The following built agents can be validated in detail:**"
+
+{list built agents}
+
+"**After this validation completes, I can spawn sub-processes to run the agent validation workflow on each built agent for deeper compliance checking.**"
+
+### 7. Auto-Proceed
+
+"**✓ Agent specs check complete.**"
+
+Proceeding to next validation...
+
+Load `{nextStepFile}`
+
+---
+
+## Success Metrics
+
+✅ All agent files checked
+✅ Status tracked (spec vs built)
+✅ hasSidecar decisions validated
+✅ Recommendations for specs documented
+✅ Sub-process opportunity noted