What problem does it solve? Cross-repository features spanning frontend, backend, and E2E test suites often lack a single agreed contract, causing selector mismatches, invented API fields, and brittle tests. This Skill converts a ringi's spec, test plan, and approved TDD sheet into one implementation-ready contract document that defines exactly what FE exposes, what BE provides, and what E2E consumes. ## Core Features & Use Cases - Gated contract generation: Reads the ringi's TDD Google Sheet and only proceeds when Metadata.Status is Done, then writes docs/ringi/contracts/{ringi-id}-contract.md. - Evidence-based selector contracts: Classifies every element as Existing, Proposed, PENDING, or Not applicable using read-only FE/BE/E2E repository inspection, with stable data-testid proposals for Page Object Models. - Journey and API traceability: Maps every E2E test case to journeys, pages, POM methods, and BE request/response contracts, plus owner work packets and PENDING decision tracking. - Use Case: After a ringi's test cases are approved in the TDD sheet, run this Skill to produce the contract that FE, BE, and E2E engineers implement against without inventing selectors or endpoints. ## Quick Start Use the fe-be-e2e-contract-agent skill to create the FE/BE/E2E contract for ringi R-1234 from its spec, test plan, and approved TDD sheet.
