Skip to content
🤖 AI-optimized docs: llms-full.txt

Edit Agents and Workflows

Modify existing agents and workflows using the builder’s edit workflows, which help you make changes while maintaining compliance with best practices.

  • Have an existing agent or workflow you want to modify
  • Understand what changes you want to make
  • Completed the relevant creation tutorial (agent or workflow)

Use Wendy’s edit workflow for comprehensive workflow modifications:

[EW] or "edit-workflow"

Wendy will guide you through:

StepWhat Happens
AssessLoad and review the existing workflow
DiscoverDescribe what changes you want
SelectChoose which parts to modify (steps, menus, frontmatter)
ApplyMake the changes
ValidateCheck for compliance issues
ElementDescription
FrontmatterName, description, goal, configuration
StepsAdd, remove, or modify step files
MenusChange menu options and handlers
TemplatesUpdate output templates
DataModify reference materials

The edit workflow can convert non-compliant workflows to BMad format:

Detection: Edit mode assesses workflow compliance first

  • Compliant → Continue to edit steps
  • Non-compliant → Offer conversion to step-00-conversion

Conversion process:

  1. Load non-compliant workflow
  2. Extract essence and structure
  3. Create plan with conversionFrom metadata
  4. Build compliant workflow
  5. Verify coverage of original functionality

For complex workflows with create/edit/validate modes, edit mode handles cross-mode integration:

Edit to Create: Route to conversion for non-compliant input Edit to Validation: After edits, offer to run validation Validation to Edit: Validation reports consumed by edit mode for fixes

Workflows are markdown files. You can edit directly:

---
name: my-workflow
description: My workflow description
# Edit frontmatter here
---
# Workflow content here

After editing, validate your workflow:

[VW] or "validate-workflow"

To add a step to an existing workflow:

  1. Create new step file: step-XX-new-step.md
  2. Update the previous step to load the new step
  3. Set the new step’s nextStepFile to continue the sequence
  4. Validate the workflow

When adding steps, consider the step type:

Step TypeWhen to UseMenu Pattern
InitStarting a new workflow phaseAuto-proceed
MiddleCollaborative content creationA/P/C or C only
BranchUser choice determines pathCustom letters
FinalCompleting the workflowNo menu

To replace a step entirely:

  1. Create replacement step file with same or new name
  2. Update previous step’s nextStepFile to load replacement
  3. Remove or archive old step file
  4. Validate the workflow

When a step exceeds 200-250 lines, extract content to /data/ files.

Good candidates for extraction:

  • Domain-specific reference materials
  • Reusable patterns or examples
  • Configuration data
  • Large lookup tables

Bond’s edit workflow helps you modify agents while maintaining compliance:

[EA] or "edit-agent"

Bond will guide you through:

StepWhat Happens
LoadSelect the agent file to edit
DiscoverDescribe what changes you want
SelectChoose which elements to modify
ApplyMake the changes with validation
CelebrateReview and confirm
ElementDescription
PersonaRole, identity, communication style, principles
Menu CommandsAdd, remove, or modify commands
Critical ActionsAutonomous behaviors
MetadataName, description, version
SidecarExpert agent memory files

For simple changes, you can edit the agent YAML file directly:

agent:
metadata:
name: "My Agent"
# Edit metadata here
persona:
role: "What they do"
# Edit persona fields here
menu:
- trigger: "my-command"
# Edit commands here

After editing, rebuild the agent:

Terminal window
npx bmad-method build <agent-name>

For module-level changes (configuration, install questions), use Morgan’s edit workflow:

[EM] or "edit-module"

This guides you through:

  • Modifying module.yaml
  • Updating install questions
  • Changing configuration values

Always validate after making changes:

Content TypeValidation Command
Agents[VA] or validate-agent
Workflows[VW] or validate-workflow
Modules[VM] or validate-module

For high-capability LLMs (like Claude):

[MV] or "validate-max-parallel-workflow"

This hyper-optimized validation uses task agents to validate multiple workflow aspects simultaneously in sub-processes for dramatically faster results.

Validation checks for:

  • Proper YAML formatting
  • Required fields are present
  • Compliance with BMad standards
  • Menu and command structure
  • Frontmatter variable usage
  • Step file size limits
  1. Run [EA] or open the agent YAML file
  2. Add to the menu section:
menu:
- trigger: "new-command"
exec: "path/to/workflow.md"
description: "What this command does"
  1. Rebuild or validate
  1. Run [EW] or open the workflow
  2. Create new step file: step-XX-new-step.md
  3. Update the previous step to load the new step
  4. Validate the workflow
  1. Run [EW] or [RW] (rework)
  2. Edit mode detects non-compliance
  3. Accept conversion offer
  4. Review conversion plan
  5. Build compliant workflow
  6. Verify coverage
TipWhy
Validate oftenCatch issues early
Test changesVerify behavior matches expectations
Backup firstKeep a copy before major edits
IterateMake small changes and test
DocumentNote why you made changes
GuideDescription
Validate Agents and WorkflowsQuality assurance
Create a Custom AgentCreating agents
Create Your First WorkflowCreating workflows
Workflow CustomizationTri-modal structure and patterns