managing-agents

# Managing Orchestration Agents

I manage the lifecycle of agents in the orchestration system: creation, execution, promotion, and cleanup.

## When I Activate

I automatically activate when you:
- Create or define custom agents
- Ask about agent lifecycle
- Mention temp agents or agent promotion
- Want to understand agent namespacing
- Ask "how do I create an agent?"

## Agent Types

### Built-in Agents

**No namespace prefix**, always available:
- `Explore` - Codebase exploration
- `general-purpose` - General-purpose tasks
- `code-reviewer` - Code review
- `implementation-architect` - Architecture planning
- `expert-code-implementer` - Code implementation

### Plugin Defined Agents

**With `orchestration:` prefix**, permanent agents in this plugin:
- `orchestration:workflow-socratic-designer`
- `orchestration:workflow-syntax-designer`
- Custom agents you promote

Located in: `agents/` directory
Registry: `agents/registry.json`

### Temp Agents

**With `orchestration:` prefix**, workflow-specific ephemeral agents:
- Created during workflow design
- Saved in `temp-agents/` directory
- Auto-cleaned after workflow execution
- Can be promoted to permanent

Reference in workflows: `$agent-name`

## Temp Agent Lifecycle

See [temp-agents.md](temp-agents.md) for complete guide.

### 1. Creation

Created automatically during workflow design:

```markdown
---
name: security-scanner
description: Scans for security vulnerabilities
created: 2025-01-08
---

You are a security expert specializing in vulnerability detection...
```

Saved to: `temp-agents/security-scanner.md`

### 2. Execution

Referenced in workflow with `$` prefix:

```flow
$security-scanner:"Scan codebase":findings ->
general-purpose:"Analyze {findings}"
```

Executed with namespace: `orchestration:security-scanner`

### 3. Promotion

After workflow completion, you can save temp agents:

```
Workflow complete!

Temp agents created:
  - security-scanner
  - performance-profiler

Save as permanent agents? [Y/n]
`