Truncated OpenAPI Schema Recovery Prompt Template

The partial OpenAPI specification text that was cut off during generation. This is the primary input to repair.

{"openapi": "3.0.3", "info": {...}, "paths": {"/users": {"get": {"summary": "List users", "responses": {"200": {"description": "A list of users", "content": {"application/json": {"schema": {"type": "array", "items": {"$ref": "#/components/schemas/

Parse check: input must be a non-empty string. Content check: input should contain recognizable OpenAPI keywords (openapi, paths, components, info). Truncation check: input should end mid-token, mid-string, or with unclosed braces/brackets.

The target OpenAPI specification version for the repaired document. Ensures the recovery prompt uses version-appropriate syntax and rules.

3.0.3

Enum check: value must be a valid OpenAPI version string (3.0.x, 3.1.x). Schema check: version must match the version declared in the truncated document if present.

A list of endpoint paths and HTTP methods that must be present and complete in the repaired specification. Prevents the model from omitting critical API surfaces.

["/users:get", "/users:post", "/users/{id}:get", "/users/{id}:patch"]

Schema check: must be a JSON array of strings. Format check: each string must follow the pattern '/path:method'. Completeness check: list should cover all endpoints expected in the final spec.

The expected set of component schema names that should be defined under #/components/schemas/. Guides the model to recover schemas that were partially defined or referenced but not completed.

["User", "UserCreateRequest", "UserUpdateRequest", "ErrorResponse", "PaginationMeta"]

Schema check: must be a JSON array of non-empty strings. Reference check: names should match $ref values found in the truncated document. Null allowed: true if no schemas are expected.

The authentication method used by the API. Informs how the model repairs securityDefinitions or securitySchemes blocks if they were truncated.

bearerAuth

Enum check: value should be a known security scheme type (bearerAuth, apiKey, oauth2, openIdConnect, basicAuth). Null allowed: true if the API has no security requirements.

Optional natural language description of the API's purpose, domain, or business logic. Helps the model infer correct field names, data types, and endpoint behavior when the truncated text is ambiguous.

A REST API for a SaaS user management system. Users have profiles, roles, and team memberships. Endpoints support CRUD operations, pagination, and filtering by status.

Type check: must be a string or null. Length check: if provided, should be under 500 tokens to avoid diluting the primary repair task. Null allowed: true.

The expected structure of the model's response. Instructs the model to return the repaired OpenAPI document and a repair summary in a structured format for downstream parsing.

{"repaired_spec": "string", "repair_summary": {"endpoints_recovered": ["string"], "schemas_recovered": ["string"], "unrecoverable_sections": ["string"], "repair_notes": "string"}}

Schema check: must be a valid JSON Schema or TypeScript interface definition. Field check: must include a field for the repaired spec string and a structured repair summary. Parse check: output schema must be parseable by the application harness.

string (semver)

Must equal '3.0.3' or '3.1.0'. Parse as semver and reject if missing or invalid.

string

Non-empty string. Must match [ORIGINAL_TITLE] if provided in context. Reject if null or whitespace-only.

string

Non-empty string. Preserve [ORIGINAL_VERSION] if present in partial input. Reject if missing.

object

Must be a valid JSON object with at least one path key. Each path item must contain at least one HTTP method operation. Validate with OpenAPI schema.

object

Every operation must have a responses object with at least one HTTP status code key. Reject operations with empty responses.

object

If present, each schema must have a 'type' property or '$ref'. Validate schema references resolve within the document. Null allowed if no schemas.

per schema

Any field present in [PARTIAL_SPEC] must appear in output with preserved values. No hallucinated fields beyond repair scope. Diff against partial input.

object

Must include 'repaired_sections' (array of strings), 'unrecoverable_sections' (array of strings), and 'confidence' (string enum: 'high'|'medium'|'low'). Required for audit trail.

Output passes a standard OpenAPI 3.x parser without errors

Parser throws syntax errors, missing required fields, or invalid references

Run output through an OpenAPI validator library (e.g., swagger-parser, openapi-core) and assert zero errors

All paths and HTTP methods present in [PARTIAL_SCHEMA] appear in the repaired output

Paths or methods from the partial input are missing or altered in the final output

Extract path+method tuples from [PARTIAL_SCHEMA] and diff against repaired output; assert 100% match

All $ref pointers resolve to components defined within the output or are preserved as-is from the partial input

Dangling $ref values that point to nonexistent component keys

Resolve all $ref pointers programmatically; assert no unresolved references in the final output

Output contains zero paths, methods, or operations not present in [PARTIAL_SCHEMA] or clearly implied by its structure

New endpoints, parameters, or response codes appear that were not in the partial input

Diff path+method+operationId sets between [PARTIAL_SCHEMA] and output; flag any additions for human review

All schema objects in #/components/schemas from [PARTIAL_SCHEMA] are preserved with their original property names and types

Properties renamed, types changed, or required fields dropped from existing component schemas

Deep-compare each schema object from [PARTIAL_SCHEMA] against the repaired output; assert structural equality for all pre-existing keys

The specific object, array, or string that was cut off at the truncation point is syntactically closed and semantically coherent

The repaired boundary introduces contradictory types, impossible values, or broken nesting

Identify the truncation point from [PARTIAL_SCHEMA]; manually inspect the repaired boundary for syntactic closure and semantic plausibility

All response schemas referenced by operations include at minimum a description and a content/mediaType entry if implied by context

Response objects are empty, missing required fields, or contain placeholder-only content

Traverse all operation responses in output; assert each has a non-empty description or content block unless explicitly optional in the spec

The info.title, info.version, and servers array from [PARTIAL_SCHEMA] are preserved exactly or completed with minimal, plausible defaults

Title or version fields are replaced with generic placeholders like 'API' or '1.0.0' without evidence from the partial input

Compare info and servers blocks from [PARTIAL_SCHEMA] against output; flag any value changes for human approval