What problem does it solve? Engineering teams often ship features without accurate, usable documentation, leading to support tickets and slow onboarding. This Skill turns source code, specs, and tests into PR-ready docs with verifiable evidence links, so every claim in the documentation is traceable to code. ## Core Features & Use Cases - Docs Generation from Code: Produces quickstarts, how-to guides, concept docs, and troubleshooting pages grounded in source code, specs, and tests, with explicit "Unverified" flags for anything that cannot be confirmed. - API Reference from Specs: Parses OpenAPI, GraphQL, or protobuf definitions into reference docs with request/response examples and error tables. - Release Notes & Docs Audits: Writes user-impact-framed release notes and migration guides, and audits existing docs for broken links, stale instructions, and missing prerequisites. - Use Case: After merging a new API feature, ask the Skill to generate a quickstart, an API reference from the OpenAPI spec, and a release notes entry, all delivered as a PR-ready change set with file-and-line evidence pointers. ## Quick Start Ask the assistant to generate a quickstart and how-to guide for a specific feature by pointing it at the relevant source files, tests, and spec in your repository.