What problem does it solve? Platform teams often expose golden paths as templates developers copy, which fragments governance and leaves agent callers without a consistent, governed API surface. This Skill designs the replacement: one contract-first platform API behind Azure API Management, plus a thin platform MCP server so every agent runtime (Claude, Copilot, Codex) inherits identical guardrails. ## Core Features & Use Cases - Contract-first API design: Produces an OpenAPI spec where each golden-path operation (create service, provision datastore, promote environment, approve change) becomes a governed endpoint. - APIM and Front Door architecture: Defines APIM products, subscription models, policy fragments (rate limits per agent principal, JWT validation, audit logging to Log Analytics), and guidance on when to add Azure Front Door. - MCP server and approval workflows: Plans the thin platform MCP server mirroring OpenAPI operations one-to-one, and approval endpoints that close the loop with Dapr durable workflows. - Use Case: A platform engineering team replacing repo-stamping templates with a governed API uses this Skill to emit the OpenAPI spec, APIM policy set, MCP tool schema list, orchestrator backend spec, and a rollout ADR for migrating from template paths to API paths. ## Quick Start Ask the agent to design the golden-path platform API on Azure APIM, including the OpenAPI contract, APIM policies, and the MCP tool surface for agent callers.
