Update Specification Skill: Keep AI-Ready Specs Current
Updates an existing specification file so AI tools can use it, following a fixed template. Listed in github/awesome-copilot.
- Installs
- 9.2K
- on skills.sh
- Stars
- 40.7K
- on GitHub
- Updated
- Oct 2026
- last repo commit
update-specification makes your agent revise a specification file when requirements or code change. The spec is rewritten to be precise and self-contained, with a front-matter header and a fixed set of sections. Requirement IDs such as REQ-001, SEC-001 and CON-001 keep items easy to find.
Specs live in /spec/ and are named with a purpose first, for example schema-, tool-, data-, infrastructure-, process-, architecture- or design-. The skill names the file as ${file}, so tell your agent which spec to update.
Good for
- Teams keeping a spec in a /spec folder as requirements change
- Developers who changed code and need the spec to match
- Architects who want requirements written clearly enough for AI agents
Install update-specification
Claude Code
- 1
Copy this prompt.
Install the update-specification skill in Claude Code. Run this command: npx skills add https://github.com/github/awesome-copilot --skill update-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
Update an existing specification file for the solution, optimized for Generative AI consumption based on new requirements or updates to any existing code.
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
- Installs on skills.sh
- 9,221 (Nov 2, 2026)
- Last repo commit
- Oct 30, 2026
- Files in the folder
- 1 file: SKILL.md
What it includes
Edits the existing spec at ${file} for new requirements or changed code
The spec must define requirements, constraints and interfaces so a generative AI can use it without outside context.
Try: “Update the spec in /spec/ for the new retry rule”
Write ·
Update the spec fileSaves in /spec/ as [a-z0-9-]+.md, starting with a purpose word
The purpose words are schema, tool, data, infrastructure, process, architecture or design.
Naming and locationKeeps a header with title, version, dates, owner and tags
Title and date_created are filled in; version, last_updated, owner and tags are marked optional.
Front matterFills an Introduction and 11 numbered sections
Purpose and scope, definitions, requirements, interfaces, acceptance criteria, test strategy, rationale, dependencies, examples, validation criteria, and related specs.
Template sectionsLabels items such as REQ, SEC, CON, GUD, PAT, AC, EXT, SVC, INF, DAT, PLT and COM
Acceptance criteria use Given-When-Then where it fits.
ID prefixesAsks for explicit language, defined acronyms, structured lists and edge cases
Seven practices are listed, such as separating requirements from recommendations and keeping the document self-contained.
AI-ready writing rules
From the official docs
Permissions
Low risk
The skill edits spec files you point it at, so a heavy rewrite could change a document your team relies on. Commit first and review the diff.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It rewrites a spec file in place
The skill updates the existing spec to fit its template, which can reshape sections you wrote by hand. Keep the file in version control and review the diff. github.com
Community content, not reviewed by GitHub for you
The awesome-copilot README says the customizations are sourced from third-party developers and asks you to inspect them before installing. Read the SKILL.md first. github.com
Technical details
| Scopes |
|
|---|
Questions
What does update-specification do?
It revises an existing spec file to match new requirements or changed code. It rewrites the spec in a strict template meant to be easy for AI tools to read.
How do I install it?
Use the install box above. It is a single SKILL.md, so the skills CLI route or a folder copy both work.
Which file does it update?
The one the prompt calls ${file}. Name the spec file in your request. New or renamed specs follow the /spec/[a-z0-9-]+.md naming rule.
Is it for .NET only?
No, but the test section of the template lists MSTest, FluentAssertions and Moq "for .NET applications" as example frameworks. Replace them with your own.
Is it safe?
It edits spec files and bundles no scripts. The risk is an over-eager rewrite of a document you rely on, so keep the spec in version control and read the diff.
Does it work in Claude Code or the Claude app?
The file is a standard SKILL.md, and the install box shows how to place it in Claude Code or upload it to Claude. The awesome-copilot README targets GitHub Copilot, and nothing in the repo says this skill was tested in Claude.
Information
updated Nov 2, 2026
- Repository
- github/awesome-copilot
- Folder
skills/update-specification
Sources
Docs, issue trackers and discussions this page is built from.
Show all 2Hide
- update-specification SKILL.md · github.com
- github/awesome-copilot README · github.com