record-decision
Skill1 starsChanged 12 days agoApache-2.0View on GitHub
Append an architecture decision record to docs/decisions.md when a design decision is made, changed, accepted or superseded, and update the docs that reference it.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- Walsworth-Group/physkittheir own version, first seen Nov 8, 2026
- Memolok/Claude-plugintheir own version, first seen Nov 6, 2026
- rpraharaj/ai-sdlctheir own version, first seen Nov 1, 2026
- rpraharaj/ai-engineertheir own version, first seen Nov 1, 2026
- shioki/Cursor-Knowledge-Management-Systemtheir own version, first seen Oct 9, 2026
- deanmikan/ai-native-company-startertheir own version, first seen Sep 4, 2026
Used with
Projects with it also use handoff.
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.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- hardness1020/VibeFlow★ 8same name
- Walsworth-Group/physkit★ 7same name
- iopsystems/skills-mcp★ 6same name
- YangFan-Code-Star/context-dev★ 2same name
- Memolok/Claude-plugin★ 1same name
- rpraharaj/ai-engineer★ 1same name
- shioki/Cursor-Knowledge-Management-System★ 1same name
- deanmikan/ai-native-company-starter★ 0same name
- Luis85/agentic-workflow★ 0same name
- rpraharaj/ai-sdlc★ 0same name
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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-ffi-bindingSkill
- add-managed-toolSkill
- evaluate-dependencySkill
- next-taskSkill
- verifySkill
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 8 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 11
Read docs/decisions.md. The next number is the highest ADR-NNNN plus one, zero-padded to four digits.
- Very specific: line 26
Update every doc that states the decision: AGENTS.md, the overview, architecture, dependency policy, platform and subsystem docs, the …
“Common” is measured: kept by at least 6 in 10 of the 8 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
- Read
docs/decisions.md. The next number is the highestADR-NNNNplus one, zero-padded to four digits. - Accepting a
ProposedADR the user just approved: change only itsStatusline toAccepted, and add the user's words and date to its Context if they added conditions. Then go to step 5. - Otherwise draft a new ADR using the template at the top of that file:
- Status:
Acceptedonly if the user explicitly made or approved the decision in this conversation. OtherwiseProposed. - Date: today's date.
- Context, Decision, Consequences, Alternatives considered: factual and specific, with numbers where they exist.
- Revisit when: a concrete, observable trigger, not "if needed".
- Status:
- If this supersedes an earlier ADR: change only that ADR's
Statusline toSuperseded by ADR-NNNN. Do not rewrite its text. Append the new ADR at the end ofdocs/decisions.md. - Update every doc that states the decision:
AGENTS.md, the overview, architecture, dependency policy, platform and subsystem docs, the roadmap, the READMEs of the crates it shapes, andCONTRIBUTING.mdorSECURITY.mdwhen it changes how people work or report. Reference the ADR number in each place you change. If it answers a task'sDecide firstline, say so in a note under that task. - Report the ADR number and title, its status, and the docs updated. If
it's
Proposed, say what the user needs to decide.
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.