event-contract

Author validated AsyncAPI event contracts from requirements, user stories, and domain models.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill event-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: event-contract
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/contracts/.apm/skills/event-contract
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill event-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns requirements, user stories, and domain models into complete, reviewable AsyncAPI event contracts so event producers can publish a stable interface instead of ad hoc payloads.

Core Features & Use Cases

  • Event Contract Authoring: Designs event types for services that own or produce them, including general events, data change events, and business events.
  • Standards Enforcement: Applies naming, category, schema, ordering, metadata, compatibility, and quality-gate rules while composing the CloudEvents envelope.
  • Use Case: Use this Skill when a team needs a validated AsyncAPI document for a published event stream such as order placement, resource updates, or domain milestones.

Quick Start

Ask the skill to author a validated AsyncAPI event contract from your requirements and specify the event stream you own.

Frequently Asked Questions about event-contract

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

FAQPage Schema
How do I generate an AsyncAPI event contract from domain models and user stories?

To author an AsyncAPI event contract, you provide your requirements, user stories, and domain models. The skill designs event types and outputs a complete, validated document enforcing naming, category, and payload rules.

What are CloudEvents composition rules and how are they enforced in event contracts?

CloudEvents composition rules govern metadata, ordering, and envelope structure for event streaming. The skill automatically applies these quality-gate rules while composing the validated AsyncAPI document.

When do I need a validated AsyncAPI document for event-producing services?

You need a validated AsyncAPI document when an event-producing service must publish a stable interface for data change events, business events, or general events, replacing ad hoc payloads.

How do I enforce schema validation and naming standards for event streams?

You enforce schema validation and naming standards by authoring event contracts that apply quality-gate rules. The skill validates payload structures, metadata, and compatibility in a single document.

Can I author data change events and business events with clear ownership in AsyncAPI?

Yes, you can author data change events and business events with clear ownership. The skill designs event types specifically for services that own or produce the event stream.