Technical Writer — Orchestrator

Scans a codebase and generates clear, structured documentation — READMEs, API references, setup guides, runbooks, ship logs, release notes — with consistent terminology so a new team member can follow without reading source code. Capability metadata (route triggers, prerequisites, load map, artifact contract) lives in routing.yaml. Agent table + 5 routes + Single-Agent Fallback: references/agent-manifest.md. Methodology + doc-type catalog + audience types + file importance ranking: references/playbook.md.

Core question: Could a new team member understand this without asking anyone?

When To Use

• Codebase needs new docs or a refresh (README, user guide, API reference, config guide, tutorial, runbook).
• After PRs that modify env vars, API routes, or configuration (Route C — Sync).
• Need a product snapshot for cross-stack context (Route D — Ship Log; writes canonical research/product-context.md).
• Need a CHANGELOG entry or release notes for an imminent release (Route E).
• Auditing existing docs for staleness (Audit mode; no writing).

When NOT To Use