elaboration-upsert-api-contract

Name: elaboration-upsert-api-contract
Availability: InStock
Author: tsunami28

Create OpenAPI 3.x YAML contracts from feature requirements and implementation slices.

Updated Jun 18, 2026

Search Tags:#openapi #rest #software architecture #yaml #endpoint design #api contract

Ready to run

npx skills add https://github.com/tsunami28/MindNova --skill elaboration-upsert-api-contract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: elaboration-upsert-api-contract
Source: https://github.com/tsunami28/MindNova/tree/main/.claude/skills/elaboration-upsert-api-contract
Command: npx skills add https://github.com/tsunami28/MindNova --skill elaboration-upsert-api-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating inconsistent API designs by transforming agreed software slices into a machine-readable OpenAPI contract that teams and automation can rely on.

Core Features & Use Cases

OpenAPI Contract Creation: Produces OpenAPI 3.x YAML specifications that define REST paths, schemas, authentication, and responses.
API Design Governance: Applies repository conventions such as naming rules, error models, status code guidance, and single-domain boundaries.
Use Case: When a team starts building a new HTTP endpoint, use this Skill to create the API contract that developers and quality engineers can consume before implementation begins.

Quick Start

Use the elaboration-upsert-api-contract skill to create an OpenAPI specification for the new REST endpoint based on the approved feature slice.

Frequently Asked Questions about elaboration-upsert-api-contract

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

FAQPage Schema

How do I generate an OpenAPI 3.x YAML specification from feature requirements?▼

Creating an OpenAPI 3.x YAML specification requires transforming agreed software feature slices into machine-readable API contracts. This process defines REST paths, schemas, authentication rules, and error response modeling before code generation begins.

What is API contract design and when do I need an OpenAPI specification?▼

API contract design defines REST endpoint boundaries, schemas, and error models in an OpenAPI YAML format. You need this specification before implementation begins so teams and automation can consume consistent API definitions.

How do I enforce repository conventions and error response modeling in REST endpoint design?▼

Enforce repository conventions by applying naming rules, status code guidance, and single-domain boundaries during OpenAPI specification authoring. This yields a governed API contract with consistent schema definitions and error response modeling.

Can I define authentication rules and schema definitions before code generation starts?▼

Yes, you can define authentication rules and schema definitions before code generation begins. The skill outputs an OpenAPI 3.x YAML contract containing these exact boundaries, allowing developers to consume the specification prior to implementation.

Does this approach to API design governance work for single-domain boundaries?▼

Yes, this API design governance approach explicitly supports single-domain boundaries. It applies repository conventions such as naming rules and error models to produce a focused OpenAPI 3.x YAML specification for your specific REST endpoint slice.