@devo-bmad-custom/agent-orchestration 1.0.1 → 1.0.3

package/src/bmb/workflows/module/steps-v/step-05-workflow-specs.md

@@ -1,152 +1,152 @@
----
-name: 'step-05-workflow-specs'
-description: 'Validate workflow specifications and built workflows'
-
-nextStepFile: './step-06-documentation.md'
-workflowSpecTemplate: '../templates/workflow-spec-template.md'
-workflowValidationWorkflow: '{project-root}/_bmad/bmb/workflows/workflow/steps-v/step-01-validate.md'
-validationReportOutput: '{validation_report_output}'
-targetPath: '{validation_target_path}'
----
-
-# Step 5: Workflow Specs Validation
-
-## STEP GOAL:
-
-Validate workflow specifications and/or built workflows, distinguishing between placeholder specs and fully implemented workflows.
-
-## 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 workflows are great
-- ✅ Track status of each workflow
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Workflow Files
-
-Find all workflow files in `{targetPath}/workflows/`:
-- `.spec.md` files (placeholder specs)
-- `workflow.md` files (built workflows)
-
-### 2. Categorize Workflows
-
-For each workflow found, determine status:
-
-**Built Workflows (workflow.md with steps/ folder):**
-- Full implementation with step files, data, templates
-- Can be validated in-depth via workflow validation workflow
-
-**Spec Workflows (.spec.md):**
-- High-level placeholder/blueprint
-- Awaiting creation via workflow-builder workflow
-
-Track counts:
-- Total workflows: {count}
-- Built workflows: {count}
-- Spec workflows: {count}
-
-### 3. Validate Spec Workflows (.spec.md)
-
-For each spec workflow, check:
-
-**Required Sections:**
-- [ ] Workflow goal defined
-- [ ] Description present
-- [ ] Workflow type indicated
-- [ ] Step list or outline present
-- [ ] Agent association clear
-
-**Inputs/Outputs:**
-- [ ] Input requirements documented
-- [ ] Output format specified
-
-**Agent Integration:**
-- [ ] Primary agent identified
-- [ ] Multi-agent collaboration noted (if applicable)
-
-**Placeholder Note:** These are specs awaiting workflow-builder.
-
-### 4. Validate Built Workflows (workflow.md)
-
-For each built workflow, check:
-
-**Workflow Structure:**
-- [ ] workflow.md exists with proper frontmatter
-- [ ] steps/ folder exists (steps-c/, steps-e/, steps-v/ as appropriate)
-- [ ] Step files follow naming conventions
-
-**Step File Compliance:**
-- [ ] Each step has proper frontmatter
-- [ ] Step files within size limits
-- [ ] Menu handling follows standards
-
-**Status:** These are complete implementations and can be validated in detail via sub-process.
-
-### 5. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## Workflow Specs Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Workflow Summary:**
-- Total Workflows: {count}
-- Built Workflows: {count} {list}
-- Spec Workflows: {count} {list}
-
-**Built Workflows:**
-{for each built workflow}
-- **{name}**: {status} - Ready for detailed validation via workflow workflow
-
-**Spec Workflows:**
-{for each spec workflow}
-- **{name}**: {status} - Placeholder awaiting workflow-builder
-
-**Issues Found:**
-{list any issues}
-
-**Recommendations:**
-{if specs exist}
-- Use `bmad:bmb:workflows:workflow` or `/workflow` to create {spec workflow names}
-- After building workflows, re-run validation to verify compliance
-{endif}
-```
-
-### 6. Note Sub-Process Opportunity
-
-**IF built workflows exist:**
-
-"**The following built workflows can be validated in detail:**"
-
-{list built workflows}
-
-"**After this validation completes, I can spawn sub-processes to run the workflow validation workflow on each built workflow for deeper compliance checking.**"
-
-### 7. Auto-Proceed
-
-"**✓ Workflow specs check complete.**"
-
-Proceeding to next validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All workflow files checked
-✅ Status tracked (spec vs built)
-✅ Agent associations validated
-✅ Recommendations for specs documented
-✅ Sub-process opportunity noted
+---
+name: 'step-05-workflow-specs'
+description: 'Validate workflow specifications and built workflows'
+
+nextStepFile: './step-06-documentation.md'
+workflowSpecTemplate: '../templates/workflow-spec-template.md'
+workflowValidationWorkflow: '{project-root}/_bmad/bmb/workflows/workflow/steps-v/step-01-validate.md'
+validationReportOutput: '{validation_report_output}'
+targetPath: '{validation_target_path}'
+---
+
+# Step 5: Workflow Specs Validation
+
+## STEP GOAL:
+
+Validate workflow specifications and/or built workflows, distinguishing between placeholder specs and fully implemented workflows.
+
+## 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 workflows are great
+- ✅ Track status of each workflow
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Workflow Files
+
+Find all workflow files in `{targetPath}/workflows/`:
+- `.spec.md` files (placeholder specs)
+- `workflow.md` files (built workflows)
+
+### 2. Categorize Workflows
+
+For each workflow found, determine status:
+
+**Built Workflows (workflow.md with steps/ folder):**
+- Full implementation with step files, data, templates
+- Can be validated in-depth via workflow validation workflow
+
+**Spec Workflows (.spec.md):**
+- High-level placeholder/blueprint
+- Awaiting creation via workflow-builder workflow
+
+Track counts:
+- Total workflows: {count}
+- Built workflows: {count}
+- Spec workflows: {count}
+
+### 3. Validate Spec Workflows (.spec.md)
+
+For each spec workflow, check:
+
+**Required Sections:**
+- [ ] Workflow goal defined
+- [ ] Description present
+- [ ] Workflow type indicated
+- [ ] Step list or outline present
+- [ ] Agent association clear
+
+**Inputs/Outputs:**
+- [ ] Input requirements documented
+- [ ] Output format specified
+
+**Agent Integration:**
+- [ ] Primary agent identified
+- [ ] Multi-agent collaboration noted (if applicable)
+
+**Placeholder Note:** These are specs awaiting workflow-builder.
+
+### 4. Validate Built Workflows (workflow.md)
+
+For each built workflow, check:
+
+**Workflow Structure:**
+- [ ] workflow.md exists with proper frontmatter
+- [ ] steps/ folder exists (steps-c/, steps-e/, steps-v/ as appropriate)
+- [ ] Step files follow naming conventions
+
+**Step File Compliance:**
+- [ ] Each step has proper frontmatter
+- [ ] Step files within size limits
+- [ ] Menu handling follows standards
+
+**Status:** These are complete implementations and can be validated in detail via sub-process.
+
+### 5. Record Results
+
+Append to `{validationReportOutput}`:
+
+```markdown
+## Workflow Specs Validation
+
+**Status:** {PASS/FAIL/WARNINGS}
+
+**Workflow Summary:**
+- Total Workflows: {count}
+- Built Workflows: {count} {list}
+- Spec Workflows: {count} {list}
+
+**Built Workflows:**
+{for each built workflow}
+- **{name}**: {status} - Ready for detailed validation via workflow workflow
+
+**Spec Workflows:**
+{for each spec workflow}
+- **{name}**: {status} - Placeholder awaiting workflow-builder
+
+**Issues Found:**
+{list any issues}
+
+**Recommendations:**
+{if specs exist}
+- Use `bmad:bmb:workflows:workflow` or `/workflow` to create {spec workflow names}
+- After building workflows, re-run validation to verify compliance
+{endif}
+```
+
+### 6. Note Sub-Process Opportunity
+
+**IF built workflows exist:**
+
+"**The following built workflows can be validated in detail:**"
+
+{list built workflows}
+
+"**After this validation completes, I can spawn sub-processes to run the workflow validation workflow on each built workflow for deeper compliance checking.**"
+
+### 7. Auto-Proceed
+
+"**✓ Workflow specs check complete.**"
+
+Proceeding to next validation...
+
+Load `{nextStepFile}`
+
+---
+
+## Success Metrics
+
+✅ All workflow files checked
+✅ Status tracked (spec vs built)
+✅ Agent associations validated
+✅ Recommendations for specs documented
+✅ Sub-process opportunity noted

package/src/bmb/workflows/module/steps-v/step-06-documentation.md

@@ -1,143 +1,143 @@
----
-name: 'step-06-documentation'
-description: 'Validate documentation (README.md, TODO.md, docs/)'
-
-nextStepFile: './step-07-installation.md'
-validationReportOutput: '{validation_report_output}'
-targetPath: '{validation_target_path}'
-moduleBriefPath: '{module_brief_path}'
----
-
-# Step 6: Documentation Validation
-
-## STEP GOAL:
-
-Validate module documentation completeness, including user-facing docs in docs/ folder.
-
-## 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 docs
-- ✅ Documentation matters for usability
-- ✅ User docs can be generated from placeholder plans
-
----
-
-## MANDATORY SEQUENCE
-
-### 1. Load Documentation Files
-
-Check for:
-- `{targetPath}/README.md` (module overview)
-- `{targetPath}/TODO.md` (development roadmap)
-- `{targetPath}/docs/` (user documentation folder)
-
-### 2. Validate README.md
-
-**Required Sections:**
-- [ ] Module name and description
-- [ ] Installation instructions
-- [ ] Components section (agents, workflows)
-- [ ] Usage examples or quick start
-- [ ] Module structure
-- [ ] Link to docs/ folder
-
-**Quality Checks:**
-- [ ] Clear description of what module does
-- [ ] Installation command shown
-- [ ] Agent/workflow lists complete
-- [ ] References user documentation
-
-### 3. Validate TODO.md
-
-**Required Content:**
-- [ ] Agent build checklist
-- [ ] Workflow build checklist
-- [ ] Testing section
-- [ ] Next steps
-
-### 4. Validate docs/ Folder
-
-**For Custom Modules:**
-- [ ] docs/ folder exists
-- [ ] Contains user-facing documentation
-- [ ] Documentation is clear and helpful
-
-**Valid docs/ Contents (may include):**
-- `getting-started.md` — Quick start guide
-- `agents.md` — Agent documentation
-- `workflows.md` — Workflow documentation
-- `examples.md` — Usage examples
-- `configuration.md` — Setup/configuration guide
-- `troubleshooting.md` — Common issues and solutions
-
-**Quality Check:**
-- [ ] Even with placeholder agent/workflow specs, user docs should provide useful information
-- [ ] Documentation references agents/workflows by name
-- [ ] Clear what functionality exists vs what is planned
-
-### 5. Generate User Docs Recommendation
-
-**IF docs/ missing or incomplete:**
-
-"**User documentation can be generated from module brief and agent/workflow specs.**"
-
-"**Even with placeholder plans, you can create helpful user documentation that describes:**
-- What each agent does and when to use it
-- What workflows are available and their purpose
-- How to get started with the module
-- Configuration options (from module.yaml)"
-
-### 6. Record Results
-
-Append to `{validationReportOutput}`:
-
-```markdown
-## Documentation Validation
-
-**Status:** {PASS/FAIL/WARNINGS}
-
-**Root Documentation:**
-- **README.md:** {present/missing} - {status}
-- **TODO.md:** {present/missing} - {status}
-
-**User Documentation (docs/):**
-- **docs/ folder:** {present/missing} - {status}
-- **Documentation files:** {count} files found
-
-**Docs Contents:**
-{list files in docs/ folder}
-
-**Issues Found:**
-{list any issues}
-
-**Recommendations:**
-{if docs/ missing or incomplete}
-- Generate user documentation from module brief and specs
-- Create getting-started.md, agents.md, workflows.md
-- User docs are valuable even with placeholder plans
-{endif}
-```
-
-### 7. Auto-Proceed
-
-"**✓ Documentation check complete.**"
-
-Proceeding to installation validation...
-
-Load `{nextStepFile}`
-
----
-
-## Success Metrics
-
-✅ All documentation checked
-✅ Required sections validated
-✅ docs/ folder presence verified
-✅ User documentation quality assessed
-✅ Recommendations documented
+---
+name: 'step-06-documentation'
+description: 'Validate documentation (README.md, TODO.md, docs/)'
+
+nextStepFile: './step-07-installation.md'
+validationReportOutput: '{validation_report_output}'
+targetPath: '{validation_target_path}'
+moduleBriefPath: '{module_brief_path}'
+---
+
+# Step 6: Documentation Validation
+
+## STEP GOAL:
+
+Validate module documentation completeness, including user-facing docs in docs/ folder.
+
+## 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 docs
+- ✅ Documentation matters for usability
+- ✅ User docs can be generated from placeholder plans
+
+---
+
+## MANDATORY SEQUENCE
+
+### 1. Load Documentation Files
+
+Check for:
+- `{targetPath}/README.md` (module overview)
+- `{targetPath}/TODO.md` (development roadmap)
+- `{targetPath}/docs/` (user documentation folder)
+
+### 2. Validate README.md
+
+**Required Sections:**
+- [ ] Module name and description
+- [ ] Installation instructions
+- [ ] Components section (agents, workflows)
+- [ ] Usage examples or quick start
+- [ ] Module structure
+- [ ] Link to docs/ folder
+
+**Quality Checks:**
+- [ ] Clear description of what module does
+- [ ] Installation command shown
+- [ ] Agent/workflow lists complete
+- [ ] References user documentation
+
+### 3. Validate TODO.md
+
+**Required Content:**
+- [ ] Agent build checklist
+- [ ] Workflow build checklist
+- [ ] Testing section
+- [ ] Next steps
+
+### 4. Validate docs/ Folder
+
+**For Custom Modules:**
+- [ ] docs/ folder exists
+- [ ] Contains user-facing documentation
+- [ ] Documentation is clear and helpful
+
+**Valid docs/ Contents (may include):**
+- `getting-started.md` — Quick start guide
+- `agents.md` — Agent documentation
+- `workflows.md` — Workflow documentation
+- `examples.md` — Usage examples
+- `configuration.md` — Setup/configuration guide
+- `troubleshooting.md` — Common issues and solutions
+
+**Quality Check:**
+- [ ] Even with placeholder agent/workflow specs, user docs should provide useful information
+- [ ] Documentation references agents/workflows by name
+- [ ] Clear what functionality exists vs what is planned
+
+### 5. Generate User Docs Recommendation
+
+**IF docs/ missing or incomplete:**
+
+"**User documentation can be generated from module brief and agent/workflow specs.**"
+
+"**Even with placeholder plans, you can create helpful user documentation that describes:**
+- What each agent does and when to use it
+- What workflows are available and their purpose
+- How to get started with the module
+- Configuration options (from module.yaml)"
+
+### 6. Record Results
+
+Append to `{validationReportOutput}`:
+
+```markdown
+## Documentation Validation
+
+**Status:** {PASS/FAIL/WARNINGS}
+
+**Root Documentation:**
+- **README.md:** {present/missing} - {status}
+- **TODO.md:** {present/missing} - {status}
+
+**User Documentation (docs/):**
+- **docs/ folder:** {present/missing} - {status}
+- **Documentation files:** {count} files found
+
+**Docs Contents:**
+{list files in docs/ folder}
+
+**Issues Found:**
+{list any issues}
+
+**Recommendations:**
+{if docs/ missing or incomplete}
+- Generate user documentation from module brief and specs
+- Create getting-started.md, agents.md, workflows.md
+- User docs are valuable even with placeholder plans
+{endif}
+```
+
+### 7. Auto-Proceed
+
+"**✓ Documentation check complete.**"
+
+Proceeding to installation validation...
+
+Load `{nextStepFile}`
+
+---
+
+## Success Metrics
+
+✅ All documentation checked
+✅ Required sections validated
+✅ docs/ folder presence verified
+✅ User documentation quality assessed
+✅ Recommendations documented