Delivery Governance

Delivery Governance

This is a meta-skill: a rule that applies across every delivery run rather than belonging to one action. Use it whenever a run's state is read from or written to — its position, result, and blocking questions. The content below is read live from this plugin's own skills/delivery-governance/delivery-governance.md every time this skill runs, so there is no separate paraphrased copy anywhere for it to drift against.

Delivery governance contract (live)

!cat "${CLAUDE_PLUGIN_ROOT}/skills/delivery-governance/delivery-governance.md"

Instructions

1. Before doing any delivery work on a run, read its current state from .kaizen/runs/<run-id>/run.yaml exactly as the State Contract above defines the format — the six fields in the stated order, blocking_questions as a YAML list.
2. Advance state only through kaizen.py run advance (bin/kaizen_run.py), in the same change set as the evidence it describes — it writes run.yaml and appends the matching journal.md line together; a hand-edited run.yaml or a state record that outruns (or lags) its evidence is a defect.
3. At scored checkpoints, apply the evidence-verification skill per the Evidence Verification section above — do not reintroduce a blind re-scoring dispatch alongside it.
4. Resuming a run after any gap or /compact: re-read run.yaml and journal.md under that run's own .kaizen/runs/<run-id>/ before dispatching or re-dispatching anything.
5. If you are re-reading this skill after skills/delivery-governance/delivery-governance.md changed, trust what you just read above over any memory of a previous run — that live content is always the current source of truth for how delivery state is read and written in this workspace.