dead-letter
📮 dead-letter — Failed Task Triage & Capture
Capture a failed or blocked task before context clears. Categorizes failure modes into a 9-part taxonomy, distinguishes transient from permanent failures, verifies actual state before any retry, preserves partial work and orphaned resources, and generates either a bounded autonomous retry prompt or an escalation decision point. Recovery follows a strict ordered sequence — classify → decide → precondition → fix → verify-against-baseline → close — tracked step-by-step in the record so a retry resumes exactly where recovery stopped. At close-out, deterministic failures can be converted into a repro test pack: the capture that documents a failure becomes the regression test that prevents its recurrence. The status sweep clusters open records by root cause — repeated failures across different tasks surface as one systemic finding with one fix, not a storm of individual retries.
Modes
Every invocation resolves to exactly one mode. Load only the matched reference:
| Mode | Trigger phrases | Behavior | Reference |
|---|---|---|---|
circuit-breaker |
"dead-letter circuit-breaker", "circuit-breaker" | Toxic Task Circuit Breaker & Concurrency Safety | references/circuit-breaker.md |
record-schema |
"dead-letter record-schema", "record-schema" | Dead-Letter Record Schema | references/record-schema.md |
sweep-protocol |
"dead-letter sweep-protocol", "sweep-protocol" | Status Sweep & Cluster Triage Protocol | references/sweep-protocol.md |