contract-handshake-and-freeze

Define, track, and freeze cross-layer frontend and backend contracts.

Updated Feb 5, 2026

Search Tags:#API #integration #governance #handoff #contract #cross-layer

Ready to run

npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill contract-handshake-and-freeze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: contract-handshake-and-freeze
Source: https://github.com/Luis-ERP/dev-agent-crew/tree/main/skills/contract-handshake-and-freeze
Command: npx skills add https://github.com/Luis-ERP/dev-agent-crew --skill contract-handshake-and-freeze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces explicit, shared contracts between frontend and backend to prevent drift, late changes, and misinterpretations during feature integration.

Core Features & Use Cases

Explicit contract artifacts: capture endpoints, request/response shapes, auth requirements, and invariants in a shared artifact.
Lifecycle governance: update contract state in HANDOFF.md (draft, changing, frozen) and reference authoritative docs.
Freeze signaling: emit a clear contract freeze signal to lock in expectations and enable parallel FE/BE work.

Quick Start

Define a new contract during feature planning by updating the feature design artifact, record the contract state in docs/team/HANDOFF.md, and move to frozen when all parties agree.

Frequently Asked Questions about contract-handshake-and-freeze

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

FAQPage Schema

How do I freeze API contracts between frontend and backend teams?▼

To freeze API contracts, you define endpoints, schemas, and auth requirements in a shared artifact, track the state in HANDOFF.md, and emit a freeze signal to lock expectations for parallel frontend and backend work.

What is cross-layer contract governance for feature integration?▼

Cross-layer contract governance explicitly defines and tracks API endpoints, request/response shapes, and invariants between frontend and backend teams to prevent drift, late changes, and misinterpretations during feature integration.

How do I track API contract lifecycle states from draft to frozen?▼

You track API contract lifecycle states by recording the current status—draft, changing, or frozen—in docs/team/HANDOFF.md and referencing authoritative docs to maintain shared expectations across teams.

When do I need to define explicit contracts for data shape evolution?▼

You need to define explicit contracts for data shape evolution when multiple teams integrate features, ensuring documented request/response schemas, auth behaviors, and error invariants are established before implementation begins.

Does cross-layer contract governance work for multi-team API changes?▼

Yes, cross-layer contract governance is designed for multi-team projects, applying to API changes, data shape evolution, and authentication behavior to ensure documented endpoints and stable invariants across teams.

Why does frontend and backend integration suffer from contract drift?▼

Frontend and backend integration suffers from contract drift when shared expectations are implicit, which this Skill prevents by capturing endpoints, schemas, and auth requirements in an explicit artifact before implementation.