log-decision
Skill0 starsChanged 15 days agoMITView on GitHub
Record a decision or an accepted risk in the decision log. Use when the owner or the team makes a decision.
8 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
- calven-ai/marketing-as-codetheir own version, first seen Oct 7, 2026
- azborgonovo/ai-skillstheir own version, first seen Sep 7, 2026
- TheKontextCo/kontext-claude-plugintheir own version, first seen Aug 26, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- holgerleichsenring/specification-first-agentic-development★ 41same name
- chacosoldier/compabob★ 34same name
- calven-ai/marketing-as-code★ 10same 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 repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- architecture-reviewSkill
- bootstrap-projectSkill
- capture-screenshotsSkill
- customizeSkill
- deliver-featureSkill
- design-reviewSkill
- docs-upkeepSkill
- fix-bugSkill
- handoffSkill
- implementSkill
- leadSkill
- refine-requirementsSkill
- release-readinessSkill
- reproduce-in-worktreeSkill
- security-auditSkill
- ship-prSkill
- start-taskSkill
- sync-branchSkill
- threat-modelSkill
- verify-featureSkill
- vet-dependencySkill
- write-adrSkill
The file
Files
Log a decision
Playbook files named here: when the project has its own copy at
.playbook/local/<same path>, use that copy instead.
Decision: $ARGUMENTS
- Classify it:
- Product: what customers get; the owner decided.
- Technical: how it's built.
- Process: how we work.
- Accepted risk: a known issue we're living with.
- Hard to reverse? Use
write-adrinstead and log a pointer.
- Write the row at the top of the right section (
${CLAUDE_PLUGIN_ROOT}/templates/decision-log.mdshape):- Date (absolute, YYYY-MM-DD).
- Bold one-line summary, then any detail. For product decisions, add "Owner decision".
- Why: the constraint or evidence, not "preferred".
- Source: the ticket, PR or question.
- Accepted risks also get revisit when.
- If it reverses an earlier decision, mark the old row Superseded (YYYY-MM-DD) with a pointer to the new one. Never delete it.
- If it implies a rule, add one bullet to
AGENTS.mdin the right section. - If it changes a ticket's scope, update the ticket description and say so in a comment.
Edit the Decision Log where AGENTS.md → "Tracker" says it lives (a tracker document, a Confluence page, or docs/decisions.md), following that section's editing notes. Insert right after the section's table header row.
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.

