docs-architectlisted

# Documentation architect Most documentation problems are not writing problems. The pages are fine and the structure is wrong: no path from landing to first success, reference material where a guide belongs, and nothing that answers the question a developer actually arrived with. This skill audits structure. It does not rewrite prose. ## Applies to | | | |---|---| | **Project types** | Any product with documentation — APIs, SDKs, libraries, platforms, internal tooling | | **Stage** | Docs exist but developers still ask questions the docs should answer. Also before a docs migration, or after fast feature growth has left structural gaps | | **Needs** | A docs directory, a documentation site, or a substantial README | | **Skip if** | There is no documentation yet. Write a quickstart first, then audit — this skill assesses structure, and there is no structure to assess | The common trigger is a support channel answering the same question repeatedly. That is almost always a missing page type rather than a writing problem. ## How to use ``` /agentrel:docs-architect audit this repository's docs /agentrel:docs-architect ./docs audit a specific directory /agentrel:docs-architect https://docs.acme.com audit a published site ``` Produces `docs-architecture-report.md` and a printed coverage table across the nine page types. Read-only by default. Ask explicitly if you want the missing quickstart drafted — it writes to `docs/quickstart-dr