Skip to main content
Define what your customers need to prepare. Preview rollouts before they start. Publish to the registry so enterprises are ready on day one.

​
Install

npx skills add interf-labs/enterprise-readiness-protocol
Then tell your coding agent: 
draft a readiness contract for this project and preview rollout for BlackRock
Works with Claude Code, Codex, Cursor, and Goose. No API keys. No network calls. No code execution.

​
Skills

SkillWhat it does
interf-draftDraft a readiness contract (`interf.yaml`)
interf-previewPreview enterprise rollout — timelines, stakeholders, risks, critical path
enterprise-readiness-protocolThe protocol specification and canonical dependency types
Install individually: 
npx skills add interf-labs/enterprise-readiness-protocol --skill interf-draft

​
The Readiness Contract

An `interf.yaml` file that defines what must be true before enterprise rollout. Each requirement is a `what` + `ready` pair — what you need, and how enterprise verifies it’s done:
interf.yaml
name: crm-automation-agent
version: 0.2.0
description: Automates CRM data entry and follow-up scheduling

requirements:
  - what: Read/write access to your CRM (contacts and opportunities)
    ready: We can create a contact and read an opportunity via API from our staging environment

  - what: SSO endpoint for our service to authenticate your users
    ready: A test user can log into our app via your SSO and see their CRM data

  - what: Someone from your data team to map your custom fields to our schema (~4 hours)
    ready: Field mapping document completed and signed off by both sides

  - what: Test environment with sample CRM data for validation
    ready: We can run our full test suite against the environment without errors

optional:
  - what: Webhook endpoint for real-time update notifications
    ready: We receive a test webhook payload within 5 seconds of a CRM update
Plain English. Any stakeholder can read it. Version it like a package. The `ready` field defines what must be true — verifiable acceptance criteria for each dependency.

​
Dependency Types

Each requirement can map to a known dependency type from the catalog. This enables deterministic matching — if a dependency like `auth.sso.saml` has already been resolved for one vendor, it auto-resolves for every other vendor that needs it.
CategoryCovers
`integration.*`CRM, ERP, HRIS, email, webhooks, ticketing, analytics
`auth.*`SSO (SAML/OIDC), API credentials, service accounts
`data.*`Historical exports, field mapping, sample data
`infra.*`Test environments, network/firewall, compute
`stakeholder.*`Data team, security, IT admin, executive sponsor
`process.*`Security review, legal/DPA, procurement, training

​
The Protocol

Enterprise rollouts stall because readiness gaps — missing data access, authentication, stakeholder coordination — are discovered mid-flight. Forward-deployed engineers spend months on dependency resolution that should have happened before rollout began. The Enterprise Readiness Protocol defines how vendors declare readiness requirements and how enterprises verify them. The contract connects both sides.

​
How It Works

  1. Draft — Vendor drafts `interf.yaml` — the readiness contract defining every requirement.
  2. Deliver — Contract is published to the Interf registry or sent directly to enterprise.
  3. Resolve — Enterprise works through each requirement, audited against the `ready` criteria.
  4. Verify — All requirements resolved. Full audit trail. Rollout can proceed.

For Vendors

Define readiness requirements in `interf.yaml`. Preview rollouts against enterprise profiles. Publish to the registry so enterprises self-prepare.

For Enterprises

Pull readiness contracts from the registry. Run readiness checks. Resolve requirements before rollout begins — not after.

​
In Production

  1. Enterprise loads the vendor contract into the Interf Gateway, creating a readiness workspace.
  2. Gateway exposes readiness state as an API — each requirement tracked from unresolved to verified.
  3. Enterprise IT resolves requirements — provisions access, configures auth, completes reviews.
  4. Vendor connects to the gateway, queries readiness state, and verifies against the contract.

​
CLI

The Interf CLI validates readiness contracts and publishes them to the registry. 
npm install -g interf
CommandPurpose
`interf`Install protocol skills to your coding agents
`interf validate`Validate `interf.yaml` — schema, canonical types, suggestions for shorthand
`interf publish`Publish contract to the Interf registry (coming soon)
`interf preview`Preview rollout powered by registry data (coming soon)
The skills teach your coding agent the protocol. The CLI is for validation and publishing.

Get Started

Install the skills and draft your first readiness contract.