api-design-reviewlisted

# API Design Review Use this skill when API complexity is high enough that the normal `/research` or `/write-a-prd` flow needs a focused contract review. This is an invoked skill, not a default pipeline step. It exists to add rigor only when the cost of an API mistake is unusually high. ## Invocation Position This is an invoked helper skill. It normally runs from `/research` or `/write-a-prd` rather than as the first entry point for a feature. Use it when the unresolved question is the API contract itself: paradigm choice, consumer-facing shape, compatibility posture, or auth and webhook model. Do not use it for ordinary backend implementation work or for non-API module design questions that belong in `/design-an-interface`. ## Invoke This Skill When Invoke `/api-design-review` only if at least one of these is true: - a new external or partner-facing API is being introduced - an existing request or response contract is changing - OAuth, scopes, token model, or webhook verification is involved - there is real uncertainty about paradigm selection (REST, RPC, GraphQL, WebHooks, WebSockets) You may also invoke it for internal APIs with multiple independent consumers when a contract mistake would create broad cleanup cost. Do not invoke it for ordinary backend changes that merely happen to call an API without changing the contract shape. ## Goals Produce a lightweight design review that answers: - What developer problem is this API solving? - Who are the consumers an