design-api-stories

Generate API design stories from requirements, domain models, and API standards.

41|7|Updated Mar 9, 2026

Search Tags:#design #api #requirements #standards #generate #stories #domain-model

Ready to run

npx skills add https://github.com/paraskakis/skills --skill design-api-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-api-stories
Source: https://github.com/paraskakis/skills/tree/main/api/design-api-stories
Command: npx skills add https://github.com/paraskakis/skills --skill design-api-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates API design stories that translate requirements, a domain model, and API standards into PM-ready narratives, bridging product goals to API design.

Core Features & Use Cases

Generate stories from three input sources (requirements, domain model, API standards).
Produce simple story format for PM review that maps to HTTP methods and resources.
Use consistent domain language and naming conventions to ensure alignment with standards.

Quick Start

Provide three inputs—Requirements, Domain, and API Standards—and ask me to generate API design stories.

Frequently Asked Questions about design-api-stories

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

FAQPage Schema

How do I translate product requirements into API design stories?▼

To translate product requirements into API design stories, provide your requirements, domain model, and API standards as inputs to generate PM-friendly narratives. These narratives map product needs to API operations for review and planning.

What are API design stories used for in product management?▼

API design stories are used to bridge product goals to API design by producing simple, PM-ready narratives. They map product requirements to HTTP methods and resources, ensuring alignment with defined naming and parameter conventions.

How do I generate API stories from a domain model and requirements?▼

To generate API stories from a domain model and requirements, input both alongside your API standards. The tool identifies themes and outputs story-focused artifacts conforming to your defined nesting, naming, and parameter conventions.

Do I need API standards and a domain model to create API stories?▼

Yes, you need API standards and a domain model to create API stories. Providing requirements, domain, and API standards as three inputs ensures the generated narratives use consistent domain language and conform to defined conventions.

Can I map product requirements to HTTP methods and resources using API stories?▼

Yes, you can map product requirements to HTTP methods and resources using API stories. The generated stories produce a simple format specifically designed for PM review that directly maps to these API operations.

What is the best way to ensure API stories conform to naming and parameter conventions?▼

The best way to ensure API stories conform to naming and parameter conventions is to provide explicit API standards as an input. The generated stories will align with these defined conventions and use consistent domain language.