What problem does it solve? Manually writing an OpenAPI specification for an existing API is slow and error-prone, especially when routes, auth schemes, and schemas must be gathered from source code or a running application. This Skill consumes the structured artifacts produced by Stage 1 reconnaissance and assembles a valid openapi.yaml without re-reading the entire codebase. ## Core Features & Use Cases - Artifact-driven spec assembly: Reads routes.json, auth-map.md, schemas.md, validators.md, and dataflows.md from /openapi-source-recon or /openapi-devtools-scan, then builds paths, tags, security schemes, and component schemas. - Merge-aware generation: If an openapi.yaml already exists, it adds new paths and updates changed ones while preserving manual edits, or overwrites entirely when requested. - Self-validation: Runs a Python structural check for YAML validity, unresolved $ref values, duplicate operationIds, and missing required fields, inserting placeholder schemas where extraction was incomplete. - Use Case: After running /openapi-source-recon on an Express.js project, invoke this Skill to produce a complete openapi.yaml plus a human-readable spec-summary.md ready for import into Postman, Swagger UI, or Burp Suite. ## Quick Start Run /openapi-spec-builder on my project directory to generate the openapi.yaml from the recon artifacts.