api-contract — cross-repo contract generation

The per-stack LLDs each describe one side of the boundary: the backend LLD says what it will expose; the frontend LLD says what it needs to consume. This skill reconciles them into ONE authoritative contract (OpenAPI) that the backend implements and the frontend consumes — the boundary that lets each side build and verify alone. Writes the contract + acceptance criteria only; no app code.

When to use / not use

• Use once both per-stack LLDs exist (.maestro/<slug>/lld/backend.md and .../frontend.md). Runs after the design phase, before implementation.
• Don't design internals (that's the LLDs) or implement. Don't invent operations neither LLD calls for.