Incident Closure

Use when the human reports breakage or says "fix it" — especially when the normal control plane (API, CLI, service) is dead and you must reach underneath it. The answer is a full understanding-first close (root cause with evidence, failing test first, green, live proof on the human's own path, commit), never a menu of options back at them. Trigger words: fix it, fix shit, full close, broken, wiped, down, it stopped working, recover, restore.

Tcuzzo Updated 2 repo stars
The Reflex Seam. On the left, a deterministic runtime owns state, files, rules and tests. On the right, a model judgment kernel owns inference, policy, reversib

File contents

Tcuzzo/backs-aios-skills commit 92b2586057

Frequently asked questions

npx get-skill add tcuzzo/incident-closure