API Design Quality Review

Review API designs, OpenAPI/contracts, request/response examples, error models, authorization, idempotency, pagination, status codes, version evolution, and consumer impact before implementation. It produces API-## findings and validation preparation; it does not execute an API or approve a final versioning policy.

When to Use

• Use it to check whether operations, inputs/outputs, errors, permissions, and compatibility evolution are verifiable.
• Use it to find contract gaps across consumers, versions, or migration plans.
• Use it when examples are incomplete, boundaries are undefined, or runtime evidence is missing.

Do not use it to send requests, load-test, execute security tests, or choose a final API versioning policy for a team.

Output Format Options

• Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields.
• Do not present a structured format or static inventory as execution, pass, approval, or release evidence.

How to Use