decision-recording
Skill0 starsChanged 7 months agoMITView on GitHub
Use when a repository should capture a high-impact engineering decision in `docs/records` instead of leaving the reasoning in chat history. Trigger for architecture changes, dependency choices, operating-rule changes, or decisions that would be expensive to reverse later.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dagarre00/claude-code-templatetheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dagarre00/claude-code-template★ 1same 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- harness-bootstrapSkill
- issue-driven-workflowSkill
- planning-workflowSkill
- review-workflowSkill
- spec-writingSkill
- subagent-workflowSkill
- technical-learning-noteSkill
- troubleshooting-workflowSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Distinctive: line 17
Write the chosen direction and its consequences.
- Very specific: line 19
Prefer docs/records/ for the note and update the records index when the decision matters beyond one task.
- Very specific: line 37
Use technical-learning-note for how the implementation works and issue-driven-workflow for task-local execution state.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Decision Recording
Capture the why behind non-trivial engineering choices so later work does not depend on memory.
This skill is for durable decision rationale, not implementation walkthroughs.
Default flow
- Confirm the decision is real, accepted, and worth keeping.
- Record the context that forced the decision.
- List the main options that were considered.
- Write the chosen direction and its consequences.
- Link evidence such as issue docs, incidents, experiments, or benchmarks.
- Prefer
docs/records/for the note and update the records index when the decision matters beyond one task.
Good fit
- selecting or removing a dependency
- changing architecture boundaries
- introducing a strong guardrail or operating rule
- choosing a workflow that other contributors must follow
Avoid for
- obvious implementation details
- temporary experiments that are not yet accepted
- one-off edits with no lasting downstream effect
Resources
- See
references/decision-checklist.mdfor the minimum record contents. - Use
technical-learning-notefor how the implementation works andissue-driven-workflowfor task-local execution state.
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.