Loading...
Loading...
Found 2 Skills
Systematic documentation audit and maintenance. This skill should be used when documentation may be stale, missing, or misorganized — after feature work, refactors, dependency upgrades, or as a periodic health check. It prescribes folder structure for docs/ and manual/, dispatches haiku subagents for codebase/doc scanning, and routes doc creation to specialized agents (reference-builder, technical-writer, learning-guide) with docs-architect as quality gate.
Use when writing, moving, reviewing, or auditing documentation in a repository — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a documentation-budget gate failure, or requests like "improve the docs", "audit the docs", "govern the docs", "standardize the documentation of a repository", "where should this be documented", or "this doc is too long".