aibdd-form-api-spec

You can generate OpenAPI specs from feature files automatically by running a reconciler workflow that reads your current api.yml, derives the desired state from .feature specs, computes diffs, and applies incremental changes to keep API contracts in sync.

The derive-read-diff-apply workflow is a reconciliation process that reads your existing API spec, derives a desired state from feature files, computes structural diffs, and applies only the necessary changes to maintain validator-friendly OpenAPI outputs.

Yes, you can update an existing OpenAPI spec without a full rewrite because the reconciler supports incremental updates, applying computed diffs to your current api.yml so existing APIs remain intact while new changes are integrated.

Yes, this tool works with existing api.yml files by reading the current API spec as a baseline, deriving the desired state from .feature files, and applying incremental diffs to ensure your OpenAPI specifications stay synchronized.

The best way to keep API contracts in sync is to automatically derive OpenAPI specifications from feature files using a reconciler workflow, which computes and applies incremental diffs to reduce manual drafting errors and maintain consistent outputs.

You should avoid automated OpenAPI spec derivation if your project lacks .feature spec files or an existing/future api.yml, as the reconciler workflow depends on reading and diffing these specific formats to apply incremental contract changes.