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

package/src/bmb/workflows/agent/steps-v/v-02a-validate-metadata.md

@@ -1,116 +1,116 @@
----
-name: 'v-02a-validate-metadata'
-description: 'Validate metadata and append to report'
-
-nextStepFile: './v-02b-validate-persona.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-agentMetadata: ../data/agent-metadata.md
-agentFile: '{agent-file-path}'
----
-
-# Validate Step 2a: Validate Metadata
-
-## STEP GOAL
-
-Validate the agent's metadata properties against BMAD standards as defined in agentMetadata.md. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and agentMetadata first
-- 🔄 CRITICAL: Load the actual agent file to validate metadata
-- 🚫 NO MENU - append 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
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS
-
-- 🎯 Load agentMetadata.md reference
-- 🎯 Load the actual agent file for validation
-- 📊 Validate all metadata fields
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load References
-
-Read `{agentMetadata}`, `{validationReport}`, and `{agentFile}`.
-
-### 2. Validate Metadata
-
-Perform these checks systematically - validate EVERY rule specified in agentMetadata.md:
-
-1. **Required Fields Existence**
-   - [ ] id: Present and non-empty
-   - [ ] name: Present and non-empty (display name)
-   - [ ] title: Present and non-empty
-   - [ ] icon: Present (emoji or symbol)
-   - [ ] module: Present and valid format
-   - [ ] hasSidecar: Present (boolean, if applicable)
-
-2. **Format Validation**
-   - [ ] id: Uses kebab-case, no spaces, unique identifier
-   - [ ] name: Clear display name for UI
-   - [ ] title: Concise functional description
-   - [ ] icon: Appropriate emoji or unicode symbol
-   - [ ] module: Either a 3-4 letter module code OR 'stand-alone'
-   - [ ] hasSidecar: Boolean value, matches actual agent structure
-
-3. **Content Quality**
-   - [ ] id: Unique and descriptive
-   - [ ] name: Clear and user-friendly
-   - [ ] title: Accurately describes agent's function
-   - [ ] icon: Visually representative of agent's purpose
-   - [ ] module: Correctly identifies module membership
-   - [ ] hasSidecar: Correctly indicates if agent uses sidecar files
-
-4. **Agent Type Consistency**
-   - [ ] If hasSidecar: true, sidecar folder path must be specified
-   - [ ] If module is a module code, agent is a module agent
-   - [ ] If module is 'stand-alone', agent is not part of a module
-   - [ ] No conflicting type indicators
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Metadata Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] id: kebab-case, no spaces, unique
-- [ ] name: clear display name
-- [ ] title: concise function description
-- [ ] icon: appropriate emoji/symbol
-- [ ] module: correct format (code or stand-alone)
-- [ ] hasSidecar: matches actual usage
-
-**Detailed Findings:**
-
-*PASSING:*
-{List of passing checks}
-
-*WARNINGS:*
-{List of non-blocking issues}
-
-*FAILURES:*
-{List of blocking issues that must be fixed}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating persona...**
+---
+name: 'v-02a-validate-metadata'
+description: 'Validate metadata and append to report'
+
+nextStepFile: './v-02b-validate-persona.md'
+validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
+agentMetadata: ../data/agent-metadata.md
+agentFile: '{agent-file-path}'
+---
+
+# Validate Step 2a: Validate Metadata
+
+## STEP GOAL
+
+Validate the agent's metadata properties against BMAD standards as defined in agentMetadata.md. Append findings to validation report and auto-advance.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read validationReport and agentMetadata first
+- 🔄 CRITICAL: Load the actual agent file to validate metadata
+- 🚫 NO MENU - append 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
+- 📊 Append findings to validation report
+- 🚫 FORBIDDEN to present menu
+
+## EXECUTION PROTOCOLS
+
+- 🎯 Load agentMetadata.md reference
+- 🎯 Load the actual agent file for validation
+- 📊 Validate all metadata fields
+- 💾 Append findings to validation report
+- ➡️ Auto-advance to next validation step
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Load References
+
+Read `{agentMetadata}`, `{validationReport}`, and `{agentFile}`.
+
+### 2. Validate Metadata
+
+Perform these checks systematically - validate EVERY rule specified in agentMetadata.md:
+
+1. **Required Fields Existence**
+   - [ ] id: Present and non-empty
+   - [ ] name: Present and non-empty (display name)
+   - [ ] title: Present and non-empty
+   - [ ] icon: Present (emoji or symbol)
+   - [ ] module: Present and valid format
+   - [ ] hasSidecar: Present (boolean, if applicable)
+
+2. **Format Validation**
+   - [ ] id: Uses kebab-case, no spaces, unique identifier
+   - [ ] name: Clear display name for UI
+   - [ ] title: Concise functional description
+   - [ ] icon: Appropriate emoji or unicode symbol
+   - [ ] module: Either a 3-4 letter module code OR 'stand-alone'
+   - [ ] hasSidecar: Boolean value, matches actual agent structure
+
+3. **Content Quality**
+   - [ ] id: Unique and descriptive
+   - [ ] name: Clear and user-friendly
+   - [ ] title: Accurately describes agent's function
+   - [ ] icon: Visually representative of agent's purpose
+   - [ ] module: Correctly identifies module membership
+   - [ ] hasSidecar: Correctly indicates if agent uses sidecar files
+
+4. **Agent Type Consistency**
+   - [ ] If hasSidecar: true, sidecar folder path must be specified
+   - [ ] If module is a module code, agent is a module agent
+   - [ ] If module is 'stand-alone', agent is not part of a module
+   - [ ] No conflicting type indicators
+
+### 3. Append Findings to Report
+
+Append to `{validationReport}`:
+
+```markdown
+### Metadata Validation
+
+**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
+
+**Checks:**
+- [ ] id: kebab-case, no spaces, unique
+- [ ] name: clear display name
+- [ ] title: concise function description
+- [ ] icon: appropriate emoji/symbol
+- [ ] module: correct format (code or stand-alone)
+- [ ] hasSidecar: matches actual usage
+
+**Detailed Findings:**
+
+*PASSING:*
+{List of passing checks}
+
+*WARNINGS:*
+{List of non-blocking issues}
+
+*FAILURES:*
+{List of blocking issues that must be fixed}
+```
+
+### 4. Auto-Advance
+
+Load and execute `{nextStepFile}` immediately.
+
+---
+
+**Validating persona...**

package/src/bmb/workflows/agent/steps-v/v-02b-validate-persona.md

@@ -1,124 +1,124 @@
----
-name: 'v-02b-validate-persona'
-description: 'Validate persona and append to report'
-
-nextStepFile: './v-02c-validate-menu.md'
-validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
-personaProperties: ../data/persona-properties.md
-principlesCrafting: ../data/principles-crafting.md
-agentFile: '{agent-file-path}'
----
-
-# Validate Step 2b: Validate Persona
-
-## STEP GOAL
-
-Validate the agent's persona against BMAD standards as defined in personaProperties.md and principlesCrafting.md. Append findings to validation report and auto-advance.
-
-## MANDATORY EXECUTION RULES
-
-- 📖 CRITICAL: Read the complete step file before taking any action
-- 🔄 CRITICAL: Read validationReport and persona references first
-- 🔄 CRITICAL: Load the actual agent file to validate persona
-- 🚫 NO MENU - append findings and auto-advance
-- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
-
-### Step-Specific Rules:
-
-- 🎯 Validate persona against personaProperties.md rules
-- 📊 Append findings to validation report
-- 🚫 FORBIDDEN to present menu
-
-## EXECUTION PROTOCOLS
-
-- 🎯 Load personaProperties.md and principlesCrafting.md
-- 🎯 Load the actual agent file for validation
-- 📊 Validate persona fields
-- 💾 Append findings to validation report
-- ➡️ Auto-advance to next validation step
-
-## MANDATORY SEQUENCE
-
-**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
-
-### 1. Load References
-
-Read `{personaProperties}`, `{principlesCrafting}`, `{validationReport}`, and `{agentFile}`.
-
-### 2. Validate Persona
-
-Perform these checks systematically - validate EVERY rule specified in personaProperties.md:
-
-1. **Required Fields Existence**
-   - [ ] role: Present, clear, and specific
-   - [ ] identity: Present and defines who the agent is
-   - [ ] communication_style: Present and appropriate to role
-   - [ ] principles: Present as array, not empty (if applicable)
-
-2. **Content Quality - Role**
-   - [ ] Role is specific (not generic like "assistant")
-   - [ ] Role aligns with agent's purpose and menu items
-   - [ ] Role is achievable within LLM capabilities
-   - [ ] Role scope is appropriate (not too broad/narrow)
-
-3. **Content Quality - Identity**
-   - [ ] Identity clearly defines the agent's character
-   - [ ] Identity is consistent with the role
-   - [ ] Identity provides context for behavior
-   - [ ] Identity is not generic or cliché
-
-4. **Content Quality - Communication Style**
-   - [ ] Communication style is clearly defined
-   - [ ] Style matches the role and target users
-   - [ ] Style is consistent throughout the definition
-   - [ ] Style examples or guidance provided if nuanced
-   - [ ] Style focuses on speech patterns only (not behavior)
-
-5. **Content Quality - Principles**
-   - [ ] Principles are actionable (not vague platitudes)
-   - [ ] Principles guide behavior and decisions
-   - [ ] Principles are consistent with role
-   - [ ] 3-7 principles recommended (not overwhelming)
-   - [ ] Each principle is clear and specific
-   - [ ] First principle activates domain knowledge
-
-6. **Consistency Checks**
-   - [ ] Role, identity, communication_style, principles all align
-   - [ ] No contradictions between principles
-   - [ ] Persona supports the menu items defined
-   - [ ] Language and terminology consistent
-
-### 3. Append Findings to Report
-
-Append to `{validationReport}`:
-
-```markdown
-### Persona Validation
-
-**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
-
-**Checks:**
-- [ ] role: specific, not generic
-- [ ] identity: defines who agent is
-- [ ] communication_style: speech patterns only
-- [ ] principles: first principle activates domain knowledge
-
-**Detailed Findings:**
-
-*PASSING:*
-{List of passing checks}
-
-*WARNINGS:*
-{List of non-blocking issues}
-
-*FAILURES:*
-{List of blocking issues that must be fixed}
-```
-
-### 4. Auto-Advance
-
-Load and execute `{nextStepFile}` immediately.
-
----
-
-**Validating menu structure...**
+---
+name: 'v-02b-validate-persona'
+description: 'Validate persona and append to report'
+
+nextStepFile: './v-02c-validate-menu.md'
+validationReport: '{bmb_creations_output_folder}/validation-report-{agent-name}.md'
+personaProperties: ../data/persona-properties.md
+principlesCrafting: ../data/principles-crafting.md
+agentFile: '{agent-file-path}'
+---
+
+# Validate Step 2b: Validate Persona
+
+## STEP GOAL
+
+Validate the agent's persona against BMAD standards as defined in personaProperties.md and principlesCrafting.md. Append findings to validation report and auto-advance.
+
+## MANDATORY EXECUTION RULES
+
+- 📖 CRITICAL: Read the complete step file before taking any action
+- 🔄 CRITICAL: Read validationReport and persona references first
+- 🔄 CRITICAL: Load the actual agent file to validate persona
+- 🚫 NO MENU - append findings and auto-advance
+- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
+
+### Step-Specific Rules:
+
+- 🎯 Validate persona against personaProperties.md rules
+- 📊 Append findings to validation report
+- 🚫 FORBIDDEN to present menu
+
+## EXECUTION PROTOCOLS
+
+- 🎯 Load personaProperties.md and principlesCrafting.md
+- 🎯 Load the actual agent file for validation
+- 📊 Validate persona fields
+- 💾 Append findings to validation report
+- ➡️ Auto-advance to next validation step
+
+## MANDATORY SEQUENCE
+
+**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
+
+### 1. Load References
+
+Read `{personaProperties}`, `{principlesCrafting}`, `{validationReport}`, and `{agentFile}`.
+
+### 2. Validate Persona
+
+Perform these checks systematically - validate EVERY rule specified in personaProperties.md:
+
+1. **Required Fields Existence**
+   - [ ] role: Present, clear, and specific
+   - [ ] identity: Present and defines who the agent is
+   - [ ] communication_style: Present and appropriate to role
+   - [ ] principles: Present as array, not empty (if applicable)
+
+2. **Content Quality - Role**
+   - [ ] Role is specific (not generic like "assistant")
+   - [ ] Role aligns with agent's purpose and menu items
+   - [ ] Role is achievable within LLM capabilities
+   - [ ] Role scope is appropriate (not too broad/narrow)
+
+3. **Content Quality - Identity**
+   - [ ] Identity clearly defines the agent's character
+   - [ ] Identity is consistent with the role
+   - [ ] Identity provides context for behavior
+   - [ ] Identity is not generic or cliché
+
+4. **Content Quality - Communication Style**
+   - [ ] Communication style is clearly defined
+   - [ ] Style matches the role and target users
+   - [ ] Style is consistent throughout the definition
+   - [ ] Style examples or guidance provided if nuanced
+   - [ ] Style focuses on speech patterns only (not behavior)
+
+5. **Content Quality - Principles**
+   - [ ] Principles are actionable (not vague platitudes)
+   - [ ] Principles guide behavior and decisions
+   - [ ] Principles are consistent with role
+   - [ ] 3-7 principles recommended (not overwhelming)
+   - [ ] Each principle is clear and specific
+   - [ ] First principle activates domain knowledge
+
+6. **Consistency Checks**
+   - [ ] Role, identity, communication_style, principles all align
+   - [ ] No contradictions between principles
+   - [ ] Persona supports the menu items defined
+   - [ ] Language and terminology consistent
+
+### 3. Append Findings to Report
+
+Append to `{validationReport}`:
+
+```markdown
+### Persona Validation
+
+**Status:** {✅ PASS / ⚠️ WARNING / ❌ FAIL}
+
+**Checks:**
+- [ ] role: specific, not generic
+- [ ] identity: defines who agent is
+- [ ] communication_style: speech patterns only
+- [ ] principles: first principle activates domain knowledge
+
+**Detailed Findings:**
+
+*PASSING:*
+{List of passing checks}
+
+*WARNINGS:*
+{List of non-blocking issues}
+
+*FAILURES:*
+{List of blocking issues that must be fixed}
+```
+
+### 4. Auto-Advance
+
+Load and execute `{nextStepFile}` immediately.
+
+---
+
+**Validating menu structure...**