record-decision
Skill1 starsChanged 6 days agoNo licenceView on GitHub
Record a decision on a Memolok ledger: the need, the alternatives weighed, and the reasoning behind the choice. Use when the user makes or describes a choice between real alternatives that will outlast the task, however small; proposes adopting one ("we should use X"); reports a problem they mean to act on now; says "record this" or "save this decision"; or acts on a world fact or recorded outcome the ledger already holds. It changes something the ledger may already have decided → `revise-decision`; written to the ledger and ready to make final → `commit-decision`; they want to be questioned → `grill-me`.
10 other projects use a version of this.
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
- 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 verify 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.
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
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
- jabbott-iii/Tidepool★ 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 repository17 other files it gives its agents.
- commit-decisionSkill
- grill-meSkill
- helpSkill
- manage-almanacSkill
- manage-notesSkill
- memolok-citationsSkill
- memolok-methodSkill
- record-outcomeSkill
- record-previewSkill
- review-ledgerSkill
- revise-decisionSkill
- revise-intentSkill
- save-matterSkill
- send-feedbackSkill
- sharing-and-privacySkill
- startSkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 6 are distinctive, and 5 are 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“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.
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.