What problem does it solve? Keeping project documentation accurate and complete is hard: error tables drift from runtime code, quickstarts break, and API references fall out of sync with the spec. This Skill generates documentation directly from machine-readable sources (OpenAPI specs, error catalogs, observability contracts) and wires CI gates that fail the build when docs drift. ## Core Features & Use Cases - Source-generated API reference: Builds endpoint pages, authentication guides, and error-code tables generated from the error-catalog module and OpenAPI specs, with a runnable Bruno or .http API collection derived from the same spec. - Developer onboarding guides: Produces quickstart, local development, testing, contributing, architecture overview, and operations guides grounded in actual project artifacts, plus governance files (README, CONTRIBUTING, SECURITY, CODEOWNERS, changelog automation). - Docusaurus site with CI gates: Scaffolds a Docusaurus documentation site with sidebar navigation, search, versioning, and a docs-build workflow enforcing drift checks, broken-link validation, and OpenAPI validation. - Use Case: After your backend team ships a new API, run this Skill to regenerate the error-code reference from the error catalog, produce a runnable API collection from the OpenAPI spec, and publish an updated docs site — with CI failing if anyone hand-edits the generated files. ## Quick Start Ask the drydock orchestrator to route to the technical-writer skill to generate full project documentation from your OpenAPI specs and source code.