record-decision
Skill1 starsChanged 15 days agoMITView on GitHub
Capture a sticky technical decision as a one-page ADR — context, options, choice, consequences. Use when the user asks to record a decision, write an ADR, or lock a choice of library, shape, or approach. Do not start a full design document.
10 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- jabbott-iii/Tidepooltheir own version, first seen Nov 8, 2026
- Walsworth-Group/physkittheir own version, first seen Nov 8, 2026
- Memolok/Claude-plugintheir own version, first seen Nov 6, 2026
- rpraharaj/ai-sdlcedited, 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 verify.
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.
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-sdlc★ 018% same
Wrote their own version · 9
- hardness1020/VibeFlow★ 8same name
- Walsworth-Group/physkit★ 7same name
- iopsystems/skills-mcp★ 6same name
- YangFan-Code-Star/context-dev★ 2same name
- jabbott-iii/Tidepool★ 1same name
- Memolok/Claude-plugin★ 1same name
- shioki/Cursor-Knowledge-Management-System★ 1same name
- deanmikan/ai-native-company-starter★ 0same name
- Luis85/agentic-workflow★ 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 repository34 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- open-prSkill
- performanceSkill
- production-passSkill
- ready-to-mergeSkill
- refactor-safelySkill
- resolve-conflictsSkill
- revert-changeSkill
- review-changeSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- start-projectSkill
- upgrade-depsSkill
- verify-uiSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-prdSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Read AGENTS.md if present.
- Distinctive: line 18
Write when the choice will be expensive to reverse: store shape, public API, a new dependency family, a cross-cutting pattern.
- Distinctive: line 20
If the decision is not yet made, list options and ask the blocking question.
- Distinctive: line 24
Use the first that exists:
- Very specific: line 28
If none: write in the reply, and offer to create docs/adr/ using this repo's markdown style
- Distinctive: line 43
No secrets. No host or vendor lock-in language unless that *is* the decision.
- Distinctive: line 51
Do not implement the decision unless the user asked.
“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 decision
Write a short architecture decision record. This is not a design doc (no delivery plan, no multi-page spec). If the user wants README, API reference, or a runbook, that is write-docs. If they want a PRD, that is write-prd. If they want system shape, that is write-architecture. If they want how this initiative will be built, that is write-design. This skill locks one expensive choice those docs can point at.
Read AGENTS.md if present.
When to write one
Write when the choice will be expensive to reverse: store shape, public API, a new dependency family, a cross-cutting pattern. Do not ADR a local rename or a one-line bug fix.
If the decision is not yet made, list options and ask the blocking question. Do not pick for the user when the options trade product risk.
Find the home
Use the first that exists:
docs/adr/,doc/adr/,adr/,docs/decisions/- A path
AGENTS.mdnames - If none: write in the reply, and offer to create
docs/adr/using this repo's markdown style
Number the file like existing ADRs (0007-title.md). If there are none, start at 0001.
Copy sections from assets/adr-template.md in this skill directory. Keep every heading; write n/a when a section does not apply. Do not invent extra headings. If that file is missing, use the same headings: Context, Drivers, Options, Decision, Consequences.
Fill from evidence
- Context is facts: current constraint, failing approach, requirement. Link files/symbols you read.
- Drivers are the two or three forces that pick among the options (or
n/aif Context is enough). - Options are real alternatives (including "do nothing"). At least two.
- Decision is one option. If the user already chose, quote them; do not relitigate.
- Consequences include what you are giving up and when to revisit.
- Related points at the PRD, architecture, or design that this choice serves.
No secrets. No host or vendor lock-in language unless that is the decision.
Done
- Path of the ADR or the full text in the reply
- The decision in one sentence
- Whether a later
data-change/implement-change/write-docs/write-designshould follow
Do not implement the decision unless the user asked. Do not commit unless asked.
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.