I use a mixed approach for OpenAPI, but not bidirectional. I have OpenAPI pieces generated from my Go source code (comment, types, function signatures) as JSON

I use a mixed approach for OpenAPI, but not bidirectional. I have OpenAPI pieces generated from my Go source code (comment, types, function signatures) as JSON. I also have a manually-edited master YAML document that refers to generated bits via $ref links. I then use openapi-preprocessor [1] (disclaimer: I wrote it) to produce a final openapi.json file which is committed in the repo. When I want to extend the API in a spec-first process, I can add the new routes manually in the YAML file. When I do the implementation I replace the manual bits by the generated one when they are ready. When committing I can check the diff of openapi.json to verify I'm not losing in the process. [1] https://github.com/dolmen-go/openapi-preprocessor https://github.com/dolmen-go/openapi-preprocessor