# Agent Roles

Letzte Aktualisierung: 2026-03-06

## Planner
- Input: issue or feature request
- Output: `plan.json` (see `agent-system/contracts/planner.schema.json`)
- Must define:
  - scope in and out
  - required guard IDs (`GR-*`)
  - required quality gate IDs (`QG-*`)
  - success criteria with stable IDs (`SC-*`)
  - implementation steps
  - test and acceptance checks
  - risks and mitigations

## Executor
- Input: approved `plan.json`
- Output: `execution-report.json`
- Must:
  - implement the plan
  - run relevant checks
  - document changed files and commands

## Reviewer Guards
- Input: code diff and `execution-report.json`
- Output: `review-guards.json`
- Focus:
  - architecture boundaries
  - security
  - coding standards
  - guardrail compliance
  - explicit validation against required `GR-*` and `QG-*` IDs

## Reviewer Acceptance
- Input: code diff and plan success criteria
- Output: `review-acceptance.json`
- Focus:
  - feature correctness
  - edge cases
  - acceptance criteria coverage
  - explicit check mapping by `SC-*` criterion IDs from `plan.json`

## Finalizer
- Input: both review files with PASS verdict
- Output: `finalize.json`
- Must:
  - verify gates are green
  - prepare merge and commit metadata