contract-define

Name: contract-define
Availability: InStock
Author: juan-estrada-itti

Generate API contract documents from RFC and PRD inputs.

Updated Apr 21, 2026

Search Tags:#documentation #integration #frontend-backend #flows #api-contract #data-model

Ready to run

npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill contract-define

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contract-define
Source: https://github.com/juan-estrada-itti/way-of-work-tools/tree/main/skills/contract-define
Command: npx skills add https://github.com/juan-estrada-itti/way-of-work-tools --skill contract-define

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Contract Define skill helps frontend and backend teams align on a shared API contract by generating precise, RFC/PRD-driven specifications that serve as a single source of truth.

Core Features & Use Cases

Generates api-contract.md, data-model.md, events.md, and flows.md from RFC and PRD to standardize interfaces.
Reads existing backend/frontend codebases to propose compatible endpoints and data models, reducing integration defects.
Use Case: when starting a greenfield feature or brownfield integration, create a complete contract before implementation to prevent FE/BE drift.

Quick Start

Copy this directory to your Claude skills folder and provide an approved RFC and PRD so the contract artifacts can be generated.

Frequently Asked Questions about contract-define

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an API contract from RFC and PRD documents?▼

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.

What is contract-driven development for frontend and backend integration?▼

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.

Can I use existing codebases to propose compatible API endpoints and data models?▼

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.

How do I validate API endpoints, data models, and Mermaid diagrams for my integration flows?▼

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.

Does this approach work for both greenfield and brownfield integration initiatives?▼

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.