What problem does it solve? After backend work ships on a ticket, frontend developers need a complete, accurate map of the API surface — but they cannot read the backend repository. This Skill produces .ai/<TICKET>/fe-handoff.md, a single document containing every GraphQL query, REST endpoint, validation rule, error shape, enum, and permission the frontend needs, derived from the real code on the ticket branch rather than stale planning notes. ## Core Features & Use Cases - Code-grounded contract extraction: Reads actual GraphQL type classes, FormRequest validation rules, and permission config to document real field names, request/response shapes, and error codes — never invented examples. - User-flow ordering: Organizes operations by the user's journey through the feature instead of an alphabetical endpoint list, with each operation flagged NEW, CHANGED, or existing. - Update mode: Rescans an existing handoff against a recorded git baseline and updates only facts the code now contradicts, preserving hand-edited prose already shared with the FE team. - Use Case: After merging backend work for ticket PHG-418, ask for the FE handoff and receive a reviewed, approved document the frontend team can build from without ever opening the backend repo. ## Quick Start Ask the assistant to prepare the FE handoff for your ticket, for example by saying "write the handoff for PHG-418" after the backend implementation is complete.
