What problem does it solve? Keeping an OpenAPI specification in sync with a live codebase is tedious and error-prone; specs drift out of date as endpoints, request contracts, and response models change. This Skill reads the actual source code and produces a spec that mirrors what the API really does. ## Core Features & Use Cases - Endpoint Discovery: Detects routing in frameworks like Express, Gin, Spring, and FastAPI, plus infrastructure manifests such as serverless.yml HTTP events, and enumerates every endpoint with method, path, and handler. - Contract Extraction: Reads validation layers (Zod, Pydantic, Go structs, class-validator) to extract path params, query params, body fields, constraints, and response models with correct status codes. - Version-Correct Output: Generates OpenAPI 3.1.0 by default (or 3.0.3 when tooling requires it), with DRY $ref-based schemas, realistic examples, and reconciliation that preserves manual additions when updating an existing spec. - Use Case: After refactoring a REST API, run this Skill to regenerate openapi.yaml so the documented endpoints, request bodies, and error responses match the current handlers exactly. ## Quick Start Generate an OpenAPI 3.1 specification for this repository by scanning its HTTP routes and validation schemas, and write it to .techdocs/docs/openapi.yaml.