AGENT_FORMAT

Agent Definition Format

This document defines the canonical structure for critic/architecture agents in .claude/agents/.

File Structure

All agent definition files must follow this structure:

---
name: agent-name
description: One-line description of agent's purpose
model: sonnet
color: blue|green|yellow|orange|purple|red|cyan|pink
tools: Read, Glob, Grep, Skill
skills: code:find-plugin-file
---

## Execution Modes

- **Critic (default fast mode):** Brief description of critic mode behavior

## Inputs

### Critic mode

- List of required input files
- Include standard files: requirements.json, code-map.json, implementation-plan.draft.md, anchors.json, critic-selection.json
- Include domain-specific files

## Outputs

### Critic mode

Write to `reviews/[agent-name].review.json` conforming to `review-delta.schema.json` (use `code:find-plugin-file` skill to locate `schemas/review-delta.schema.json`).

**Note:** The schema accepts both `items` and `review_items` as field names. The `agent` and `mode` fields are optional.

**Example structure:**

```json
{
  "review_items": [
    {
      "anchor_id": "task:example-task",
      "severity": "blocking|major|minor",
      "rationale": "Concrete, domain-specific explanation with evidence",
      "proposed_change": {
        "op": "insert|append|replace",
        "target": "task",
        "path": "task:example-task",
        "value": "Specific enhancement with domain expertise"
      },
      "files": ["path/to/relevant/file.tsx"],
      "ac_refs": ["AC-001"],
      "tags": ["domain-tag-1", "domain-tag-2"]
    }
  ]
}
```

Budget constraints:

• Review budget from critic-selection.json
• Severity ordering: blocking → major → minor
• Drop minor items if over budget

Quality requirements:

• All anchor_id values must exist in anchors.json
• Every item references specific files
• Rationale cites concrete evidence (code patterns, metrics, risks)
• Proposed changes are actionable and domain-specific