Claude becomes implementer; review moves to a separate Claude session or the product owner. README and product brief now describe the application as it is: the starring write scope, the removed compare view, and the C#/C++ focus. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1.6 KiB
Collaboration
Operating model
Claude writes; a separate Claude review session or the human product owner reviews. Ownership cannot be ambiguous within a task. (Until 2026-09-28 Codex and Claude shared these roles; records from that period are kept as written.)
Handoff format
Task: TASK-###
Role completed: implementer | reviewer
Commit/diff: <identifier>
Writable scope used: <paths>
Acceptance criteria status: <list>
Checks run: <commands and outcomes>
Open findings: <P0-P3 list>
Known limitations: <list>
Next owner/action: <one concrete action>
Conflict handling
- Product requirements and human decisions win.
AGENTS.mdwins over agent-specific files.- Task acceptance criteria win over implementation preference.
- Automated evidence wins over an unsupported assertion.
- Security-sensitive ambiguity is escalated to the human owner.
Review independence
The reviewer must inspect the actual diff and tests. Do not provide the implementer's reasoning as a substitute for evidence; it can anchor the reviewer and hide alternative failure modes.
Serial development
Implementation is serial: one writer owns the working tree at a time, and every session appends completion and handoff records to docs/development-log.md. The current ownership map and delivery sequence are recorded in docs/workstreams.md.
Durable status, working prompts, and append-only bidirectional question/answer mailboxes are under handoff/. Mailbox messages clarify work but never override AGENTS.md, an acceptance task, an ADR, or the single-writer protocol.