What problem does it solve? Structural checks can verify that links resolve and identifiers bind, but they cannot tell whether a documentation corpus adds up to one coherent account. This Skill performs the human-model half of a coherence sweep: reading documents and reporting the contradictions, quiet supersessions, and gaps that no deterministic linter can detect. ## Core Features & Use Cases - Briefing-driven workflow: Run headwater sweep plan --under <path> to get every classified document in a slice with its identifier, kind, title, summary, and all declared graph edges. - Five finding classes: Report undeclared_conflict, quiet_supersession, undefined_concept, audience_mismatch, and unwritten_section findings with verbatim quotations the engine can verify. - Validated reporting: Submit findings via headwater sweep report, which confirms each quotation exists in the cited document, each path is a classified document, and no proposed edge duplicates the graph. - Use Case: After a major spec revision, sweep docs/spec to find older documents that still read as live, then propose conflicts_with edges so the engine owns the problem permanently. ## Quick Start Ask the assistant to run a coherence sweep over the docs/spec directory and report any contradictions or quietly superseded documents it finds.
