api-spec

Generate OpenAPI 3.0.3 specifications from project story data.

45|13|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/rakovi4/continue-framework --skill api-spec-rakovi4
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-spec
Source: https://github.com/rakovi4/continue-framework/tree/main/.claude/skills/api-spec
Command: npx skills add https://github.com/rakovi4/continue-framework --skill api-spec-rakovi4

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The api-spec Skill streamlines the creation of OpenAPI specifications for story endpoints, automating the generation process and ensuring consistency with the story's design and requirements.

Core Features & Use Cases

  • Automated Specification Generation: Generates OpenAPI 3.0.3 specifications for frontend endpoints directly from story data.
  • Customization Options: Allows users to select specific stories by name, number, or interactively through prompts.
  • Workflow Automation: Integrates with existing project structures to read from context files and update project documentation automatically.

Quick Start

To generate an API specification for a story, run /api-spec "Story name" or select the story using interactive selection.

Frequently Asked Questions about api-spec

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

FAQPage Schema
How do I generate OpenAPI specifications from project story data?

Generating OpenAPI specifications from project story data requires parsing project specifications and mockups to automate endpoint definition and versioning. This process outputs formatted OpenAPI 3.0.3 specifications directly from structured story workflows.

How do I automate OpenAPI spec generation for specific frontend endpoints?

Automating OpenAPI spec generation for frontend endpoints is done by running a command with a specific story name or number. The system reads existing project context files and updates project documentation automatically with the generated specifications.

What is the best way to keep API specifications consistent with story requirements?

Keeping API specifications consistent with story requirements is achieved by integrating specification generation directly into your structured workflow. This ensures endpoint definitions and versioning strictly adhere to the project's API design standards.

Can I interactively select stories to build an OpenAPI 3.0.3 specification?

Selecting stories interactively to build an OpenAPI 3.0.3 specification is fully supported. Users can prompt the system to choose specific stories by name, number, or through an interactive selection process.

Do I need mockups to automate endpoint definition and versioning?

Mockups are required alongside project specifications to automate endpoint definition and versioning accurately. Parsing these structured inputs ensures the generated OpenAPI specifications match the intended frontend design.

What are the limitations of automating API specification generation from story data?

Limitations of automating API specification generation include the strict dependency on structured project story data, specifications, and mockups. Projects lacking organized context files or adhering to non-standard API design workflows may not produce accurate OpenAPI outputs.