Guide · Agent skill
How to use the Create Specification agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The create-specification skill is a set of instructions that tells an AI agent to write a formal specification document for a software solution before anyone builds it. It is useful for developers who want a requirements file an AI coding tool can read and implement, and for students who want to see how a formal spec is organised. After reading this guide you will know what the skill produces, how to install it, how to ask for it, and where its limits are.
Create Specification Filesgithub/awesome-copilot · MIT Download the skill Quick start
- 1Download the ZIP. Download the create-specification ZIP from this page. It contains the SKILL.md file.
- 2Unzip into a skills folder. Unzip into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder for one repository.
- 3Or upload in the Claude apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the ZIP.
- 4Ask for a specification. Describe the feature or component and ask for a specification file in plain language.
- 5Check the output in /spec/. Find the new file in the /spec/ folder and confirm its name follows the spec-[a-z0-9-]+.md pattern.
- 6Review the content. Have someone who knows the system check requirements, interfaces and acceptance criteria.
What is an agent skill, and what does this one do?
An agent skill is a folder containing a SKILL.md file with instructions that an AI agent loads when a request matches the skill's description. This skill is one of those files. It contains no scripts and does not reach the internet; it only shapes how the agent writes.
When the skill is active, the agent follows a fixed template to write a specification for a software solution. The template covers purpose and scope, definitions, requirements and constraints, interfaces and data contracts, acceptance criteria, a test automation strategy, rationale, dependencies, examples and edge cases, and validation criteria. The text is written in precise, structured Markdown so that other AI tools can parse and implement it.
- The spec is saved into a /spec/ folder.
- File names follow the pattern spec-[a-z0-9-]+.md and start with a purpose word such as schema, tool, data, infrastructure, process, architecture or design.
- Requirements use labelled IDs such as REQ-001, SEC-001, CON-001 and AC-001.
Install the create-specification skill
Download the ZIP for this skill from this page. It contains SKILL.md. Then choose one of the following routes.
For a personal install, unzip the file into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder. In the Claude apps you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/ (available across your projects).
- Project: .claude/skills/ inside the project folder (shared with anyone using that repository).
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP.
Trigger the skill with a natural request
You do not need a special command. Describe the spec you want in plain language, naming the feature or component. The skill's description is about creating a specification file for a solution, so requests along those lines are the ones most likely to load it.
The source template names a spec purpose as the input, so state what the spec is for. Good requests name the component, the goal and, if you have one, the spec type.
- "Create a specification file for the user login feature."
- "Write an AI-ready spec for a nightly data import tool, saved in /spec/."
- "Make a design spec for the notification service before I hand it to a coding agent."
What the output looks like
The generated file starts with front matter containing title, date_created, and optional fields such as version, last_updated, owner and tags. The body then follows the numbered template from Introduction through Related Specifications.
Requirements are listed with IDs, and acceptance criteria can use Given-When-Then wording. Check that every section is filled in. The template asks for all sections to be completed appropriately, so an empty heading is a sign the agent skipped something.
- Front matter: title, version, date_created, last_updated, owner, tags (some optional).
- Sections 1 to 11, covering purpose through validation criteria.
- Acceptance criteria such as AC-001: Given [context], When [action], Then [expected outcome].
Review and use the spec with an AI coding agent
Read the generated spec before you hand it on. The skill's own guidance is that the spec should be self-contained and unambiguous, but the content reflects the agent's assumptions. Someone who knows the system must confirm the requirements, interfaces and acceptance criteria.
Once reviewed, point your coding agent at the file in /spec/ and ask it to implement the spec.
- Confirm each requirement matches what the system actually needs.
- Check interface and data contract sections against real APIs.
- Adjust the test strategy if your stack is not .NET (see the FAQ).
Safety notes: scripts and network access
This skill runs no scripts and uses no network. It is only instructions, so installing it does not give it access to your files beyond what the agent already does when writing a document in your session.
Because it writes files, review where the agent saves the output and confirm it lands in the /spec/ folder you expect.
- Runs scripts: no.
- Uses network: no.
- Requires: nothing listed.
What people use it for
- Writing a requirements file for a new feature before a coding agent implements it.
- Producing a self-contained spec for a component handed off to an AI coding agent.
- Learning how a formal software specification is structured by reading a generated example.
- Documenting interfaces, data contracts and acceptance criteria for an API or service.
Frequently asked questions
How do I install the create-specification skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps you can upload the ZIP under Settings → Capabilities → Skills.
Is the create-specification skill free?
It is published under the MIT licence on the github/awesome-copilot repository. The source does not mention pricing, so check the repository for licence terms.
What does the create-specification skill require?
The listing says it requires nothing. It runs no scripts and uses no network access, and it consists of a single SKILL.md file.
Does the skill work for non-software projects?
Not well. The template assumes a software solution with interfaces, APIs and tests, so it is a poor fit for non-software projects or quick informal notes.
Why does the test section mention MSTest and Moq?
The template's test automation section lists MSTest, FluentAssertions and Moq as frameworks for .NET applications. If your stack is different, you will need to edit that section after the agent writes it.
What are alternatives to this skill for writing specs?
The source does not compare other tools. For a lighter approach, write a short informal note instead, since this template is long and formal and can be heavier than needed.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a developer or team who wants a structured, AI-readable requirements document before building a software component, or if you are learning how formal specs are laid out. Skip it for quick notes, non-software projects, or any spec you will not review yourself, since the generated content reflects the agent's assumptions.
Download the skill