skills.rest
rikdc
rikdcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

specify

Converts design documents into technical specifications with data models and API contracts.

2|1|Updated Jul 2, 2025
Search Tags:#architecture#specification#requirements#API contracts#data models#design-to-spec
One-click install
npx skills add https://github.com/rikdc/claude_code_template --skill specify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/rikdc/claude_code_template/tree/main/.claude/skills/specify
Command: npx skills add https://github.com/rikdc/claude_code_template --skill specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts high-level design concepts into precise, unambiguous technical specifications that developers can implement directly, reducing ambiguity and rework.

Core Features & Use Cases

  • Structured Spec Generation: Translates requirements, architectures, and design documents into formal specs including functional and non-functional requirements, data models, and API contracts.
  • Consistency & Traceability: Maintains traceability from requirements to implementation, with validation criteria and acceptance metrics.
  • Use Case: Given a design document for a new REST API, generate endpoints, data models, error handling, and example payloads ready for implementation.

Quick Start

/specify /specify <design_doc> /specify --api <service> /specify --data <entity> /specify --integration <service>

Frequently Asked Questions about specify

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

FAQPage Schema
How do I convert a design document into a technical specification?▼

Convert design documents into precise technical specifications by translating high-level concepts into structured requirements, API contracts, data models, and validation criteria that developers can implement directly without ambiguity.

What should a technical specification include for API development?▼

A technical specification for APIs must include endpoints, request/response data models, error handling, validation rules, non-functional requirements like performance and security, and example payloads ready for implementation.

How do I maintain traceability from requirements to implementation?▼

Maintain traceability by documenting functional and non-functional requirements, component interfaces, acceptance metrics, and validation criteria within the specification so every implementation decision traces back to requirements.

Can I generate specifications for data models and integrations?▼

Yes, this Skill generates specifications for data models, integration services, and architecture designs by structuring entity definitions, relationships, validation rules, and integration contracts into implementable specs.

What's the difference between a design document and a technical specification?▼

Design documents communicate concepts and decisions at a high level, while technical specifications translate those into precise, unambiguous functional and non-functional requirements with data models, interfaces, and acceptance criteria ready for code.

Related Skills

Explore More Software Engineering Skills→
AllGoodHQAllGoodHQ

marketo-parser

Parse Marketo Email 2.0 templates to extract modules, variables, and container metadata.

Official
Advanced
tejovanthntejovanthn
1

zod-validation

Validate and infer TypeScript runtime data with Zod schemas.

Community
Intermediate
Veloxia-agencyVeloxia-agency

spec-driven-workflow

Define approved specifications with Given/When/Then criteria before implementation.

Community
Advanced
hohai99hohai99

spec-driven-planning

Transform ambiguous requirements into formal specifications with goals, data models, and API contracts.

Community
Advanced