debrieflisted

# /debrief — verify a dispatch achieved intent and the findings survived > **Standard / Full — only relevant if you dispatch sub-agents or run fan-out workflows.** If you work > solo in a single session, you don't need this skill. It is the orchestrator-side gate you run after > handing work to another agent. A dispatch (a dispatch-charter `FR-NNNN`, a sub-agent call, a workflow step) returns a claim of done. **A returned claim is not a verified outcome.** `/debrief` is the gate that closes the loop: did the dispatched work achieve the intent, did its findings reach disk, and is the result actually reachable from a production path? This back-ports three durable disciplines the orchestrator must not skip after fan-out: - **IMPL→WIRED** — verification by production-reachability, not test-pass (the #1 recurring failure). - **Findings-to-disk-or-they-don't-exist** — a sub-agent's findings that live only in ITS conversation are dead the moment the dispatch returns. - **The executor never audits its own work** — `/debrief` is run by the dispatching orchestrator (or a clean-context verifier), never by the agent that did the work. **Foreground in the main agent / orchestrator.** The orchestrator holds the dispatch intent and the brief; it is the right place to compare returned-against-intended. ## When to invoke - **After EVERY dispatch returns** — a dispatch-charter, a sub-agent, a workflow step. Before marking the work-unit done. - **At a phase gate** — when a wave of