# Template: Categorized Agent

Use this template for agents that belong to a category subdirectory (e.g., efcore/, gitflow/).

## Generated agent file format:

```yaml
---
name: {{AGENT_NAME}}
description: {{DESCRIPTION}}
{{#if MODEL}}
model: {{MODEL}}
{{/if}}
{{#if TOOLS}}
tools: "{{TOOLS}}"
{{/if}}
{{#if DISALLOWED_TOOLS}}
disallowedTools: "{{DISALLOWED_TOOLS}}"
{{/if}}
{{#if PERMISSION_MODE}}
permissionMode: {{PERMISSION_MODE}}
{{/if}}
{{#if COLOR}}
color: {{COLOR}}
{{/if}}
---

{{SYSTEM_PROMPT}}

## Context: {{CATEGORY}}

This agent is part of the **{{CATEGORY}}** agent group, specialized for {{CATEGORY_PURPOSE}}.

## Workflow

1. **{{STEP_1_NAME}}**: {{STEP_1_DESC}}
2. **{{STEP_2_NAME}}**: {{STEP_2_DESC}}
3. **{{STEP_3_NAME}}**: {{STEP_3_DESC}}

## Execution Rules

- {{RULE_1}}
- {{RULE_2}}
- {{RULE_3}}

## Output Format

{{OUTPUT_FORMAT_DESCRIPTION}}
```

## File Location:
- Project: `.claude/agents/{category}/{name}.md`
- Global: `~/.claude/agents/{category}/{name}.md`
- Templates: `templates/agents/{category}/{name}.md`

## Category Examples:
| Category | Purpose | Agents |
|----------|---------|--------|
| `efcore` | EF Core database operations | migration, db-status, db-deploy, conflicts |
| `gitflow` | Git workflow management | commit, merge, plan, finish, status |
| `testing` | Test execution and validation | unit-tests, integration-tests, coverage |

## Notes:
- Category directories group related agents together
- Agents within a category often share similar tool requirements
- Category name should be lowercase, descriptive
- Each agent in the category should have a distinct, non-overlapping purpose
