log-decision
Skill10 starsChanged 39 days agoMITView on GitHub
Record a decision in memory/decision-log.md. Use whenever a discussion, meeting or thread resolves something ("log this decision", "we decided X"), or when work surfaces a decision never logged.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- holgerleichsenring/specification-first-agentic-developmenttheir own version, first seen Oct 28, 2026
- triet4p/coding-agent-stackstheir own version, first seen Oct 25, 2026
- chacosoldier/compabobtheir own version, first seen Oct 23, 2026
- azborgonovo/ai-skillstheir own version, first seen Sep 7, 2026
- TheKontextCo/kontext-claude-plugintheir own version, first seen Aug 26, 2026
- RndmCodeGuy20/ordnancetheir own version, first seen Aug 25, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- holgerleichsenring/specification-first-agentic-development★ 41same name
- chacosoldier/compabob★ 34same name
- Jerovino/EngineeringOS-template★ 2same name
- azborgonovo/ai-skills★ 1same name
- TheKontextCo/kontext-claude-plugin★ 1same name
- RndmCodeGuy20/ordnance★ 0same name
- triet4p/coding-agent-stacks★ 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 repository111 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ab-test-planSkill
- account-signalsSkill
- ad-briefSkill
- add-integrationSkill
- ads-account-auditSkill
- ads-performanceSkill
- advocacy-programSkill
- aeo-page-optimizeSkill
- ai-share-of-voiceSkill
- analyst-briefSkill
- apify-ads-intelligenceSkill
- apify-ai-search-citationsSkill
- apify-buying-signal-detectionSkill
- apify-creator-emailsSkill
- apify-easy-competitive-intelligenceSkill
- apify-ecommerceSkill
- apify-google-maps-leadsSkill
- apify-influencer-brand-collabsSkill
- apify-lead-scoring-enrichmentSkill
- apify-link-prospecting-outreachSkill
- apify-verified-email-finderSkill
- attribution-analysisSkill
- backlink-analysisSkill
- battlecardSkill
- brand-imageSkill
- brand-monitorSkill
- budget-pacingSkill
- campaign-discoverySkill
- campaign-planSkill
- case-studySkill
- chief-of-staffSkill
- churn-signalsSkill
- closed-lost-revivalSkill
- co-marketing-planSkill
- community-digestSkill
- community-planSkill
- comparison-pageSkill
- competitor-watchSkill
- content-briefSkill
- content-calendarSkill
- content-decay-monitorSkill
- content-inventorySkill
- content-strategySkill
- context-freshnessSkill
- coverage-trackerSkill
- cro-auditSkill
- data-hygiene-auditSkill
- design-qaSkill
- doctorSkill
- edit-copySkill
- email-performanceSkill
- event-followupSkill
- event-planSkill
- expansion-playSkill
- icp-refreshSkill
- keyword-clusterSkill
- landing-pageSkill
- launch-planSkill
- lead-lifecycle-specSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
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
- Very specific: line 25
Cascade if obvious: if the decision plainly invalidates something in strategy/, brand/, or memory/knowledge/, propose that edit as a diff …
- Distinctive: line 33
No attribution guessing: if you don't know who decided, ask or write "team".
“Common” is measured: kept by at least 6 in 10 of the 7 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
Log a decision
Procedure
- Extract the decision as one clean sentence of what was decided (not the discussion). If multiple decisions are tangled together, log them as separate entries.
- Add the entry to
memory/decision-log.mddirectly below the---separator (newest on top), in the file's exact format: date, decided-by, source (transcript path, PR, or link), context (1 to 3 sentences: the problem and the options weighed), follow-ups. - File the follow-ups per
integrations/tasks.mdand list them in the entry. - Cascade if obvious: if the decision plainly invalidates something in
strategy/,brand/, ormemory/knowledge/, propose that edit as a diff for review; never apply it silently.
Rules
- Append-only: never edit or delete an existing entry. A reversal is a new entry linking the old one.
- No attribution guessing: if you don't know who decided, ask or write "team".
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.