create-specifications

Generate a technical specification with architecture, data models, and API contracts from a requirements document.

5|Updated Jul 25, 2025

Search Tags:#architecture #documentation #specification #requirements #data-models #api-contracts

Ready to run

npx skills add https://github.com/tomzx/agents --skill create-specifications

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-specifications
Source: https://github.com/tomzx/agents/tree/main/skills/create-specifications
Command: npx skills add https://github.com/tomzx/agents --skill create-specifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforms a requirements document into a structured technical specification detailing architecture, data models, API contracts, component design, and sequences.

Core Features & Use Cases

Generate architecture diagrams and data models from requirements.
Define API contracts, endpoints, schemas, and error codes.
Produce a complete specification document suitable for SDLC handoff.

Quick Start

Provide a requirements document (or a path to one) and run the specification generator to produce the target file at .sdlc/features/FEAT-NNNN-<slug>/specification.md.

Frequently Asked Questions about create-specifications

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

FAQPage Schema

How do I generate a technical specification from a requirements document?▼

To generate a technical specification, provide a requirements document to the generator, which then produces architecture, data models, API contracts, and sequencing details. The output is a structured specification file written to `.sdlc/features/FEAT-NNNN-<slug>/specification.md`.

What sections are included in a complete software specification?▼

A complete software specification includes sections for Architecture, Data Models, API Contracts, Sequences, and Technical Decisions. These components ensure comprehensive coverage of system design, endpoint schemas, and component interactions for SDLC handoff.

Can I automatically create API contracts and data models from requirements?▼

Yes, you can automatically create API contracts and data models from requirements. The generator defines endpoints, schemas, error codes, and data structures, transforming raw requirements into structured technical specifications suitable for development.

Do I need a specific file format for requirements input to generate architecture diagrams?▼

You need a requirements document available or provided as a path to generate architecture diagrams. The system processes this input to produce detailed technical designs, writing the final specification output directly to your local `.sdlc/features/` directory.

What's the best way to structure specification files for SDLC handoff?▼

The best way to structure specification files for SDLC handoff is using a standardized directory path like `.sdlc/features/FEAT-NNNN-<slug>/specification.md`. This ensures all architecture, component design, and sequencing details are organized consistently for downstream development.