mirror of
https://github.com/R0m1k3/Socialflow.git
synced 2026-10-20 05:28:13 +02:00
feat: implement reel improvements (clean text, deletion, mobile TTS)
This commit is contained in:
Michael committed
1 parent
cb0ff8a0ea
commit
dbddf3a74e
895 files changed
+26890
-93267
No files matched your search
@@ -4,7 +4,7 @@ description: 'Load and analyze existing agent for editing'
|
||||
|
||||
# File References
|
||||
thisStepFile: ./e-01-load-existing.md
|
||||
workflowFile: ../workflow.md
|
||||
workflowFile: ../workflow-edit-agent.md
|
||||
nextStepFile: './e-02-discover-edits.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentMetadata: ../data/agent-metadata.md
|
||||
@@ -59,7 +59,9 @@ Load the existing agent file, parse its structure, and create an edit plan track
|
||||
- Limits: Analysis only, no modifications
|
||||
- Dependencies: Agent file must exist and be valid YAML
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Load Agent File
|
||||
|
||||
@@ -74,14 +76,20 @@ Expected format: `{path-to-agent}/{agent-name}.agent.yaml`"
|
||||
|
||||
### 2. Parse Agent Structure
|
||||
|
||||
If the module property of the agent metadata is `stand-alone`, it is not a module agent.
|
||||
If the module property of the agent is a module code (like bmm, bmb, etc...) it is a module agent.
|
||||
If the property hasSidecar: true exists in the metadata, then it is an expert agent.
|
||||
Else it is a simple agent.
|
||||
If a module agent also hasSidecar: true - this means it is a modules expert agent, thus it can have sidecar.
|
||||
|
||||
**Extract and categorize all agent components:**
|
||||
|
||||
```yaml
|
||||
# Basic Metadata
|
||||
- name: {agent-name}
|
||||
- description: {agent-description}
|
||||
- type: {simple|expert|module}
|
||||
- version: {version}
|
||||
- module: {stand-alone|bmm|cis|bmgd|custom}
|
||||
- hasSidecar: {true|false}
|
||||
|
||||
# Persona
|
||||
- persona: {full persona text}
|
||||
@@ -104,8 +112,7 @@ Expected format: `{path-to-agent}/{agent-name}.agent.yaml`"
|
||||
```markdown
|
||||
## Agent Analysis: {agent-name}
|
||||
|
||||
**Type:** {simple|expert|module}
|
||||
**Version:** {version}
|
||||
**Type:** {simple|expert|module} (derived from module + hasSidecar)
|
||||
**Status:** ready-for-edit
|
||||
|
||||
### Current Structure:
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
name: 'e-02-discover-edits'
|
||||
description: 'Discover what user wants to change about the agent'
|
||||
|
||||
nextStepFile: './e-03a-validate-metadata.md'
|
||||
nextStepFile: './e-04-sidecar-metadata.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
|
||||
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
||||
@@ -54,7 +54,9 @@ Conduct targeted discovery to understand exactly what the user wants to change a
|
||||
- Limits: Discovery and documentation only, no implementation
|
||||
- Dependencies: Agent must be loaded in editPlan
|
||||
|
||||
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Read Edit Plan Context
|
||||
|
||||
@@ -72,8 +74,8 @@ I can help you modify:
|
||||
**[P]ersona** - Role, identity, communication style, principles
|
||||
**[C]ommands** - Add, remove, or modify commands and menu structure
|
||||
**[M]etadata** - Name, description, version, tags, category
|
||||
**[S]idecar** - Add or remove memory (convert hasSidecar: true/false)
|
||||
**[A]ctions** - Critical actions and activation behaviors
|
||||
**[T]ype** - Convert between Simple/Expert/Module types
|
||||
**[O]ther** - Configuration, capabilities, system context
|
||||
|
||||
Which areas would you like to edit? (You can select multiple)"
|
||||
@@ -105,10 +107,10 @@ Which areas would you like to edit? (You can select multiple)"
|
||||
- "Should new activation behaviors be added?"
|
||||
- "Are current actions executing as expected?"
|
||||
|
||||
#### If Type conversion selected:
|
||||
- "What type are you converting from/to?"
|
||||
- "What's driving this conversion?"
|
||||
- "Are you aware of the implications (e.g., Expert needs sidecar)?"
|
||||
#### If Sidecar selected:
|
||||
- "Do you want to add memory (hasSidecar: true) or remove it (hasSidecar: false)?"
|
||||
- "What should the agent remember across sessions?"
|
||||
- "Are you aware of the implications?"
|
||||
|
||||
### 4. Document Edits to Plan
|
||||
|
||||
@@ -133,8 +135,9 @@ Which areas would you like to edit? (You can select multiple)"
|
||||
- [ ] {edit description}
|
||||
- [ ] {edit description}
|
||||
|
||||
### Type Conversion
|
||||
- [ ] {from: X, to: Y, rationale: ...}
|
||||
### Sidecar Conversion
|
||||
- [ ] {from: hasSidecar: false, to: hasSidecar: true, rationale: ...}
|
||||
- [ ] {from: hasSidecar: true, to: hasSidecar: false, rationale: ...}
|
||||
|
||||
### Other Edits
|
||||
- [ ] {edit description}
|
||||
@@ -168,7 +171,7 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [C continue option] is selected and [all edits documented and confirmed by user], will you then load and read fully `{nextStepFile}` to execute and begin validation.
|
||||
ONLY WHEN [C continue option] is selected and [all edits documented and confirmed by user], will you then load and read fully `{nextStepFile}` to execute and checks.
|
||||
|
||||
---
|
||||
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
# Placeholder - do not load this step.
|
||||
@@ -1,78 +0,0 @@
|
||||
---
|
||||
name: 'e-03a-validate-metadata'
|
||||
description: 'Validate metadata (before edit) - no menu, auto-advance'
|
||||
|
||||
nextStepFile: './e-03b-validate-persona.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentMetadata: ../data/agent-metadata.md
|
||||
---
|
||||
|
||||
# Edit Step 3a: Validate Metadata (Before Edit)
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Validate the agent's metadata properties against BMAD standards. Record findings to editPlan and auto-advance to next validation step.
|
||||
|
||||
## 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
|
||||
- 🚫 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}` to understand validation rules.
|
||||
Read `{editPlan}` to get agent file path and metadata.
|
||||
|
||||
### 2. Validate Metadata
|
||||
|
||||
Perform checks on:
|
||||
- **id**: kebab-case, no spaces
|
||||
- **name**: display name, clear branding
|
||||
- **title**: concise function description
|
||||
- **icon**: appropriate emoji or symbol
|
||||
- **module**: correct format `{project}:{type}:{name}`
|
||||
- **hasSidecar**: boolean, matches actual sidecar usage
|
||||
|
||||
### 3. Record Findings
|
||||
|
||||
Append to editPlan frontmatter:
|
||||
|
||||
```yaml
|
||||
validationBefore:
|
||||
metadata:
|
||||
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 metadata checks performed and recorded
|
||||
✅ Findings saved to editPlan
|
||||
✅ Auto-advanced to next step
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to persona validation...**
|
||||
@@ -1,76 +0,0 @@
|
||||
---
|
||||
name: 'e-03b-validate-persona'
|
||||
description: 'Validate persona (before edit) - no menu, auto-advance'
|
||||
|
||||
nextStepFile: './e-03c-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 3b: Validate Persona (Before Edit)
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Validate the agent's persona fields against BMAD standards. 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
|
||||
- 🚫 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}` and `{principlesCrafting}`.
|
||||
Read `{editPlan}` to get agent file path and persona.
|
||||
|
||||
### 2. Validate Persona
|
||||
|
||||
Perform checks on:
|
||||
- **role**: present, specific, not generic
|
||||
- **identity**: present, defines who agent is
|
||||
- **communication_style**: present, speech patterns only (no behavioral words)
|
||||
- **principles**: present, first principle activates expert knowledge, not generic duties
|
||||
|
||||
### 3. Record Findings
|
||||
|
||||
Append to editPlan frontmatter:
|
||||
|
||||
```yaml
|
||||
persona:
|
||||
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 persona checks performed and recorded
|
||||
✅ Findings saved to editPlan
|
||||
✅ Auto-advanced to next step
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to menu validation...**
|
||||
@@ -1,75 +0,0 @@
|
||||
---
|
||||
name: 'e-03c-validate-menu'
|
||||
description: 'Validate menu structure (before edit) - no menu, auto-advance'
|
||||
|
||||
nextStepFile: './e-03d-validate-structure.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentMenuPatterns: ../data/agent-menu-patterns.md
|
||||
---
|
||||
|
||||
# Edit Step 3c: Validate Menu (Before Edit)
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Validate the agent's command menu structure against BMAD standards. 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
|
||||
- 🚫 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}`.
|
||||
Read `{editPlan}` to get agent file path and commands.
|
||||
|
||||
### 2. Validate Menu
|
||||
|
||||
Perform checks on:
|
||||
- **A/P/C convention**: each menu has Advanced Elicitation, Party Mode, Continue
|
||||
- **Command names**: clear, descriptive
|
||||
- **Command descriptions**: specific, actionable
|
||||
- **Menu handling logic**: properly specified
|
||||
|
||||
### 3. Record Findings
|
||||
|
||||
Append to editPlan frontmatter:
|
||||
|
||||
```yaml
|
||||
menu:
|
||||
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 menu checks performed and recorded
|
||||
✅ Findings saved to editPlan
|
||||
✅ Auto-advanced to next step
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to structure validation...**
|
||||
@@ -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...**
|
||||
@@ -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...**
|
||||
@@ -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.
|
||||
+21
-18
@@ -1,5 +1,5 @@
|
||||
---
|
||||
name: 'e-04-type-metadata'
|
||||
name: 'e-04-sidecar-metadata'
|
||||
description: 'Review and plan metadata edits'
|
||||
|
||||
nextStepFile: './e-05-persona.md'
|
||||
@@ -11,11 +11,11 @@ advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitati
|
||||
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Edit Step 4: Type and Metadata
|
||||
# Edit Step 4: Sidecar and Metadata
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Review the agent's type and metadata, and plan any changes. If edits involve type conversion, identify the implications.
|
||||
Review the agent's hasSidecar decision and metadata, and plan any changes. If edits involve sidecar conversion, identify the implications.
|
||||
|
||||
## MANDATORY EXECUTION RULES:
|
||||
|
||||
@@ -26,7 +26,7 @@ Review the agent's type and metadata, and plan any changes. If edits involve typ
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Load reference documents before discussing edits
|
||||
- 📊 Document type conversion requirements if applicable
|
||||
- 📊 Document sidecar conversion requirements if applicable
|
||||
- 💬 Focus on metadata that user wants to change
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
@@ -36,26 +36,30 @@ Review the agent's type and metadata, and plan any changes. If edits involve typ
|
||||
- 💾 Document planned metadata changes
|
||||
- 🚫 FORBIDDEN to proceed without documenting changes
|
||||
|
||||
## Sequence of Instructions:
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
Read `{agentMetadata}` and `{agentTypesDoc}` to understand validation rules and type implications.
|
||||
Read `{agentMetadata}` and `{agentTypesDoc}` to understand validation rules and sidecar implications.
|
||||
|
||||
### 2. Review Current Metadata
|
||||
|
||||
From `{editPlan}`, display current:
|
||||
- agentType (simple/expert/module)
|
||||
- All metadata fields: id, name, title, icon, module, hasSidecar
|
||||
- hasSidecar (true/false)
|
||||
- All metadata fields: id, name, title, icon, module
|
||||
|
||||
### 3. Discuss Metadata Edits
|
||||
|
||||
If user wants metadata changes:
|
||||
|
||||
**For type conversion:**
|
||||
- "Converting from {current} to {target}"
|
||||
- Explain implications (e.g., Simple → Expert requires sidecar)
|
||||
- Update editPlan with type conversion
|
||||
**For sidecar conversion:**
|
||||
- "Converting from hasSidecar: {current} to {target}"
|
||||
- Explain implications:
|
||||
- false → true: Need to create sidecar folder, add critical_actions with sidecar file loading
|
||||
- true → false: Remove sidecar fields; if critical_actions only has sidecar references, remove section; otherwise keep non-sidecar critical_actions
|
||||
- Update editPlan with conversion
|
||||
|
||||
**For metadata field changes:**
|
||||
- id: kebab-case requirements
|
||||
@@ -63,7 +67,6 @@ If user wants metadata changes:
|
||||
- title: function description format
|
||||
- icon: emoji/symbol
|
||||
- module: path format
|
||||
- hasSidecar: boolean implications
|
||||
|
||||
### 4. Document to Edit Plan
|
||||
|
||||
@@ -71,9 +74,9 @@ Append to `{editPlan}`:
|
||||
|
||||
```yaml
|
||||
metadataEdits:
|
||||
typeConversion:
|
||||
from: {current-type}
|
||||
to: {target-type}
|
||||
sidecarConversion:
|
||||
from: {current-hasSidecar}
|
||||
to: {target-hasSidecar}
|
||||
rationale: {explanation}
|
||||
fieldChanges:
|
||||
- field: {field-name}
|
||||
@@ -110,13 +113,13 @@ ONLY WHEN [C continue option] is selected and [metadata changes documented], wil
|
||||
|
||||
- Reference documents loaded
|
||||
- Metadata changes discussed and documented
|
||||
- Type conversion implications understood
|
||||
- Sidecar conversion implications understood
|
||||
- Edit plan updated
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Proceeded without loading reference documents
|
||||
- Type conversion without understanding implications
|
||||
- Sidecar conversion without understanding implications
|
||||
- Changes not documented to edit plan
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -37,7 +37,9 @@ Review the agent's persona and plan any changes using the four-field persona sys
|
||||
- 💾 Document planned persona changes
|
||||
- 🚫 FORBIDDEN to proceed without documenting changes
|
||||
|
||||
## Sequence of Instructions:
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
|
||||
@@ -35,7 +35,9 @@ Review the agent's command menu and plan any additions, modifications, or remova
|
||||
- 💾 Document planned command changes
|
||||
- 🚫 FORBIDDEN to proceed without documenting changes
|
||||
|
||||
## Sequence of Instructions:
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
|
||||
@@ -1,14 +1,12 @@
|
||||
---
|
||||
name: 'e-07-activation'
|
||||
description: 'Review critical_actions and route to type-specific edit'
|
||||
description: 'Review critical_actions and route to edit step'
|
||||
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
criticalActions: ../data/critical-actions.md
|
||||
|
||||
# Type-specific edit routes
|
||||
simpleEdit: './e-08a-edit-simple.md'
|
||||
expertEdit: './e-08b-edit-expert.md'
|
||||
moduleEdit: './e-08c-edit-module.md'
|
||||
# Edit step route (determined by hasSidecar)
|
||||
agentEdit: './e-08-edit-agent.md'
|
||||
|
||||
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
||||
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
||||
@@ -18,52 +16,56 @@ partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Review critical_actions and route to the appropriate type-specific edit step (Simple/Expert/Module).
|
||||
Review critical_actions and route to the agent edit step based on hasSidecar value.
|
||||
|
||||
## MANDATORY EXECUTION RULES:
|
||||
|
||||
- 📖 CRITICAL: Read the complete step file before taking any action
|
||||
- 🔄 CRITICAL: Load criticalActions and editPlan first
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}}`
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Load criticalActions.md before discussing activation
|
||||
- 📊 Determine target type for routing
|
||||
- 💬 Route based on POST-EDIT agent type
|
||||
- 📊 Determine hasSidecar for routing
|
||||
- 💬 Route based on POST-EDIT hasSidecar value
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Load criticalActions.md
|
||||
- 📊 Check editPlan for target agent type
|
||||
- 💾 Route to appropriate type-specific edit step
|
||||
- ➡️ Auto-advance to type-specific edit on [C]
|
||||
- 📊 Check editPlan for target hasSidecar value
|
||||
- 💾 Route to agent edit step
|
||||
- ➡️ Auto-advance to edit step on [C]
|
||||
|
||||
## Sequence of Instructions:
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
Read `{criticalActions}` and `{editPlan}` to understand:
|
||||
- Current critical_actions (if any)
|
||||
- Target agent type after edits
|
||||
- Target hasSidecar value after edits
|
||||
|
||||
### 2. Review Critical Actions
|
||||
|
||||
If user wants to add/modify critical_actions:
|
||||
- Reference patterns from criticalActions.md
|
||||
- Define action name, description, invocation
|
||||
- For Expert agents: specify sidecar-folder and file paths
|
||||
- For hasSidecar: true — specify sidecar-folder and file paths
|
||||
|
||||
### 3. Determine Routing
|
||||
|
||||
Check `{editPlan}` metadataEdits.typeConversion.to or current agentType:
|
||||
Check `{editPlan}` for agent metadata (hasSidecar):
|
||||
|
||||
```yaml
|
||||
agentType: simple → route to e-08a-edit-simple.md
|
||||
agentType: expert → route to e-08b-edit-expert.md
|
||||
agentType: module → route to e-08c-edit-module.md
|
||||
# Simple routing based on hasSidecar
|
||||
hasSidecar: true → route to e-08-edit-agent.md (create sidecar structure)
|
||||
hasSidecar: false → route to e-08-edit-agent.md (single YAML file)
|
||||
```
|
||||
|
||||
The edit step handles both cases based on hasSidecar value.
|
||||
|
||||
### 4. Document to Edit Plan
|
||||
|
||||
Append to `{editPlan}`:
|
||||
@@ -74,19 +76,19 @@ activationEdits:
|
||||
additions: []
|
||||
modifications: []
|
||||
routing:
|
||||
destinationEdit: {e-08a|e-08b|e-08c}
|
||||
targetType: {simple|expert|module}
|
||||
destinationEdit: e-08-edit-agent.md
|
||||
hasSidecar: {true|false} # Derived from edit plan
|
||||
```
|
||||
|
||||
### 5. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Type-Specific Edit"
|
||||
Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Edit Agent"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
|
||||
- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
|
||||
- IF C: Save to {editPlan}, determine routing based on targetType, then only then load and execute the appropriate type-specific edit step
|
||||
- IF C: Save to {editPlan}, then only then load and execute the agent edit step
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#5-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
@@ -97,11 +99,10 @@ Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Cont
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
This is the **ROUTING HUB** for edit flow. ONLY WHEN [C continue option] is selected and [routing determined], load and execute the appropriate type-specific edit step:
|
||||
This is the **ROUTING HUB** for edit flow. ONLY WHEN [C continue option] is selected and [routing determined], load and execute the agent edit step:
|
||||
|
||||
- targetType: simple → e-08a-edit-simple.md
|
||||
- targetType: expert → e-08b-edit-expert.md
|
||||
- targetType: module → e-08c-edit-module.md
|
||||
- hasSidecar: false → Single YAML file edit
|
||||
- hasSidecar: true → YAML + sidecar folder structure edit
|
||||
|
||||
---
|
||||
|
||||
@@ -110,13 +111,13 @@ This is the **ROUTING HUB** for edit flow. ONLY WHEN [C continue option] is sele
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- criticalActions.md loaded
|
||||
- Routing determined based on target type
|
||||
- Routing determined based on hasSidecar
|
||||
- Edit plan updated with routing info
|
||||
|
||||
### ❌ SYSTEM FAILURE:
|
||||
|
||||
- Proceeded without loading reference documents
|
||||
- Routing not determined
|
||||
- Wrong type-specific edit step selected
|
||||
- Wrong edit step selected
|
||||
|
||||
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|
||||
@@ -0,0 +1,196 @@
|
||||
---
|
||||
name: 'e-08-edit-agent'
|
||||
description: 'Apply edits to agent (with or without sidecar)'
|
||||
|
||||
nextStepFile: './e-09-celebrate.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentFile: '{original-agent-path}'
|
||||
agentBackup: '{original-agent-path}.backup'
|
||||
|
||||
# Template and Architecture
|
||||
agentTemplate: ../templates/agent-template.md
|
||||
agentArch: ../data/agent-architecture.md
|
||||
agentValidation: ../data/agent-validation.md
|
||||
agentCompilation: ../data/agent-compilation.md
|
||||
agentMetadata: ../data/agent-metadata.md
|
||||
personaProperties: ../data/persona-properties.md
|
||||
principlesCrafting: ../data/principles-crafting.md
|
||||
agentMenuPatterns: ../data/agent-menu-patterns.md
|
||||
criticalActions: ../data/critical-actions.md
|
||||
|
||||
# Reference examples
|
||||
noSidecarExample: ../data/reference/without-sidecar/commit-poet.agent.yaml
|
||||
withSidecarExample: ../data/reference/with-sidecar/journal-keeper/journal-keeper.agent.yaml
|
||||
|
||||
advancedElicitationTask: '{project-root}/_bmad/core/workflows/advanced-elicitation/workflow.xml'
|
||||
partyModeWorkflow: '{project-root}/_bmad/core/workflows/party-mode/workflow.md'
|
||||
---
|
||||
|
||||
# Edit Step 8: Edit Agent
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply all planned edits to the agent YAML file. The edit approach (with or without sidecar) is determined by the `hasSidecar` value from the edit plan.
|
||||
|
||||
## MANDATORY EXECUTION RULES:
|
||||
|
||||
- 🛑 ALWAYS create backup before modifying agent file
|
||||
- 📖 CRITICAL: Read template and architecture files first
|
||||
- 🔄 CRITICAL: Load editPlan and agentFile
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Load all reference files before applying edits
|
||||
- 📊 Apply edits exactly as specified in editPlan
|
||||
- 💾 Validate YAML after each edit
|
||||
- 🎭 Handle sidecar structure if hasSidecar: true
|
||||
- ➡️ Auto-advance to celebration when complete
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Load template, architecture, and validation files
|
||||
- 📊 Read editPlan to get all planned changes
|
||||
- 💾 Create backup
|
||||
- 📝 Apply edits: sidecar conversion, metadata, persona, commands, critical_actions
|
||||
- 🎭 Manage sidecar folder structure (if applicable)
|
||||
- ✅ Validate YAML and sidecar paths
|
||||
- ➡️ Auto-advance to next step
|
||||
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
Read all files before editing:
|
||||
- `{agentTemplate}` - YAML structure reference
|
||||
- `{agentArch}` - Agent architecture (with/without sidecar)
|
||||
- `{agentValidation}` - Validation checklist
|
||||
- `{agentCompilation}` - Assembly guidelines
|
||||
- `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
|
||||
- `{agentMenuPatterns}`, `{criticalActions}`
|
||||
|
||||
### 2. Load Edit Plan and Agent
|
||||
|
||||
Read `{editPlan}` to get all planned edits.
|
||||
Read `{agentFile}` to get current agent YAML.
|
||||
|
||||
Check the `hasSidecar` value from editPlan to determine edit approach.
|
||||
|
||||
### 3. Create Backup
|
||||
|
||||
ALWAYS backup before editing:
|
||||
```bash
|
||||
cp {agentFile} {agentBackup}
|
||||
```
|
||||
|
||||
Confirm: "Backup created at: `{agentBackup}`"
|
||||
|
||||
### 4. Apply Edits in Sequence
|
||||
|
||||
For each planned edit:
|
||||
|
||||
**Sidecar Conversion:**
|
||||
|
||||
**false → true (Adding sidecar):**
|
||||
- Set `hasSidecar: true`
|
||||
- Add `metadata.sidecar-folder` if not present
|
||||
- Add `critical_actions` section with sidecar file references
|
||||
- Create sidecar directory: `{agent-folder}/{agent-name}-sidecar/`
|
||||
- Create starter files: `memories.md`, `instructions.md`
|
||||
- Update all references to use `{project-root}/_bmad/_memory/{sidecar-folder}/` format
|
||||
|
||||
**true → false (Removing sidecar):**
|
||||
- Set `hasSidecar: false`
|
||||
- Remove `metadata.sidecar-folder` and `metadata.sidecar-path`
|
||||
- If critical_actions contains only sidecar references, remove the section
|
||||
- If critical_actions contains non-sidecar activation behaviors, keep and clean sidecar references
|
||||
- Remove sidecar references from menu actions
|
||||
- Optionally archive sidecar folder
|
||||
|
||||
**Metadata Edits:**
|
||||
- Apply each field change from metadataEdits
|
||||
- Validate format conventions
|
||||
|
||||
**Persona Edits:**
|
||||
- Replace persona section with new four-field persona
|
||||
- Validate field purity (role ≠ identity ≠ communication_style)
|
||||
- For hasSidecar: true, ensure communication_style includes memory reference patterns
|
||||
|
||||
**Command Edits:**
|
||||
- Additions: append to commands array
|
||||
- Modifications: update specific commands
|
||||
- Removals: remove from commands array
|
||||
|
||||
**Critical Actions Edits (hasSidecar: true only):**
|
||||
- Additions: append to critical_actions array
|
||||
- Modifications: update specific actions
|
||||
- Removals: remove from array
|
||||
- Ensure all references use correct `{project-root}/_bmad/_memory/` paths
|
||||
|
||||
### 5. Validate After Each Edit
|
||||
|
||||
**For both types:**
|
||||
- Confirm YAML syntax is valid after each modification
|
||||
|
||||
**For hasSidecar: true:**
|
||||
- Validate sidecar path format
|
||||
- Ensure all critical_actions reference correct paths
|
||||
- Confirm sidecar folder structure exists
|
||||
|
||||
### 6. Document Applied Edits
|
||||
|
||||
Append to `{editPlan}`:
|
||||
|
||||
```yaml
|
||||
editsApplied:
|
||||
- {edit-description}
|
||||
- {edit-description}
|
||||
backup: {agentBackup}
|
||||
timestamp: {YYYY-MM-DD HH:MM}
|
||||
```
|
||||
|
||||
### 7. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
|
||||
- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
|
||||
- IF C: Save 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](#7-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 [all edits applied and validated], will you then load and read fully `{nextStepFile}` to execute and celebrate.
|
||||
|
||||
---
|
||||
|
||||
## SUCCESS METRICS
|
||||
|
||||
✅ Backup created
|
||||
✅ All reference files loaded
|
||||
✅ All edits applied correctly
|
||||
✅ YAML remains valid
|
||||
✅ Sidecar structure correct (if hasSidecar: true)
|
||||
✅ Sidecar paths validated (if hasSidecar: true)
|
||||
✅ Edit plan tracking updated
|
||||
|
||||
## FAILURE MODES
|
||||
|
||||
❌ Backup failed
|
||||
❌ YAML became invalid
|
||||
❌ Sidecar paths broken (hasSidecar: true)
|
||||
❌ Edits not applied as specified
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to celebration when complete...**
|
||||
@@ -1,134 +0,0 @@
|
||||
---
|
||||
name: 'e-08a-edit-simple'
|
||||
description: 'Apply edits to Simple agent'
|
||||
|
||||
nextStepFile: './e-09a-validate-metadata.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentFile: '{original-agent-path}'
|
||||
agentBackup: '{original-agent-path}.backup'
|
||||
|
||||
# Template and Architecture
|
||||
simpleTemplate: ../templates/simple-agent.template.md
|
||||
simpleArch: ../data/simple-agent-architecture.md
|
||||
agentCompilation: ../data/agent-compilation.md
|
||||
agentMetadata: ../data/agent-metadata.md
|
||||
personaProperties: ../data/persona-properties.md
|
||||
principlesCrafting: ../data/principles-crafting.md
|
||||
agentMenuPatterns: ../data/agent-menu-patterns.md
|
||||
criticalActions: ../data/critical-actions.md
|
||||
---
|
||||
|
||||
# Edit Step 8a: Edit Simple Agent
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply all planned edits to the Simple agent YAML file using templates and architecture references for validation.
|
||||
|
||||
## MANDATORY EXECUTION RULES:
|
||||
|
||||
- 🛑 ALWAYS create backup before modifying agent file
|
||||
- 📖 CRITICAL: Read template and architecture files first
|
||||
- 🔄 CRITICAL: Load editPlan and agentFile
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Load all reference files before applying edits
|
||||
- 📊 Apply edits exactly as specified in editPlan
|
||||
- 💾 Validate YAML after each edit
|
||||
- ➡️ Auto-advance to post-edit validation when complete
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Load template, architecture, and data files
|
||||
- 📊 Read editPlan to get all planned changes
|
||||
- 💾 Create backup
|
||||
- 📝 Apply edits: type conversion, metadata, persona, commands, critical_actions
|
||||
- ✅ Validate YAML syntax
|
||||
- ➡️ Auto-advance to next validation step
|
||||
|
||||
## Sequence of Instructions:
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
Read all files before editing:
|
||||
- `{simpleTemplate}` - YAML structure reference
|
||||
- `{simpleArch}` - Simple agent architecture
|
||||
- `{agentCompilation}` - Assembly guidelines
|
||||
- `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
|
||||
- `{agentMenuPatterns}`, `{criticalActions}`
|
||||
|
||||
### 2. Load Edit Plan and Agent
|
||||
|
||||
Read `{editPlan}` to get all planned edits.
|
||||
Read `{agentFile}` to get current agent YAML.
|
||||
|
||||
### 3. Create Backup
|
||||
|
||||
ALWAYS backup before editing:
|
||||
`cp {agentFile} {agentBackup}`
|
||||
|
||||
Confirm: "Backup created at: `{agentBackup}`"
|
||||
|
||||
### 4. Apply Edits in Sequence
|
||||
|
||||
For each planned edit:
|
||||
|
||||
**Type Conversion:**
|
||||
- Update `type:` field if converting
|
||||
- Add/remove type-specific fields
|
||||
|
||||
**Metadata Edits:**
|
||||
- Apply each field change from metadataEdits
|
||||
|
||||
**Persona Edits:**
|
||||
- Replace persona section with new four-field persona
|
||||
- Validate field purity (role ≠ identity ≠ communication_style)
|
||||
|
||||
**Command Edits:**
|
||||
- Additions: append to commands array
|
||||
- Modifications: update specific commands
|
||||
- Removals: remove from commands array
|
||||
|
||||
**Critical Actions Edits:**
|
||||
- Additions: append to critical_actions array
|
||||
- Modifications: update specific actions
|
||||
- Removals: remove from array
|
||||
|
||||
### 5. Validate YAML After Each Edit
|
||||
|
||||
Confirm YAML syntax is valid after each modification.
|
||||
|
||||
### 6. Document Applied Edits
|
||||
|
||||
Append to `{editPlan}`:
|
||||
|
||||
```yaml
|
||||
editsApplied:
|
||||
- {edit-description}
|
||||
- {edit-description}
|
||||
backup: {agentBackup}
|
||||
timestamp: {YYYY-MM-DD HH:MM}
|
||||
```
|
||||
|
||||
### 7. Auto-Advance
|
||||
|
||||
When all edits applied successfully, load and execute `{nextStepFile}` immediately.
|
||||
|
||||
## SUCCESS METRICS
|
||||
|
||||
✅ Backup created
|
||||
✅ All reference files loaded
|
||||
✅ All edits applied correctly
|
||||
✅ YAML remains valid
|
||||
✅ Edit plan tracking updated
|
||||
|
||||
## FAILURE MODES
|
||||
|
||||
❌ Backup failed
|
||||
❌ YAML became invalid
|
||||
❌ Edits not applied as specified
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to post-edit validation...
|
||||
@@ -1,117 +0,0 @@
|
||||
---
|
||||
name: 'e-08b-edit-expert'
|
||||
description: 'Apply edits to Expert agent'
|
||||
|
||||
nextStepFile: './e-09a-validate-metadata.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentFile: '{original-agent-path}'
|
||||
agentBackup: '{original-agent-path}.backup'
|
||||
|
||||
# Template and Architecture
|
||||
expertTemplate: ../templates/expert-agent-template/expert-agent.template.md
|
||||
expertArch: ../data/expert-agent-architecture.md
|
||||
agentCompilation: ../data/agent-compilation.md
|
||||
agentMetadata: ../data/agent-metadata.md
|
||||
personaProperties: ../data/persona-properties.md
|
||||
principlesCrafting: ../data/principles-crafting.md
|
||||
agentMenuPatterns: ../data/agent-menu-patterns.md
|
||||
criticalActions: ../data/critical-actions.md
|
||||
expertValidation: ../data/expert-agent-validation.md
|
||||
---
|
||||
|
||||
# Edit Step 8b: Edit Expert Agent
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply all planned edits to the Expert agent YAML file and manage sidecar structure changes.
|
||||
|
||||
## MANDATORY EXECUTION RULES:
|
||||
|
||||
- 🛑 ALWAYS create backup before modifying agent file
|
||||
- 📖 CRITICAL: Read template and architecture files first
|
||||
- 🔄 CRITICAL: Load editPlan and agentFile
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Load all reference files before applying edits
|
||||
- 📊 Manage sidecar structure for Expert agents
|
||||
- 💾 Validate YAML and sidecar paths after edits
|
||||
- ➡️ Auto-advance to post-edit validation when complete
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Load template, architecture, and data files
|
||||
- 📊 Read editPlan to get all planned changes
|
||||
- 💾 Create backup
|
||||
- 📝 Apply edits including sidecar management
|
||||
- ✅ Validate YAML and sidecar paths
|
||||
- ➡️ Auto-advance to next validation step
|
||||
|
||||
## Sequence of Instructions:
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
Read all files before editing:
|
||||
- `{expertTemplate}` - Expert YAML structure
|
||||
- `{expertArch}` - Expert agent architecture
|
||||
- `{agentCompilation}`, `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
|
||||
- `{agentMenuPatterns}`, `{criticalActions}`, `{expertValidation}`
|
||||
|
||||
### 2. Load Edit Plan and Agent
|
||||
|
||||
Read `{editPlan}` to get all planned edits.
|
||||
Read `{agentFile}` to get current agent YAML.
|
||||
|
||||
### 3. Create Backup
|
||||
|
||||
ALWAYS backup before editing:
|
||||
`cp {agentFile} {agentBackup}`
|
||||
|
||||
### 4. Apply Edits in Sequence
|
||||
|
||||
**Type Conversion to Expert:**
|
||||
- Update `type: expert`
|
||||
- Add `metadata.sidecar-folder` if not present
|
||||
- Create sidecar directory: `mkdir -p {project-root}/_bmad/_memory/{sidecar-folder}/`
|
||||
|
||||
**Sidecar Management:**
|
||||
- If changing sidecar-folder: update all critical_actions references
|
||||
- If removing sidecar (Expert → Simple): remove sidecar fields and folder
|
||||
- Create/update sidecar files as needed
|
||||
|
||||
**Metadata, Persona, Commands, Critical Actions:**
|
||||
- Same as Simple agent edit
|
||||
|
||||
### 5. Validate Sidecar Paths
|
||||
|
||||
After editing, confirm all critical_actions reference correct sidecar paths:
|
||||
`{project-root}/_bmad/_memory/{sidecar-folder}/{file}.md`
|
||||
|
||||
### 6. Document Applied Edits
|
||||
|
||||
Append to `{editPlan}` with sidecar changes noted.
|
||||
|
||||
### 7. Auto-Advance
|
||||
|
||||
When all edits applied successfully, load and execute `{nextStepFile}` immediately.
|
||||
|
||||
## SUCCESS METRICS
|
||||
|
||||
✅ Backup created
|
||||
✅ All reference files loaded
|
||||
✅ All edits applied correctly
|
||||
✅ YAML remains valid
|
||||
✅ Sidecar structure correct
|
||||
✅ Sidecar paths validated
|
||||
|
||||
## FAILURE MODES
|
||||
|
||||
❌ Backup failed
|
||||
❌ YAML became invalid
|
||||
❌ Sidecar paths broken
|
||||
❌ Edits not applied as specified
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to post-edit validation...
|
||||
@@ -1,120 +0,0 @@
|
||||
---
|
||||
name: 'e-08c-edit-module'
|
||||
description: 'Apply edits to Module agent'
|
||||
|
||||
nextStepFile: './e-09a-validate-metadata.md'
|
||||
editPlan: '{bmb_creations_output_folder}/edit-plan-{agent-name}.md'
|
||||
agentFile: '{original-agent-path}'
|
||||
agentBackup: '{original-agent-path}.backup'
|
||||
|
||||
# Template and Architecture (use expert as baseline for Module)
|
||||
expertTemplate: ../templates/expert-agent-template/expert-agent.template.md
|
||||
expertArch: ../data/expert-agent-architecture.md
|
||||
moduleArch: ../data/module-agent-validation.md
|
||||
agentCompilation: ../data/agent-compilation.md
|
||||
agentMetadata: ../data/agent-metadata.md
|
||||
personaProperties: ../data/persona-properties.md
|
||||
principlesCrafting: ../data/principles-crafting.md
|
||||
agentMenuPatterns: ../data/agent-menu-patterns.md
|
||||
criticalActions: ../data/critical-actions.md
|
||||
---
|
||||
|
||||
# Edit Step 8c: Edit Module Agent
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Apply all planned edits to the Module agent YAML file and manage workflow integration and sidecar structure.
|
||||
|
||||
## MANDATORY EXECUTION RULES:
|
||||
|
||||
- 🛑 ALWAYS create backup before modifying agent file
|
||||
- 📖 CRITICAL: Read template and architecture files first
|
||||
- 🔄 CRITICAL: Load editPlan and agentFile
|
||||
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||||
|
||||
### Step-Specific Rules:
|
||||
|
||||
- 🎯 Load all reference files before applying edits
|
||||
- 📊 Manage workflow integration paths for Module agents
|
||||
- 💾 Validate YAML and workflow paths after edits
|
||||
- ➡️ Auto-advance to post-edit validation when complete
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Load template, architecture, and data files
|
||||
- 📊 Read editPlan to get all planned changes
|
||||
- 💾 Create backup
|
||||
- 📝 Apply edits including workflow paths
|
||||
- ✅ Validate YAML and workflow paths
|
||||
- ➡️ Auto-advance to next validation step
|
||||
|
||||
## Sequence of Instructions:
|
||||
|
||||
### 1. Load Reference Documents
|
||||
|
||||
Read all files before editing:
|
||||
- `{expertTemplate}` - Module uses expert as baseline
|
||||
- `{expertArch}`, `{moduleArch}` - Architecture references
|
||||
- `{agentCompilation}`, `{agentMetadata}`, `{personaProperties}`, `{principlesCrafting}`
|
||||
- `{agentMenuPatterns}`, `{criticalActions}`
|
||||
|
||||
### 2. Load Edit Plan and Agent
|
||||
|
||||
Read `{editPlan}` to get all planned edits.
|
||||
Read `{agentFile}` to get current agent YAML.
|
||||
|
||||
### 3. Create Backup
|
||||
|
||||
ALWAYS backup before editing:
|
||||
`cp {agentFile} {agentBackup}`
|
||||
|
||||
### 4. Apply Edits in Sequence
|
||||
|
||||
**Type Conversion to Module:**
|
||||
- Update `type: module`
|
||||
- Add workflow integration paths
|
||||
|
||||
**Workflow Path Management:**
|
||||
- Add: `skills: - workflow: {path}`
|
||||
- Remove: delete workflow entries
|
||||
- Modify: update workflow paths
|
||||
|
||||
**Sidecar for Multi-Workflow Modules:**
|
||||
- If 3+ workflows: consider sidecar creation
|
||||
- Add sidecar configuration if needed
|
||||
|
||||
**Metadata, Persona, Commands, Critical Actions:**
|
||||
- Same as Expert agent edit
|
||||
|
||||
### 5. Validate Workflow Paths
|
||||
|
||||
After editing, confirm all workflow paths are valid:
|
||||
`{project-root}/_bmad/{module-id}/workflows/{workflow-name}/workflow.md`
|
||||
|
||||
### 6. Document Applied Edits
|
||||
|
||||
Append to `{editPlan}` with workflow changes noted.
|
||||
|
||||
### 7. Auto-Advance
|
||||
|
||||
When all edits applied successfully, load and execute `{nextStepFile}` immediately.
|
||||
|
||||
## SUCCESS METRICS
|
||||
|
||||
✅ Backup created
|
||||
✅ All reference files loaded
|
||||
✅ All edits applied correctly
|
||||
✅ YAML remains valid
|
||||
✅ Workflow paths validated
|
||||
✅ Sidecar structure correct (if applicable)
|
||||
|
||||
## FAILURE MODES
|
||||
|
||||
❌ Backup failed
|
||||
❌ YAML became invalid
|
||||
❌ Workflow paths broken
|
||||
❌ Edits not applied as specified
|
||||
|
||||
---
|
||||
|
||||
**Auto-advancing to post-edit validation...
|
||||
+13
-8
@@ -1,14 +1,15 @@
|
||||
---
|
||||
name: 'e-10-celebrate'
|
||||
name: 'e-09-celebrate'
|
||||
description: 'Celebrate successful agent edit completion'
|
||||
|
||||
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'
|
||||
validationWorkflow: '{project-root}/src/modules/bmb/workflows/agent/steps-v/v-01-load-review.md'
|
||||
---
|
||||
|
||||
# Edit Step 10: Celebration
|
||||
# Edit Step 9: Celebration
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
@@ -48,7 +49,9 @@ Celebrate the successful agent edit, provide summary of changes, and mark edit w
|
||||
- Limits: No more edits, only acknowledgment
|
||||
- Dependencies: All edits successfully applied
|
||||
|
||||
## Sequence of Instructions:
|
||||
## MANDATORY SEQUENCE
|
||||
|
||||
**CRITICAL:** Follow this sequence exactly. Do not skip, reorder, or improvise unless user explicitly requests a change.:
|
||||
|
||||
### 1. Read Edit Plan
|
||||
|
||||
@@ -110,24 +113,26 @@ Append to editPlan:
|
||||
|
||||
### 6. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [X] Exit Workflow"
|
||||
Display: "**✅ Agent Edit Complete! Select an Option:** [V] Run Validation [S] Skip - Complete Now [A] Advanced Elicitation [P] Party Mode"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF V: "Loading validation phase..." → Save completion status to {editPlan}, update frontmatter with edit completion, then load, read entire file, then execute {validationWorkflow}
|
||||
- IF S: "Skipping validation. Completing workflow..." → Save completion status to {editPlan} and end workflow gracefully
|
||||
- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
|
||||
- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
|
||||
- IF X: Save completion status to {editPlan} and end workflow gracefully
|
||||
- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
|
||||
|
||||
#### EXECUTION RULES:
|
||||
|
||||
- ALWAYS halt and wait for user input after presenting menu
|
||||
- ONLY complete workflow when user selects 'X'
|
||||
- After other menu items execution, return to this menu
|
||||
- User can choose validation (V), skip to complete (S), or use advanced elicitation (A) or party mode (P)
|
||||
- After other menu items execution (A/P), return to this menu
|
||||
|
||||
## CRITICAL STEP COMPLETION NOTE
|
||||
|
||||
ONLY WHEN [X exit option] is selected and [completion documented], will the workflow end gracefully with agent edit complete.
|
||||
ONLY WHEN [S skip option] is selected and [completion documented], will the workflow end gracefully with agent edit complete.
|
||||
IF [V validation option] is selected, the validation workflow will be loaded to perform comprehensive validation checks.
|
||||
|
||||
---
|
||||
|
||||
@@ -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...**
|
||||
@@ -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...**
|
||||
@@ -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...**
|
||||
@@ -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...**
|
||||
@@ -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...**
|
||||
@@ -1,111 +0,0 @@
|
||||
---
|
||||
name: 'e-09f-validation-summary'
|
||||
description: 'Display all validation findings after edit'
|
||||
|
||||
nextStepFile: './e-10-celebrate.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 9f: Validation Summary (After Edit)
|
||||
|
||||
## STEP GOAL:
|
||||
|
||||
Display all post-edit validation findings and compare with pre-edit state. Present findings and await confirmation to proceed to celebration.
|
||||
|
||||
## 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
|
||||
- 📊 Compare before/after states
|
||||
- 💬 Present options for handling any remaining issues
|
||||
|
||||
## EXECUTION PROTOCOLS:
|
||||
|
||||
- 🎯 Read editPlan to get validation findings
|
||||
- 📊 Display organized summary with before/after comparison
|
||||
- 💾 Allow user to decide how to proceed
|
||||
|
||||
## Sequence of Instructions:
|
||||
|
||||
### 1. Load Validation Findings
|
||||
|
||||
Read `{editPlan}` frontmatter to collect validationBefore and validationAfter findings.
|
||||
|
||||
### 2. Display Validation Summary
|
||||
|
||||
```markdown
|
||||
## Post-Edit Validation Report for {agent-name}
|
||||
|
||||
### Before vs After Comparison
|
||||
|
||||
| Component | Before | After | Status |
|
||||
|-----------|--------|-------|--------|
|
||||
| Metadata | {status} | {status} | {Δ} |
|
||||
| Persona | {status} | {status} | {Δ} |
|
||||
| Menu | {status} | {status} | {Δ} |
|
||||
| Structure | {status} | {status} | {Δ} |
|
||||
| Sidecar | {status} | {status} | {Δ} |
|
||||
|
||||
### Detailed Findings (After Edit)
|
||||
|
||||
**Metadata:** {summary}
|
||||
**Persona:** {summary}
|
||||
**Menu:** {summary}
|
||||
**Structure:** {summary}
|
||||
**Sidecar:** {summary}
|
||||
```
|
||||
|
||||
### 3. Present Options
|
||||
|
||||
"How do the edits look?
|
||||
|
||||
**[R]eview** - Show detailed before/after for any component
|
||||
**[F]ix** - Address any remaining issues
|
||||
**[A]ccept** - Proceed to celebration"
|
||||
|
||||
### 4. Present MENU OPTIONS
|
||||
|
||||
Display: "**Select an Option:** [A] Advanced Elicitation [P] Party Mode [C] Continue to Celebration"
|
||||
|
||||
#### Menu Handling Logic:
|
||||
|
||||
- IF A: Execute {advancedElicitationTask}, and when finished redisplay the menu
|
||||
- IF P: Execute {partyModeWorkflow}, and when finished redisplay the menu
|
||||
- IF R: Show detailed before/after comparison, 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 celebrate completion.
|
||||
|
||||
---
|
||||
|
||||
## 🚨 SYSTEM SUCCESS/FAILURE METRICS
|
||||
|
||||
### ✅ SUCCESS:
|
||||
|
||||
- All validation findings displayed clearly
|
||||
- Before/after comparison shown
|
||||
- User given options for handling issues
|
||||
|
||||
### ❌ 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.
|
||||
Reference in new issue
Block a user