docs-governance
Routes broad documentation-governance requests to the right specialized skill and runs a read-only audit of documentation roles, links, ADR indexes, and evidence references.
What it does
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit without naming a narrower skill.
Quality judgment
A well-scoped router with clear activation/deactivation criteria, a concrete routing table, exit-code semantics, and good examples including a negative case. It loses points for an unresolved placeholder path (<docs-governance-skill>), reliance on an unverifiable external reference file, and no guidance on audit output format or how to present results to the user.