create-specification

Creates structured Markdown specification files optimized for Generative AI consumption.

25|4|Updated Dec 21, 2025

Search Tags:#documentation #markdown #specification #requirements #technical writing #acceptance criteria #ai-ready

Ready to run

npx skills add https://github.com/thangchung/agent-engineering-experiment --skill create-specification-thangchung

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-specification
Source: https://github.com/thangchung/agent-engineering-experiment/tree/main/agentgateway-entraid-obo/.claude/skills/create-specification
Command: npx skills add https://github.com/thangchung/agent-engineering-experiment --skill create-specification-thangchung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing technical specifications that both humans and AI systems can reliably interpret is difficult, often resulting in ambiguous requirements and inconsistent document structures. ## Core Features & Use Cases - Standardized Spec Template: Generates specification files following an 11-section template covering purpose, requirements, interfaces, acceptance criteria, and test strategy. - AI-Ready Formatting: Enforces unambiguous language, defined acronyms, and structured Markdown so specifications can be consumed by Generative AI tools. - Naming & Storage Conventions: Saves files to the /spec/ directory using the spec-[a-z0-9-]+.md convention with purpose prefixes like schema, tool, data, infrastructure, process, architecture, or design. - Use Case: A team starting a new API integration asks the AI to produce a specification defining requirements, data contracts, and acceptance criteria, receiving a complete, consistently formatted spec document ready for review. ## Quick Start Create a specification for the new authentication service covering its requirements, interfaces, and acceptance criteria.

Frequently Asked Questions about create-specification

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

FAQPage Schema

How do I create a technical specification file for a software project?▼

Provide the specification's purpose and the skill generates a Markdown file following a standard template with sections for purpose, definitions, requirements, interfaces, acceptance criteria, and test strategy. The file is saved in the /spec/ directory with a descriptive kebab-case name.

What sections should a software specification document include?▼

This template includes 11 sections: Introduction, Purpose & Scope, Definitions, Requirements & Constraints, Interfaces & Data Contracts, Acceptance Criteria, Test Automation Strategy, Rationale, Dependencies, Examples, and Validation Criteria.

How do I write requirements that AI tools can understand?▼

Use precise, unambiguous language with unique identifiers like REQ-001 or SEC-001 for each requirement. Define all acronyms, avoid idioms and context-dependent references, and structure content with headings, lists, and tables for easy parsing.

What naming convention should specification files follow?▼

Files must match the pattern spec-[a-z0-9-]+.md and start with a high-level purpose prefix such as schema, tool, data, infrastructure, process, architecture, or design. They are stored in the /spec/ directory.

How do I write acceptance criteria in Given-When-Then format?▼

Structure each criterion as: Given a context, When an action occurs, Then state the expected outcome. The template uses identifiers like AC-001 and also supports declarative forms such as 'The system shall behave in a specific way when a condition occurs.'