bmad-method 6.0.0-alpha.22 → 6.0.0-alpha.23

package/src/modules/bmb/workflows/agent/steps-e/e-03d-validate-structure.md

@@ -1,75 +0,0 @@
----
-name: 'e-03d-validate-structure'
-description: 'Validate YAML structure (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03e-validate-sidecar.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentCompilation: ../data/agent-compilation.md
----
-
-# Edit Step 3d: Validate Structure (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's YAML structure and completeness. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentCompilation first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate YAML structure and required fields
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentCompilation.md reference
-- 📊 Validate YAML structure
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentCompilation}`.
-Read `{editPlan}` to get agent file path.
-
-### 2. Validate Structure
-
-Perform checks on:
-- **YAML syntax**: valid, no parse errors
-- **Required fields**: name, description, type, persona present
-- **Field types**: arrays where expected, strings where expected
-- **Indentation**: consistent 2-space indentation
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  structure:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-When validation complete, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All structure checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to sidecar validation...**

package/src/modules/bmb/workflows/agent/steps-e/e-03e-validate-sidecar.md

@@ -1,78 +0,0 @@
----
-name: 'e-03e-validate-sidecar'
-description: 'Validate sidecar structure (before edit) - no menu, auto-advance'
-
-nextStepFile: './e-03f-validation-summary.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
----
-
-# Edit Step 3e: Validate Sidecar (Before Edit)
-
-## STEP GOAL:
-
-Validate the agent's sidecar structure if Expert type. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and expertValidation first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate sidecar structure for Expert agents
-- 📊 Record findings to editPlan frontmatter
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load expertValidation.md reference
-- 📊 Validate sidecar if Expert type, skip for Simple/Module
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to validation summary when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{expertValidation}`.
-Read `{editPlan}` to get agent type.
-
-### 2. Conditional Validation
-
-**IF agentType == expert:**
-- Check metadata.sidecar-folder is present
-- Check sidecar-path is correct format
-- Verify sidecar files exist at specified path
-
-**IF agentType != expert:**
-- Mark as N/A (not applicable)
-- Skip detailed checks
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  sidecar:
-    status: [pass|fail|warning|n/a]
-    findings:
-      - {check}: [pass|fail|n/a]
-      - {check}: [pass|fail|n/a]
-```
-
-### 4. Auto-Advance
-
-When validation complete, load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ Sidecar checks performed (or N/A recorded)
-✅ Findings saved to editPlan
-✅ Auto-advanced to validation summary
-
----
-
-**Auto-advancing to validation summary...**

package/src/modules/bmb/workflows/agent/steps-e/e-03f-validation-summary.md

@@ -1,119 +0,0 @@
----
-name: 'e-03f-validation-summary'
-description: 'Display all validation findings before edit'
-
-nextStepFile: './e-04-type-metadata.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-
-advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
-partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
----
-
-# Edit Step 3f: Validation Summary (Before Edit)
-
-## STEP GOAL:
-
-Display all validation findings from the previous 5 validation steps to the user. Present findings clearly and await confirmation to proceed.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan to collect all validation findings
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Display all validation findings clearly organized
-- 📊 Aggregate findings from all 5 validation steps
-- 💬 Present options for handling any issues found
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Read editPlan to get validation findings
-- 📊 Display organized summary
-- 💾 Allow user to decide how to proceed
-- ➡️ Proceed to edit plan on [C]
-
-## Sequence of Instructions:
-
-### 1. Load Validation Findings
-
-Read `{editPlan}` frontmatter to collect:
-- validationBefore.metadata.status and findings
-- validationBefore.persona.status and findings
-- validationBefore.menu.status and findings
-- validationBefore.structure.status and findings
-- validationBefore.sidecar.status and findings
-
-### 2. Display Validation Summary
-
-```markdown
-## Pre-Edit Validation Report for {agent-name}
-
-### Metadata Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-
-### Persona Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-
-### Menu Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-
-### Structure Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-{Findings summary}
-
-### Sidecar Validation
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL / N/A}
-{Findings summary}
-```
-
-### 3. Present Options
-
-"How would you like to proceed?
-
-**[I**ntegrate fixes**] - Add validation fixes to your edit plan
-**[S]kip** - Proceed with your planned edits only
-**[A]dvanced** - Deeper exploration of any issues"
-
-### 4. Present MENU OPTIONS
-
-Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Edit Plan"
-
-#### Menu Handling Logic:
-
-- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
-- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
-- IF I: Add validation fixes to editPlan, then redisplay menu
-- IF C: Save validation summary to {editPlan}, then only then load, read entire file, then execute {nextStepFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#4-present-menu-options)
-
-#### EXECUTION RULES:
-
-- ALWAYS halt and wait for user input after presenting menu
-- ONLY proceed to next step when user selects 'C'
-- After other menu items execution, return to this menu
-
-## CRITICAL STEP COMPLETION NOTE
-
-ONLY WHEN [C continue option] is selected and [validation summary displayed], will you then load and read fully `{nextStepFile}` to execute and begin edit planning.
-
----
-
-## 🚨 SYSTEM SUCCESS/FAILURE METRICS
-
-### ✅ SUCCESS:
-
-- All validation findings displayed clearly
-- User given options for handling issues
-- Validation summary saved to editPlan
-
-### ❌ SYSTEM FAILURE:
-
-- Findings not displayed to user
-- Proceeding without user acknowledgment
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/modules/bmb/workflows/agent/steps-e/e-09a-validate-metadata.md

@@ -1,70 +0,0 @@
----
-name: 'e-09a-validate-metadata'
-description: 'Validate metadata (after edit) - no menu, auto-advance'
-
-nextStepFile: './e-09b-validate-persona.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentMetadata: ../data/agent-metadata.md
----
-
-# Edit Step 9a: Validate Metadata (After Edit)
-
-## STEP GOAL:
-
-Validate the agent's metadata properties after edits. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentMetadata first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate metadata against agentMetadata.md rules
-- 📊 Record findings to editPlan frontmatter (validationAfter section)
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMetadata.md reference
-- 📊 Validate all metadata fields
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMetadata}` and `{editPlan}`.
-
-### 2. Validate Metadata
-
-Perform checks on id, name, title, icon, module, hasSidecar.
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-validationAfter:
-  metadata:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All metadata checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to persona validation...**

package/src/modules/bmb/workflows/agent/steps-e/e-09b-validate-persona.md

@@ -1,70 +0,0 @@
----
-name: 'e-09b-validate-persona'
-description: 'Validate persona (after edit) - no menu, auto-advance'
-
-nextStepFile: './e-09c-validate-menu.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
----
-
-# Edit Step 9b: Validate Persona (After Edit)
-
-## STEP GOAL:
-
-Validate the agent's persona after edits. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and persona references first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate persona four-field system
-- 📊 Record findings to editPlan frontmatter (validationAfter section)
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load personaProperties.md and principlesCrafting.md
-- 📊 Validate persona fields
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{personaProperties}`, `{principlesCrafting}`, and `{editPlan}`.
-
-### 2. Validate Persona
-
-Perform checks on role, identity, communication_style, principles.
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  persona:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All persona checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to menu validation...**

package/src/modules/bmb/workflows/agent/steps-e/e-09c-validate-menu.md

@@ -1,69 +0,0 @@
----
-name: 'e-09c-validate-menu'
-description: 'Validate menu structure (after edit) - no menu, auto-advance'
-
-nextStepFile: './e-09d-validate-structure.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentMenuPatterns: ../data/agent-menu-patterns.md
----
-
-# Edit Step 9c: Validate Menu (After Edit)
-
-## STEP GOAL:
-
-Validate the agent's command menu structure after edits. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentMenuPatterns first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate command/menu structure
-- 📊 Record findings to editPlan frontmatter (validationAfter section)
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentMenuPatterns.md reference
-- 📊 Validate commands and menu
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentMenuPatterns}` and `{editPlan}`.
-
-### 2. Validate Menu
-
-Perform checks on A/P/C convention, command names, descriptions.
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  menu:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All menu checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to structure validation...**

package/src/modules/bmb/workflows/agent/steps-e/e-09d-validate-structure.md

@@ -1,69 +0,0 @@
----
-name: 'e-09d-validate-structure'
-description: 'Validate YAML structure (after edit) - no menu, auto-advance'
-
-nextStepFile: './e-09e-validate-sidecar.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-agentCompilation: ../data/agent-compilation.md
----
-
-# Edit Step 9d: Validate Structure (After Edit)
-
-## STEP GOAL:
-
-Validate the agent's YAML structure after edits. Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and agentCompilation first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate YAML structure and required fields
-- 📊 Record findings to editPlan frontmatter (validationAfter section)
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load agentCompilation.md reference
-- 📊 Validate YAML structure
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to next validation step when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{agentCompilation}` and `{editPlan}`.
-
-### 2. Validate Structure
-
-Perform checks on YAML syntax, required fields, field types, indentation.
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  structure:
-    status: [pass|fail|warning]
-    findings:
-      - {check}: [pass|fail]
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ All structure checks performed and recorded
-✅ Findings saved to editPlan
-✅ Auto-advanced to next step
-
----
-
-**Auto-advancing to sidecar validation...**

package/src/modules/bmb/workflows/agent/steps-e/e-09e-validate-sidecar.md

@@ -1,70 +0,0 @@
----
-name: 'e-09e-validate-sidecar'
-description: 'Validate sidecar structure (after edit) - no menu, auto-advance'
-
-nextStepFile: './e-09f-validation-summary.md'
-editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
-expertValidation: ../data/expert-agent-validation.md
----
-
-# Edit Step 9e: Validate Sidecar (After Edit)
-
-## STEP GOAL:
-
-Validate the agent's sidecar structure after edits (if Expert type). Record findings to editPlan and auto-advance.
-
-## MANDATORY EXECUTION RULES:
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read editPlan and expertValidation first
-- 🚫 NO MENU in this step - record findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate sidecar structure for Expert agents
-- 📊 Record findings to editPlan frontmatter (validationAfter section)
-- 🚫 FORBIDDEN to present menu - auto-advance when complete
-
-## EXECUTION PROTOCOLS:
-
-- 🎯 Load expertValidation.md reference
-- 📊 Validate sidecar if Expert type, skip for Simple/Module
-- 💾 Record findings to editPlan
-- ➡️ Auto-advance to validation summary when complete
-
-## Sequence of Instructions:
-
-### 1. Load References
-
-Read `{expertValidation}` and `{editPlan}` to get agent type.
-
-### 2. Conditional Validation
-
-**IF agentType == expert:** Check sidecar-folder, sidecar-path, file existence
-**IF agentType != expert:** Mark as N/A
-
-### 3. Record Findings
-
-Append to editPlan frontmatter:
-
-```yaml
-  sidecar:
-    status: [pass|fail|warning|n/a]
-    findings:
-      - {check}: [pass|fail|n/a]
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
-## SUCCESS METRICS
-
-✅ Sidecar checks performed (or N/A recorded)
-✅ Findings saved to editPlan
-✅ Auto-advanced to validation summary
-
----
-
-**Auto-advancing to validation summary...**