new-adr
Skill0 starsChanged 35 days agoMITView on GitHub
Record an architecture decision as the next numbered ADR in docs/adr.
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
- jamesmccomish/mp-mcptheir own version, first seen Oct 20, 2026
- maaferna/job-search-agent-systemtheir own version, first seen Oct 15, 2026
- RemiMyrset/rootstheir own version, first seen Oct 2, 2026
- pjlangley/fftheir own version, first seen Sep 23, 2026
- brayandiazc/project-starter-template-en-aitheir own version, first seen Sep 7, 2026
Used with
Projects with it also use new-spec and 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.
eugenelimSkillnew-spec
Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for…". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting proposals (use `new-rfc`) or recording decisions (use `new-adr`).
Also in 5 projects that use this
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
- eugenelim/agent-ready-repo★ 31same name
- brayandiazc/project-starter-template-es-ai★ 15same name
- eugenelim/llm-wiki-kit★ 12same name
- pjlangley/ff★ 4same name
- brayandiazc/project-starter-template-en-ai★ 2same name
- jamesmccomish/mp-mcp★ 2same name
- maaferna/job-search-agent-system★ 1same name
- MetaMindTeam/ssot-kit★ 1same name
- tstephx/book-mcp-server★ 1same name
- yashyaadav/arcadedb★ 1same 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 repository3 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-moduleSkill
- explainSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Add the record to the index table in docs/adr/README.md.
- Very specific: line 20
Do not invent facts. Where the conversation gives no answer, write TODO(author): and the question, so the gap is visible in review.
“Common” is measured: kept by at least 6 in 10 of the 12 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
Record an architecture decision
Title: $ARGUMENTS
- List
docs/adr/and take the next four-digit number. - Copy
docs/adr/template.mdtodocs/adr/NNNN-kebab-case-title.md. - Fill every section from this conversation: the context and forces,
the options with what each would cost (doing nothing included), the
decision, why it beats the others, the consequences good and bad, and
the signal that would make it worth revisiting. Use the status
Proposedunless the user has said the decision is made. - Add the record to the index table in
docs/adr/README.md. - Do not invent facts. Where the conversation gives no answer, write
TODO(author):and the question, so the gap is visible in review.
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.

