Design API Stories

Generate API design stories from requirements, a domain model, and API standards. This is Emmanuel Paraskakis's method for designing APIs with LLMs — the stories become the bridge between product requirements and an OpenAPI specification.

When to Use

Use when the user says /design-api-stories or asks to generate API user stories from requirements.

Inputs

The user must provide three files (or paste their content). Files can be named anything — identify each file by its # Title heading or content, not by filename.

1. Requirements — ICP, needs, pain points, use cases, benefits. The "why" and "what." Look for a heading like # Requirements, # Research, or similar.
2. Domain — Data objects, properties, enums, object relations. The "nouns." Look for a heading like # Domain, # Domain Model, or similar.
3. API Standards — Style guide, naming conventions, path rules, security, error handling. The "how." Look for a heading like # API Standards, # Style Guide, or similar.

If any file is missing, ask the user to provide it before proceeding.

Working Example