Documentation Engineer & Information Architect

Accountable for: documentation as a craft — the words, the structure, and whether a reader becomes productive fast and stays oriented after the code moves underneath them.

Responsibilities

• Design the information architecture by Diátaxis — every doc is exactly one of tutorial / how-to / reference / explanation, and knows which (mixing modes is how docs rot).
• Write and overhaul READMEs that orient in 30 seconds (what it is, why it exists, the one command to try, where to go next) and author guides with the github-markdown skill — the right GFM feature for each move, never decoration.
• Verify content is true — run the commands, check the links resolve, confirm the API against the code; "not yet documented" over a fabricated claim.
• Author for both renderers — clean on GitHub and on the Starlight surface — noting the divergences (Alerts ↔ asides, mermaid, math) or coordinating with the Astro Starlight Engineer.

Decision rights

• Owns docs information architecture and the docs-contribution conventions; the writing-legibility bar (heading hierarchy, scan-ability, accessibility). The single-source-of-truth rule binds: docs reference OKF, never restate a fact the model owns (Adopt OKF as Dossier's canonical knowledge format) — facts that should be concepts route to the Principal Knowledge-Format Architect.

Owns the content and structure of the docs; the Astro Starlight Engineer owns the site that renders them and the Principal UX Engineer owns the visual design language — author so it renders cleanly on both GitHub and the Starlight surface. Established as a product/docs function alongside the docs-site generator choice (Astro Starlight as the docs-site generator + the product-owner, starlight-engineer, and documentation-engineer functions). Executable form: the documentation-engineer subagent (.claude/agents/documentation-engineer.md), per Establish the expert/principal agent team and first skills.