new-spec
Skill301 starsChanged 11 days agoApache-2.0View on GitHub
Create a new specification document in the specs/ directory. Use when the user asks to create a spec, write a specification, draft a spec, add a new spec, or generate a specification document.
12 other projects use a version of this.
Adopted by
Most recently taken up by
- eugenelim/agent-ready-repotheir own version, first seen Nov 14, 2026
- phanijapps/memextheir own version, first seen Oct 17, 2026
- kitloomlk-stack/spec-driven-planning-kittheir own version, first seen Oct 15, 2026
- gabo963/claude-skillstheir own version, first seen Oct 15, 2026
- RocketChat/Rocket.Chat.Electrontheir own version, first seen Oct 8, 2026
- a16z/jolttheir own version, first seen Oct 8, 2026
Used with
Projects with it also use release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- RocketChat/Rocket.Chat.Electron★ 1.7ksame name
- a16z/jolt★ 1.1ksame name
- eugenelim/agent-ready-repo★ 31same name
- brayandiazc/project-starter-template-es-ai★ 15same name
- eugenelim/llm-wiki-kit★ 12same name
- brayandiazc/project-starter-template-en-ai★ 2same name
- jhlee0409/omni-harness-kit★ 2same name
- dabodamjan/app-idea-to-spec★ 0same name
- gabo963/claude-skills★ 0same name
- kitloomlk-stack/spec-driven-planning-kit★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- js/AGENTS.mdAGENTS.md
- sandbox-image/AGENTS.mdAGENTS.md
- amika-annotationsSkill
- amika-cliSkill
- create-cli-release-commitSkill
- create-sdk-release-commitSkill
- distill-sessionSkill
- make-stacked-prsSkill
- naive-reader-reviewSkill
- release-commit-sandbox-imageSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Create the file: Use the name specs/<NNN>-<name>.md.
- Very specific: line 42
Do not create a .d directory when you create the spec.
- Very specific: line 65
Put supporting documents for specs/NNN-name.md in specs/NNN-name.d/.
- Distinctive: line 66
Create the directory when you add the first document.
- Very specific: line 67
Do not rename or renumber the .d directory alone.
- Very specific: line 71
Keep all design decisions in the .md spec, not in .d/.
- Very specific: line 73
When a .d directory has more than two or three files, add a README.md to it.
- Distinctive: line 77
Do not commit raw output, such as large logs or benchmark dumps.
- Distinctive: line 82
Use specs to record product, design, and technical decisions.
- Distinctive: line 86
Write for human reviewers.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Create a New Specification
Procedure
- Find the next number. List the files in
specs/. Find the highest number prefix. Add 1 to it. Use three digits with leading zeros. For example, if002-foo.mdis the highest, the next number is003. - Create the file. Use the name
specs/<NNN>-<name>.md. Get<name>from$ARGUMENTS. If$ARGUMENTSis empty, ask the user for a name. - Use this template:
# <Title>
## Overview
<Brief summary of what this spec covers>
## <Main Sections>
<Detailed content organized into logical sections>
## Dependencies
<External requirements, if any>
## Future Considerations
<Known limitations and potential future work>- Write the content. Work with the user to fill in the spec from their requirements.
Do not create a .d directory when you create the spec. Create it only when
the spec has supporting documents.
Supporting Documents: the .d Directory
A spec can have a sibling directory. The directory has the same name as the
spec, but .d replaces .md:
specs/019-sandbox-ssh-stream-relay.md <- the spec
specs/019-sandbox-ssh-stream-relay.d/ <- its supporting documentsThe .md file is the specification. It tells what the team will build and
why. It must be complete and easy to review alone.
The .d directory holds working documents that support the spec. These
documents would make the spec too long. Examples are implementation plans,
test plans, critiques, run evidence, prompts, follow-up lists, and design
notes.
Obey these rules:
- Put supporting documents for
specs/NNN-name.mdinspecs/NNN-name.d/. Create the directory when you add the first document. - Do not rename or renumber the
.ddirectory alone. If you rename the spec, rename its.ddirectory too. - The
.mdspec is the authority. If a.d/document does not agree with the spec, the spec is correct. Update the spec or correct the document. - Keep all design decisions in the
.mdspec, not in.d/. The spec can link to.d/for more detail. A reader must understand the spec without.d/. - When a
.ddirectory has more than two or three files, add aREADME.mdto it. TheREADME.mdlinks back to the spec. It lists each document and gives its purpose in one line. - A document in
.d/can have its own.ddirectory. The same rules apply. - Do not commit raw output, such as large logs or benchmark dumps. Commit only evidence that you examined and cleaned.
Guidelines
- Use specs to record product, design, and technical decisions.
- Give sufficient detail to implement the spec. Do not paste large blocks of code.
- Tell why you made a decision, not only what the decision is.
- Write for human reviewers.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

