From wf
ALWAYS USE if you are the verifier or gardener. Use after any build cycle to audit documentation accuracy — check diagram drift, living doc freshness, ARCHITECTURE.md currency, cross-link integrity, and plan status. Gardener uses broadly across the full doc tree; verifier uses post-build to confirm the builder did its doc duty.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wf:common-doc-audit-kThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Knowledge skill** — Doc health: what to check, how to prioritize, verifier vs gardener scope.
Knowledge skill — Doc health: what to check, how to prioritize, verifier vs gardener scope.
Stale docs actively mislead. From an agent's perspective, anything not in the repo doesn't exist — and anything in the repo that's wrong is worse than nothing.
Verifier — runs post-build as part of the main loop. Checks: did the builder do its doc duty? Do living docs match what was just built? Are diagrams current? Is ARCHITECTURE.md updated?
Gardener — runs anytime, broader scope. Checks: does the entire design-docs/ tree accurately represent the system? Have things drifted since last audit? Are there orphans, broken links, stale plans?
Same checklist, different aperture.
Check │ What "wrong" looks like
─────────────────────────────┼──────────────────────────────────────
Diagram accuracy │ Class diagram missing new fields/methods
│ Data flow doesn't match actual flow
│ Component diagram has removed modules
─────────────────────────────┼──────────────────────────────────────
ARCHITECTURE.md │ Doesn't cover new components
│ Module names don't match code
│ Dependency directions wrong
─────────────────────────────┼──────────────────────────────────────
Living doc freshness │ Describes old behavior
│ References files that don't exist
│ Examples don't work
─────────────────────────────┼──────────────────────────────────────
Plan status │ Completed plans still marked active
│ Progress sections not updated
│ Missing decision logs
─────────────────────────────┼──────────────────────────────────────
Cross-links │ Plans don't link to architecture
│ Living docs not in ARCHITECTURE.md
│ Plans missing from index
─────────────────────────────┼──────────────────────────────────────
Coverage │ Components built without living docs
│ Major modules undocumented
│ New APIs without integration docs
npx claudepluginhub jsai23/claude-tooling --plugin wfAudits Archcore documentation: dashboard (counts, status, relations, orphans), deep coverage audit, or drift detection (code/cascade/temporal staleness). Use for 'show status', 'documentation gaps', or after a staleness warning.
Detects documentation drift, stale references, and cross-document inconsistencies in projects. Scans code-doc mismatches, broken links, outdated versions, and git staleness.
Validates project documentation: lints formatting and naming, checks broken/orphan links, verifies glossary terms and synonyms, detects contradictions/gaps, audits completeness via /doc:lint, /doc:links, etc.