| name | debrief-protocol |
| description | Use for any agent that writes code and must produce a work audit before building. Defines the debrief file format, naming convention, timing, and required sections. |
Debrief Protocol
You MUST write a debrief/work audit as part of your build-verify cycle -- before requesting a build, not after. The debrief is committed alongside your code changes so the build verifies the complete commit.
File Location and Naming
Write debriefs to Notes/docker-claude/debriefs/ in the workspace (create the directory if needed). Use the filename format:
debrief-NNNN-keyword-keyword-keyword.md
where NNNN is a zero-padded 4-digit counter (check existing files to determine the next number) and the three keywords summarise the work area (e.g. debrief-0001-crowdfield-teardown-fix.md).
Timing
- Write your debrief, commit it with your code, then request the build.
- If the build fails, fix the issues, update or write a new debrief describing what you had to fix, commit, and rebuild.
- Each build/validate/revise iteration should have a corresponding debrief entry.
Required Sections
- Task Summary — What was asked and what you understood the goal to be.
- Changes Made — List every file you created or modified, with a one-line description of each change.
- Design Decisions — Any non-obvious choices you made and why.
- Build & Test Results — Whether the project built and tests passed, including any failures and how you resolved them. (On the first debrief before any build, state "pending initial build".)
- Open Questions / Risks — Anything you were uncertain about, couldn't verify, or that warrants human review.
- Suggested Follow-ups — Work that naturally follows from what you did but was out of scope.
Keep it factual and concise. This document is for the human operator to audit your work without needing to read every diff.
