What problem does it solve? Technical and scientific documentation often drifts out of sync with the code it describes, leaving readers with incorrect commands, outdated interfaces, or missing context. This Skill performs a read-only audit of documentation against actual repository evidence, producing prioritised findings without touching any files. ## Core Features & Use Cases - Evidence-backed audits: Verifies documentation claims against implementation, CLI help, tests, schemas, and release records rather than stylistic preference. - Two-pass assessment: Evaluates functional assurance (correctness, interfaces, runnable examples, units, links) and reader experience (prerequisites, sequencing, terminology, Diátaxis coherence). - Prioritised findings and needs maps: Returns findings ranked by user consequence, plus a compact needs map for repository-wide audits covering scope, audience, coverage, and validation. - Use Case: Before a release, ask for an audit of the getting-started path. The Skill checks each step against the current CLI and examples, then reports which instructions are false, unsafe, or task-blocking, without modifying the working tree. ## Quick Start Use $documentation-assessment to audit the getting-started documentation against the current codebase and report prioritised findings without changing any files.
