skills.rest
slusset
slussetCOMMUNITY
Explore all skills by this author →
GitHub

behavior-contract

Transform solution narratives into Gherkin feature files and protocol contracts.

1|Updated Feb 8, 2026
Search Tags:#openapi#asyncapi#traceability#bdd#gherkin#behavior-contract
One-click install
npx skills add https://github.com/slusset/intention-driven-design --skill behavior-contract
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: behavior-contract
Source: https://github.com/slusset/intention-driven-design/tree/main/skills/behavior-contract
Command: npx skills add https://github.com/slusset/intention-driven-design --skill behavior-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts solution narratives into executable specifications and protocol contracts, reducing drift between intent and implementation.

Core Features & Use Cases

  • Generate Gherkin feature files from journeys and stories.
  • Produce OpenAPI/AsyncAPI/JSON-RPC contracts and fixtures for testing.
  • Maintain end-to-end traceability from story to contract to implementation.

Quick Start

Create a narrative, then request a full feature, contract, and fixture set.

Frequently Asked Questions about behavior-contract

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

FAQPage Schema
How do I generate Gherkin feature files from user stories?▼

To generate Gherkin feature files from user stories, provide a solution narrative to transform it into executable specifications with consistent structure and end-to-end traceability metadata linking stories to features.

How do I create OpenAPI and AsyncAPI contracts from a narrative?▼

You create OpenAPI and AsyncAPI contracts from a narrative by submitting the solution story to generate protocol contracts alongside test fixtures and traceability metadata, reducing drift between intent and implementation.

What is the best way to maintain traceability between user stories and API contracts?▼

Maintaining traceability between user stories and API contracts requires mapping solution narratives directly to executable specifications and protocol contracts, enforcing end-to-end artifact consistency across stories, features, contracts, and fixtures.

Can I generate JSON-RPC contracts and test fixtures from user journeys?▼

Yes, you can generate JSON-RPC contracts and test fixtures from user journeys by processing the narrative to produce executable specifications, applying consistent artifact structure across the generated contracts and fixtures.

Does converting user stories into executable specifications require existing API definitions?▼

Converting user stories into executable specifications does not require existing API definitions; the transformation generates OpenAPI, AsyncAPI, or JSON-RPC contracts and fixtures directly from the solution narrative you provide.

Related Skills

Explore More Software Engineering Skills→
jsaliojsalio

sdd

Create SDD contracts with data models, API contracts, and documentation from feature ideas.

Community
Advanced
exerias21exerias21

eval-harness

Run pytest tests and pipeline simulations to verify feature behavior.

Community
Intermediate
GoldziherGoldziher
115

Code Generator Design - Spec-to-Handler Codegen

Generate type-safe API handler stubs and test fixtures from OpenAPI and AsyncAPI specifications.

Community
Advanced
AI-SafeterAI-Safeter
10

api-documenter

Generate API documentation from OpenAPI and AsyncAPI specifications.

Community
Advanced