create-specification skill (GitHub) for Claude Code: write AI-ready spec files

create-specification makes your agent write a structured spec file for a solution, in a format other AI tools can read.

Installs: 13.6K; on skills.sh
Stars: 40.7K; on GitHub
Updated: Oct 2026; last repo commit

create-specification is a skill from GitHub's awesome-copilot collection. Tell the agent what the spec is for and it writes a Markdown file in a /spec/ folder, named spec-[a-z0-9-]+.md and starting with one of seven purposes: schema, tool, data, infrastructure, process, architecture or design.

The file follows a template with a short introduction and 11 numbered sections: purpose and scope, definitions, requirements, interfaces, acceptance criteria, test strategy, rationale, dependencies, examples, validation criteria and related specs. The test-strategy section of the template lists .NET example frameworks (MSTest, FluentAssertions, Moq). The skill bundles no scripts. SKILL.md uses the placeholder ${input:SpecPurpose} for the topic, so say clearly what the spec is for.

Good for

Developers who want a written spec before they hand work to an AI agent
Architects documenting a component, API or process
Teams standardising how requirements and acceptance criteria are written

Install create-specification

Claude Code

Copy this prompt.

Install the create-specification skill in Claude Code. Run this command:

npx skills add https://github.com/github/awesome-copilot --skill create-specification

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

From its listing on skills.sh. Source.

What's in the skill

When it loads

Create a new specification file for the solution, optimized for Generative AI consumption.

Sections in SKILL.md

Best Practices for AI-Ready Specifications
1. Purpose & Scope
2. Definitions
3. Requirements, Constraints & Guidelines
4. Interfaces & Data Contracts
5. Acceptance Criteria
6. Test Automation Strategy
7. Rationale & Context
8. Dependencies & External Integrations
External Systems
Third-Party Services
Infrastructure Dependencies
Data Dependencies
Technology Platform Dependencies
Compliance Dependencies
9. Examples & Edge Cases

Key facts

Author: github (GitHub account that owns the repo)
Source repo: github/awesome-copilot
Installs on skills.sh: 13,577 as of 2026-11-02
GitHub stars: 40,666 (whole repo) as of 2026-11-02
License: MIT
Last repo commit: 2026-10-30
Files: 1 file (SKILL.md)
skills.sh audits: Gen Agent Trust Hub pass, Socket pass, Snyk pass

What it includes

Seven rules: precise language, structured formatting, defined acronyms, self-contained.
AI-ready writing rules
Saves to /spec/ as spec-[a-z0-9-]+.md, starting with a purpose such as schema or process.
Write · File naming and location
title, version, date_created, last_updated, owner and tags.
Front matter
Purpose and scope, definitions, requirements, interfaces, acceptance criteria.
Introduction and sections 1 to 5
Test automation strategy, rationale and context, dependencies and external integrations.
Template sections 6 to 8
Examples and edge cases, validation criteria, related specifications.
Template sections 9 to 11

From the official docs

Permissions

Low risk

The skill bundles no scripts and writes a spec file into a /spec/ folder. The repository README says its contents come from third-party developers, so read SKILL.md before installing.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

Repo content is from third parties
The awesome-copilot README says the customizations are sourced from third-party developers and to inspect any agent and its documentation before installing. github.com

Technical details

Scopes	A /spec/ folder in your project

Questions

How do I install the create-specification skill?

Use the install box above. It is a single SKILL.md, so the skills CLI command or copying the folder into your skills directory both work. After installing, ask the agent to create a spec and say what it is for.

Where does the spec file go?

SKILL.md says to save it in the /spec/ directory with a name like spec-architecture-payments.md. The name must match spec-[a-z0-9-]+.md and start with the high-level purpose: schema, tool, data, infrastructure, process, architecture or design.

What sections does the spec have?

A short introduction, then 11 numbered sections: purpose and scope, definitions, requirements, interfaces, acceptance criteria, test strategy, rationale, dependencies, examples, validation criteria and related specs. The tool list above groups them.

Does it need an API key or setup?

The skill does not mention one and bundles no scripts. It writes one Markdown file for you to review.

Does it work with Copilot only?

It comes from GitHub's awesome-copilot repository, but the skill is Markdown instructions. The install box lists Claude Code, Claude app and Codex routes. SKILL.md uses ${input:SpecPurpose} as a placeholder for the topic, so state the purpose in your prompt.

Is create-specification safe to install?

It bundles no scripts and writes a Markdown file to a /spec/ folder in your project. The repository README warns that the collection comes from third-party developers and says to inspect any agent and its documentation before installing.

Information

updated Nov 2, 2026

Repository: github/awesome-copilot
Folder: skills/create-specification

github/awesome-copilot skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

create-specification SKILL.md · github.com
awesome-copilot README · github.com
create-specification on skills.sh · skills.sh