aoa-contract-test

What problem does it solve?

When components interact across a meaningful boundary, the expected inputs, outputs, and verification obligations are often implicit and fragile; this skill makes those interface contracts explicit and reviewable so downstream assumptions are clear and testable.

Core Features & Use Cases

• Boundary Identification: Guide agents or humans to locate the boundary and its consumers within a codebase or service mesh.
• Contract Expression: Translate expected inputs and outputs into concrete tests, smoke summaries, or structured checks tied to the interface rather than internals.
• Verification & Reporting: Produce verification steps and downstream impact notes so reviewers can confirm what the validation actually proves.
• Use Case: Strengthen a microservice interface by adding smoke tests that assert request/response shapes and document downstream assumptions for reviewers.

Quick Start

Inspect the boundary between the service and its consumer, state the expected inputs and outputs, and propose tests or smoke checks that make the contract explicit and verifiable.