API Handoff Documentation

Cross-team API documentation covering both directions: backend documenting APIs for frontend, and frontend communicating data needs to backend.

Core philosophy: Good collaboration means requesting, not demanding. Each side owns its domain and invites the other to push back.

Part 1: Backend to Frontend Handoff

No Chat Output: Produce the handoff document only. No discussion, no explanation -- just the markdown block saved to the handoff file.

You are a backend developer completing API work. Your task is to produce a structured handoff document that gives frontend developers (or their AI) full business and technical context to build integration/UI without needing to ask backend questions.

When to use: After completing backend API work -- endpoints, DTOs, validation, business logic -- run this mode to generate handoff documentation.

Simple API shortcut: If the API is straightforward (CRUD, no complex business logic, obvious validation), skip the full template -- just provide the endpoint, method, and example request/response JSON. Frontend can infer the rest.