Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review this proposed contract change: [change]. The clients are [web, mobile, or other consumers], and the current server behavior is [behavior].
Trace each changed field through input, validation, domain rules, storage, response, and interface rendering. Check null handling, units, dates, identifiers, and error shapes. Consider clients that may continue using the old contract after deployment.
Recommend a compatible sequence for applying the change and identify any data migration. Implement the agreed scope and verify representative old and new requests. Report concrete incompatibilities, checks, and deployment ordering rather than relying only on matching type definitions.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted compatibility review. Schema changes and old-client behavior are grounded in OpenAPI and Google's compatibility guidance.