new-spec
Skill2 starsChanged 4 months agoMITView on GitHub
Scaffold a spec triplet (spec.md / plan.md / context.md) under specs/YYYYMMDD-<name>/ before starting a non-trivial piece of work. Use when a task spans multiple modules / several commits / a new ADR, or when the user says "new spec", "스펙 만들어", "plan this out", "spec this", "기획부터".
12 other projects use a version of this.
Adopted by
Most recently taken up by
- eugenelim/agent-ready-repotheir own version, first seen Nov 8, 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
- gofixpoint/amikatheir own version, first seen Oct 8, 2026
- RocketChat/Rocket.Chat.Electrontheir 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
- gofixpoint/amika★ 301same name
- eugenelim/agent-ready-repo★ 28same name
- brayandiazc/project-starter-template-es-ai★ 15same name
- eugenelim/llm-wiki-kit★ 12same name
- brayandiazc/project-starter-template-en-ai★ 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.
- adrSkill
- assessSkill
- blast-radiusSkill
- coding-guidelinesSkill
- diagnoseSkill
- handoffSkill
- introspectSkill
- localizeSkill
- pickupSkill
- tddSkill
- worktreeSkill
The file
Files
new-spec
Structure non-trivial work before coding — the spec is what keeps the work grounded on the original ask (this is where reliability comes from, not from a measurement system).
- Decide if a spec is warranted. Yes if the task touches ≥2 modules / areas, needs ≥3 commits, introduces a new ADR, or is forward-only. Skip it for small work (single file, doc-only, a follow-up) — spec ceremony on tiny tasks is net-negative.
- Scaffold: run
bash "${CLAUDE_PLUGIN_ROOT}/skills/new-spec/new-spec.sh" "<name>"from the repo root. It createsspecs/<date>-<slug>/{spec,plan,context}.mdand prints the directory. - Fill, in order:
spec.md(the original ask verbatim + acceptance),plan.md(dependency-ordered tasks), then load the tasks and surface N/M as you work. A "done" tone before all plan tasks are consumed is not allowed. context.md## 0. Resume here— write it with/harness-kit:handoffat a stopping point; a fresh session resumes from it with/harness-kit:pickup.
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.