Debrief

Second brain for code changes, so the user owns a change instead of just having it merged — they can explain the problem, defend the solution, name the alternatives, and answer a skeptical senior engineer without the agent present. Two modes. Change mode: after-action review of work just done (read the real diff, explain in three layers, Mermaid diagrams, write the debrief doc, then flip roles and interview the user). Comment mode: work through PR review feedback until the claim is understood, its risk is triaged, and a decision is made together. Output always goes to the separate debrief repo, never into the project. Trigger on: /debrief, "debrief this", "after-action re…