What problem does it solve?
Recurring agent failures hide inside orchestration logs and judgment records, forcing teams to rediscover the same mistakes. This Skill reads those ledgers and turns repeated failures into structured, reviewable rule proposals without ever modifying your source-of-truth documents.
Core Features & Use Cases
- Failure Pattern Extraction: Reads the breezing orchestration ledger and Judgment Ledger to detect recurring failure signatures with occurrence counts.
- Confidence-Scored Proposals: Emits failure-rule.v1 JSON with confidence levels (low, medium at 3+ occurrences, high at 5+) and a suggested SSOT target (patterns.md or decisions.md).
- Human-Approval-Only Promotion: Promotion to SSOT files is structurally blocked; AutoPromote always errors, so a human must manually edit patterns.md or decisions.md after review.
- Use Case: After several failed companion runs, run the dry-run proposal command to get a JSON list of codified failure rules, review the evidence references, then manually record approved patterns.
Quick Start
Ask the assistant to run the failure codifier in dry-run mode to propose failure rules from the current orchestration and judgment ledgers.