What problem does it solve? Frontend and backend teams often drift apart because they build against assumptions instead of a shared specification, causing integration failures discovered late in development. This Skill produces a single authoritative API contract that both sides implement against with zero tolerance for deviation. ## Core Features & Use Cases - Structured Contract Authoring: Defines each endpoint with path, HTTP method, request parameters, typed fields, and success/error response examples in a consistent Markdown format. - Configurable Contract Location: Reads api_contract_path from .archflow/project-settings.yaml so the contract lands where the project expects it, defaulting to docs/api-contract.md. - Scoped, Append-Only Updates: Limits contract work to the active release and appends per-story sections without rewriting or dropping existing endpoints. - Use Case: During Archflow Phase 2.5, after wireframes are approved, generate the full API contract for the current release so api-engineer and ui-engineer can build in parallel without integration mismatches. ## Quick Start Ask the agent to create the API contract for the current release's stories and write it to the configured api_contract_path.