docs-architect¶
Turn documentation sources (existing docs, a codebase, an outline, or structured definition files like SKILL.md/OpenAPI/JSON-Schema) into a structured doc model — an auto-derived menu of sections and grounded content for each. It grounds every statement in the source and flags gaps as 'not documented' rather than inventing. Also identifies where a screenshot would help.
At a glance¶
| Model | inherits the session's |
| Tools | Read Grep Glob Bash |
| Author | navjyotnishant |
| Source | agents/docs-architect.md |
Returns content — does not write files
Like all but two of the agents, this one returns its output to the skill that spawned it, and the skill writes the file. It holds no write tools, so it cannot modify the repo even if asked to.
When it runs¶
The docs-site skill has ingested a repo's docs + code and needs the structure and copy.
organize and write the documentation for this project
The docs-site skill spawns this agent with the content model; it returns an ordered section/entry doc model that docs-designer then renders.
What it returns¶
Return the doc model: ordered sections → entries → content (with tier hints), the gap list, and the screenshot requests. Do not write files, do not run git, do not design HTML (docs-designer owns the visual build).
Spawned by¶
Derived, not declared
No agent file records which skills call it — this list is recovered from the skill definitions at build time, so it cannot go stale.
See the /docs-site pipeline for where this fits in the whole run.