What problem does it solve? Feature work generates friction findings logged in META.md files, but turning those observations into actual improvements to agent skills, templates, and scripts requires a careful, human-gated process that avoids weakening safety gates or thrashing prior decisions. ## Core Features & Use Cases - Finding triage: Reads open findings from spec/{slug}/META.md via meta_status.py, filtered by id, severity, or across all features with --all. - Human-gated application: Previews a concrete diff per finding, confirms with the human, then applies each fix as its own atomic [harness] commit on main (or a harness/{slug} branch with PR mode). - Anti-thrash ledger: Records every applied, rejected, and deferred decision in harness-log.md so future runs detect reverts of recent changes or repeats of rejected fixes. - Use Case: After a feature merges, run /cm-harness my-feature --dry-run to preview fixes for its open findings, then apply the approved ones as individual commits with status flips and ledger entries. ## Quick Start Ask the agent to run /cm-harness with a feature slug to review and apply that feature's open harness findings as atomic commits on main.
