PR delivery post-mortem routine

Use this routine after a long, costly, or repeatedly red PR iteration. The goal is to convert delivery-loop waste into a platform improvement, not to retell the whole PR.

Trigger

Run the routine when any of these are true:

Capture

Record the case study with these fields:

Route Learnings

Create or update backlog/docs/commons in this order:

  1. Backlog: file the smallest platform improvement with a concrete acceptance test. Link the PR and evidence ids.
  2. Docs/runbooks: update the operator or agent routine that would have changed the next agent’s first action.
  3. Commons: if the lesson changes standing agent doctrine, update the relevant founder-kernel principle, AGENTS.md rule, or skill instruction.
  4. Tests: add a contract test for the failure mode before editing the substrate.

PR #3480 Reference Pattern

PR #3480 is the post-mortem case study for BI-C22152E7. It showed that: