decision
Skill2 starsChanged 33 days agoMITView on GitHub
Use when the user has made an architectural, technical, or product decision and wants it recorded as a written `.context/decisions/` ADR — what was chosen, why, the alternatives, and the consequences — so the team does not re-litigate it later. Fires on "we decided X", "document this decision", "write an ADR", "record the decision to X", "log why we chose X", "we settled on X, write it up". Not for: planning multi-step work (/aidex:plan); deferring or parking an idea for later (/aidex:backlog); capturing a stakeholder/client request (/aidex:request), research notes (/aidex:research), or a settled reference (/aidex:reference); ecosystem audits (/aidex:aidex); project-state audits (/aidex:audit).
17 other projects use a version of this.
Adopted by
Most recently taken up by
- sohaibt/product-modetheir own version, first seen Nov 8, 2026
- lulufoo/lulu-workflowtheir own version, first seen Nov 6, 2026
- qbicus/skillstheir own version, first seen Oct 25, 2026
- emiljuchnikowski/ai-os-templatetheir own version, first seen Oct 20, 2026
- tsukumogami/shirabetheir own version, first seen Oct 15, 2026
- chrisalehman/bionictheir own version, first seen Oct 13, 2026
Used with
Projects with it also use brief and 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.
AnthropicSkillbrief
Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- sohaibt/product-mode★ 176same name
- aleksander-dytko/ai-pm-workspace★ 34same name
- chrisalehman/bionic★ 9same name
- mhxie/Atelier★ 5same name
- lulufoo/lulu-workflow★ 3same name
- madebypx/PXOS★ 3same name
- Jsnnmsc/10000x-engineer★ 2same name
- roethlar/AgentGovernanceBootstrap★ 2same name
- Tamircohen28/tamirs-superpowers★ 2same name
- cerebrocybersolutions/libro★ 1same name
7 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 repository21 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Read the decision conventions canon: ${CLAUDE_PLUGIN_ROOT}/skills/conventions/references/request-decision-conventions.md (Decisions section.
- Very specific: line 21
Create a single dated file: .context/decisions/YYYY-MM-DD-<slug>.md (slug kebab-case.
- Distinctive: line 29
Add a separate Options Considered (Pros/Cons) section only when two or more alternatives were genuinely weighed.
- Very specific: line 53
If the project carries a ratchet baseline (.context/.validate-baseline.json), a non-zero exit means you introduced a NEW violation — fix it …
“Common” is measured: kept by at least 6 in 10 of the 16 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
Decision
Record an architectural, technical, or product decision as an ADR in
.context/decisions/ so it is not re-litigated later. This skill is the
single-purpose entry point for decision records; the formatting canon
lives in the shared conventions reference package (not forked here).
Workflow
- Read the decision conventions canon:
${CLAUDE_PLUGIN_ROOT}/skills/conventions/references/request-decision-conventions.md(Decisions section; or.claude/skills/conventions/references/request-decision-conventions.mdif a project-level copy exists). - Create a single dated file:
.context/decisions/YYYY-MM-DD-<slug>.md(slug kebab-case; dateYYYY-MM-DD). - Front-matter per the canon — decisions use the ADR status enum
(
accepted·superseded·dropped), not the base open/doing/done vocabulary. Setsuperseded_by: decision/<filename>when one decision replaces another. - Body per the canon template: Context, Decision, Consequences are the mandated triad. Capture the deciding factor, not just the verdict. Add a separate Options Considered (Pros/Cons) section only when two or more alternatives were genuinely weighed; otherwise fold the alternatives into the Decision prose ("considered X and Y; chose Z because …"). Write the artifact in English (canon §Language).
Closing a decision
Decisions close only when superseded or dropped (an accepted ADR stays active
in place). Close atomically (stamps updated, sets status + superseded_by,
archives per D-10) instead of hand-editing:
bash ${CLAUDE_PLUGIN_ROOT}/skills/conventions/scripts/close-dated-artifact.sh decisions <slug> --status superseded --superseded-by decision/<new-adr>
bash ${CLAUDE_PLUGIN_ROOT}/skills/conventions/scripts/close-dated-artifact.sh decisions <slug> --status droppedSelf-check
Validate the artifact you just wrote and fix any violation before closing:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/conventions/scripts/validate.py --type decisionsIf the project carries a ratchet baseline (.context/.validate-baseline.json),
a non-zero exit means you introduced a NEW violation — fix it before closing.
Boundaries
| The user wants to… | Route to |
| Plan multi-step / multi-phase implementation work | plan |
| Defer / park / shelve an idea for later | backlog |
| Capture a stakeholder/client request | request |
| Investigate / research how something works | research |
| Document a settled system reference | reference |
| Audit the Claude Code ecosystem | aidex |
| Audit project state (UX/security/perf/a11y) | audit |
Related
- conventions — owns the shared documentation canon (this skill
delegates into its
references/request-decision-conventions.md).
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.