contract-define

You can generate an API contract from RFC and PRD by providing approved documents to the skill, which then outputs api-contract.md, data-model.md, events.md, and flows.md files to serve as the single source of truth for frontend and backend alignment.

Contract-driven development is a workflow where RFCs, PRDs, and codebases are aligned to prevent frontend and backend drift. You need it when starting greenfield features or brownfield integrations to standardize interfaces and reduce integration defects before implementation begins.

Yes, you can use existing frontend and backend codebases to propose compatible API endpoints and data models. The skill reads your current codebase to generate precise specifications that reduce integration defects and align with your existing architecture.

To validate API endpoints, data models, and Mermaid diagrams, the skill generates flows.md with built-in validation during contract creation. This ensures your frontend and backend integration flows remain accurate and consistent with the approved RFC and PRD specifications.

Yes, this approach works for both greenfield and brownfield integration initiatives. The skill applies to contract-driven development workflows where RFCs, PRDs, and codebases must be aligned, creating a complete contract before implementation to prevent FE/BE drift.