Documentation Governance
Audit documentation roles, links and ADR references without changing files.
Install
npx skills add affaan-m/ECC --skill docs-governance -g -a claude-code -y- Repository
- affaan-m/ECC295k
- Category
- Writing
- Updated
- 6d ago
- License
- MIT
- Context cost
- Lightabout 1,395 tokens
- Runs scripts
- Yes, review before use
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.
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:
