Agent skill · affaan-m
docs-governance
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.
What it needs
About 3k tokens when loaded.
What this skill does
Documentation Governance Router Use this optional router to select the smallest existing ECC capability for a documentation-governance request. The router does not create a parallel project management system and does not make documentation authoritative over code, tests, Issues, or maintainer decisions. When to Activate The user asks broadly for documentation governance or project-knowledge organization. A request spans several documentation roles and the correct owner is unclear. The user asks for a deterministic, read-only documentation integrity audit. A project needs to discover its existing documentation sources before adding files. Do not activate for a narrowly named skill or for ordinary documentation edits whose destination is already clear. Role Contract Read the artifact-role contract before interpreting .governance/docs-map.json or default filenames. Logical roles own facts; filenames are fallbacks. Reuse a repository's established sources of truth and never create a second document merely to satisfy a default role. Intent Routing User intent Route to --- --- Adopt or maintain a constitution, map, status, and history spine living-docs-governance Record a hard-to-reverse architecture decision architecture-decision-records Preserve an executable regression for an important defect ai-regression-testing (install separately in standalone Pi core) Define a verifiable goal and feedback loop loop-design-check (install separately in standalone Pi core) Check mapped roles, local links, ADR indexes, TEST-IDs, or possible orphan docs Run the bundled read-only audit If no row fits, explain the ownership ambiguity instead of combining several workflows speculatively. Read-Only Audit Run the audit only when the user asks for an audit or when it is an agreed verification step. Resolve the selected skill directory first, then invoke: Available scopes are spine, context, adr, artifacts, modules, and full. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/docs-governance--d43ca3