detecting-doc-bloat
Installation
SKILL.md
Detecting Doc Bloat
Drift asks whether a doc is accurate; bloat asks whether it still earns its tokens. This skill is a thin router: the engine owns scope, segmentation, membership, and validation; per-need references carry the verdict rules; you supply judgment one bounded chunk at a time. Three non-negotiables:
- A verdict requires evidence. Every verdict names the quote, code line, or grep that proves the finding — never "feels redundant".
- The result is structured, not prose. Verdicts per
output-contract.md, shape-checked at every seam and audited by the engine. Approval of a record's digest is the only bridge from a finding to a file change. - Read-only — this skill never edits. A human approves digests;
fixing-docsapplies the approved subset.
Every engine command below is python3 -m doclifecycle … with the plugin's
engine/ directory on PYTHONPATH (plugins/doc-lifecycle/engine/README.md
covers both spellings).