docs: restructure docs to diataxis and finalize DOCS-RESTRUCTURE-001
This commit is contained in:
29
docs/reference-agents-overview.md
Normal file
29
docs/reference-agents-overview.md
Normal file
@@ -0,0 +1,29 @@
|
||||
# Agent Workflow Overview
|
||||
|
||||
Letzte Aktualisierung: 2026-03-06
|
||||
|
||||
This project uses a multi-role workflow for issue and feature delivery.
|
||||
|
||||
Roles:
|
||||
- Planner
|
||||
- Executor
|
||||
- Reviewer (guards and best practices)
|
||||
- Reviewer (feature acceptance)
|
||||
- Finalizer
|
||||
|
||||
Primary goals:
|
||||
- predictable handovers
|
||||
- strict quality gates
|
||||
- fast retry loop from reviewers back to executor
|
||||
- explicit guard and gate IDs (`GR-*`, `QG-*`) across all roles
|
||||
|
||||
Source of truth:
|
||||
- guardrails and planning standards in `tools/codex-skills/`
|
||||
- contracts and templates in `agent-system/`
|
||||
- guard catalog: `agent-system/checks/guard-catalog.json`
|
||||
- quality gates: `agent-system/checks/quality-gates.json`
|
||||
|
||||
Entry points:
|
||||
- roles: `docs/agents/roles.md`
|
||||
- workflow: `docs/agents/flow.md`
|
||||
- schemas and prompts: `agent-system/`
|
||||
Reference in New Issue
Block a user