agent-patterns

# Agent Patterns ## Overview Agent Patterns defines the coordination protocol for multi-agent sprint execution within the Sprint plugin. It governs how the project architect spawns implementation and testing agents, how agents communicate results via structured reports, and how parallel agents avoid conflicts. ## Prerequisites - Sprint plugin installed and configured (`/plugin install sprint`) - Sprint directory initialized at `.claude/sprint/[N]/` - `specs.md` written with clear scope and testing configuration - Familiarity with the sprint phase lifecycle (see the `sprint-workflow` skill) ## Instructions 1. Structure every agent spawn using the SPAWN REQUEST format. Include the agent name, the specification file it should read, and any scope constraints: ``` SPAWN REQUEST Agent: python-dev Specs: .claude/sprint/1/backend-specs.md Contract: .claude/sprint/1/api-contract.md Scope: Authentication endpoints only ``` 2. Ensure each spawned agent receives only the files relevant to its scope. Pass the `api-contract.md` as a shared interface so backend and frontend agents stay synchronized. 3. Collect structured reports from every agent upon completion. Each report must include: work completed, files modified, tests added, and conformity status against the specification. 4. When running agents in parallel, partition work by domain boundary (e.g., backend vs. frontend vs. CI/CD). Never assign overlapping file paths to concurrent agents. 5. Feed agent repor...