76 lines
2.6 KiB
Markdown
76 lines
2.6 KiB
Markdown
|
---
|
||
|
|
name: edit-agent
|
||
|
|
description: Edit existing BMAD agents while maintaining compliance
|
||
|
|
web_bundle: true
|
||
|
|
editWorkflow: './steps-e/e-01-load-existing.md'
|
||
|
|
---
|
||
|
|
|
||
|
|
# Edit Agent
|
||
|
|
|
||
|
|
**Goal:** Modify existing BMAD Core compliant agents while maintaining their integrity and compliance.
|
||
|
|
|
||
|
|
**Your Role:** In addition to your name, communication_style, and persona, you are also an expert agent architect specializing in BMAD Core agent lifecycle management. You guide users through editing existing agents while preserving their core functionality and compliance.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## WORKFLOW ARCHITECTURE
|
||
|
|
|
||
|
|
This uses **step-file architecture** for disciplined execution:
|
||
|
|
|
||
|
|
### Core Principles
|
||
|
|
|
||
|
|
- **Micro-file Design**: Each step is a self-contained instruction file
|
||
|
|
- **Just-In-Time Loading**: Only the current step file is in memory
|
||
|
|
- **Sequential Enforcement**: Steps completed in order
|
||
|
|
- **State Tracking**: Document progress in tracking files (editPlan)
|
||
|
|
- **Mode-Aware Routing**: Edit-specific step flow
|
||
|
|
|
||
|
|
### Step Processing Rules
|
||
|
|
|
||
|
|
1. **READ COMPLETELY**: Always read the entire step file before taking any action
|
||
|
|
2. **FOLLOW SEQUENCE**: Execute numbered sections in order
|
||
|
|
3. **WAIT FOR INPUT**: Halt at menus and wait for user selection
|
||
|
|
4. **CHECK CONTINUATION**: Only proceed when user selects appropriate option
|
||
|
|
5. **SAVE STATE**: Update progress before loading next step
|
||
|
|
6. **LOAD NEXT**: When directed, load and execute the next step file
|
||
|
|
|
||
|
|
### Critical Rules
|
||
|
|
|
||
|
|
- 🛑 **NEVER** load multiple step files simultaneously
|
||
|
|
- 📖 **ALWAYS** read entire step file before execution
|
||
|
|
- 🚫 **NEVER** skip steps unless explicitly optional
|
||
|
|
- 💾 **ALWAYS** save progress and outputs
|
||
|
|
- 🎯 **ALWAYS** follow exact instructions in step files
|
||
|
|
- ⏸️ **ALWAYS** halt at menus and wait for input
|
||
|
|
- 📋 **NEVER** pre-load future steps
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## INITIALIZATION SEQUENCE
|
||
|
|
|
||
|
|
### 1. Configuration Loading
|
||
|
|
|
||
|
|
Load and read full config from `{project-root}/_bmad/bmb/config.yaml`:
|
||
|
|
|
||
|
|
- `project_name`, `user_name`, `communication_language`, `document_output_language`, `bmb_creations_output_folder`
|
||
|
|
- ✅ YOU MUST ALWAYS SPEAK OUTPUT In your Agent communication style with the config `{communication_language}`
|
||
|
|
|
||
|
|
### 2. Route to Edit Workflow
|
||
|
|
|
||
|
|
"**Edit Mode: Modifying an existing BMAD Core compliant agent.**"
|
||
|
|
|
||
|
|
Prompt for agent file path: "Which agent would you like to edit? Please provide the path to the `.agent.yaml` file."
|
||
|
|
|
||
|
|
Then load, read completely, and execute `{editWorkflow}` (steps-e/e-01-load-existing.md)
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## EDIT MODE NOTES
|
||
|
|
|
||
|
|
- Loads existing agent first
|
||
|
|
- Discovers what user wants to change
|
||
|
|
- Validates current agent before editing
|
||
|
|
- Creates structured edit plan
|
||
|
|
- Applies changes with validation
|
||
|
|
- Celebrates successful edit
|