generate-api-spec

Generate RESTful API specifications from feature.md into structured endpoint docs.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/clover-storm/agentic --skill generate-api-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-api-spec
Source: https://github.com/clover-storm/agentic/tree/main/.claude/skills/generate-api-spec
Command: npx skills add https://github.com/clover-storm/agentic --skill generate-api-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines API planning by automatically generating RESTful API specifications from feature briefs, reducing manual drafting time and ensuring consistency across documentation.

Core Features & Use Cases

  • Automated API spec generation: Converts feature definitions into comprehensive API endpoints, schemas, and error handling.
  • Design-to-doc mapping: Produces structured API docs suitable for OpenAPI-like formats to guide implementation.
  • Use Case: Ideal for product teams and API designers who want to translate requirements into concrete API contracts before coding begins.

Quick Start

Provide a feature document path to generate API specs, e.g., feature_path: specs/feature.md, and invoke the skill to produce specs/new_api_endpoint.md.

Frequently Asked Questions about generate-api-spec

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

FAQPage Schema
How do I generate REST API specifications from feature requirements?

This skill automatically converts feature briefs into comprehensive REST API specifications with endpoints, schemas, and error handling. Provide a feature document (feature.md) as input, and it produces structured API documentation suitable for OpenAPI-like formats to guide implementation.

What's included in the generated API spec output?

Generated specs include RESTful endpoints, request/response schemas, error handling definitions, and structured documentation formatted for OpenAPI compatibility. Output is written to specs/new_api_endpoint.md for immediate use in backend planning.

Can I use this to document existing APIs or only for new designs?

This skill translates feature definitions into API contracts before coding begins, making it ideal for design-phase documentation. It converts product requirements into concrete endpoint specifications rather than reverse-engineering from existing implementations.

Do I need OpenAPI knowledge to use API spec generation?

No prior OpenAPI expertise required. The skill handles the technical specification structure automatically. Provide a feature document describing requirements, and it produces OpenAPI-like structured documentation ready for developer handoff or implementation.

How does this reduce manual API documentation work?

Automated spec generation eliminates manual drafting of endpoints, schemas, and error responses by extracting requirements from feature briefs. This ensures consistency across documentation and accelerates the design-to-implementation cycle for product and API teams.