What problem does it solve?
Engineering decisions are often made and then forgotten, leaving teams unsure whether a past choice still holds after code changes, time passes, or evidence expires. This Skill closes the loop by re-checking recorded DecisionRecords against real measurements so stale or invalidated decisions are surfaced before further work relies on them.
Core Features & Use Cases
- Baseline-vs-measure verification: Runs each decision's declared predictions (observable, threshold, verify_after) against actual test results, metrics, or code checks, then records an accepted, partial, or failed verdict.
- Drift and decay detection: Baselines affected_files content hashes to detect drift, and surfaces decisions whose evidence has passed its valid_until date per FPF Evidence Decay.
- Maintenance backlog drain: Previews and applies kernel-classified machine-safe closures for stale decisions while keeping material or security-sensitive cases operator-facing.
- Use Case: After shipping a caching change recorded as dec-20260525-abc, ask whether the decision still holds; the Skill runs the latency benchmark, attaches the measurement as evidence with a congruence level, and records the verdict.
Quick Start
Ask the agent to verify whether decision dec-20260525-abc still holds, or run it with no argument to check what is stale across the project.