What problem does it solve? Teams often let coding agents implement public APIs, schemas, or module boundaries before anyone has agreed on the shape, which locks in costly-to-reverse contracts and causes breakage for downstream callers. This Skill inserts an approval gate so durable interfaces are reviewed and approved before any implementation lands. ## Core Features & Use Cases - Contract Detection: Identifies when a task defines or changes a caller-facing surface such as exported functions, public types, HTTP endpoints, CLI flags, event payloads, database schemas, migrations, or package boundaries. - Scaled Approval Gates: Scales the gate with reversal cost, so additive and easily reversed changes proceed while breaking or durable shapes require an explicit approve, revise, or reject decision. - Compatibility Decisions: Forces an explicit choice on renames and removals, covering breaking changes, aliases, shims, deprecation paths, or retained old surfaces. - Use Case: Before adding a new REST endpoint and its request/response schema, the agent stops, lists each proposed surface with file and line evidence, waits for your approval, and only then implements the agreed shape. ## Quick Start Use the contract-first skill to propose and get approval for the new API endpoint shape before writing any implementation code.