agentleFS
emiljuchnikowskiemiljuchnikowski/ai-os-template/.claude/skills/decision/SKILL.md

decision

Skill0 starsChanged 3 months agoMITView on GitHub

Appends a decision to decisions/log.md (append-only). Use when the conversation reaches an agreement worth remembering ("we decided that...", "from today we do...").

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use explore, plan and 3 more.

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.
  • genomewalkerSkill

    explore

    RLM-style recursive memory exploration - dynamically navigate the memory graph

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    If the decision changes how the OS operates → also update CLAUDE.md.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 18 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Decision — the decision journal

Append AT THE END of decisions/log.md (never edit old entries):

## YYYY-MM-DD — [title]
- **Decision:** ...
- **Why:** ... (context + rejected alternatives)
- **Consequences:** ...

If the decision changes how the OS operates → also update CLAUDE.md. Commit: docs: decision — <title>.

Checklist before committing:

  • Does this decision change the scope, permissions or write target of ANY connection? → update connections.md (the connection entry + a permission-journal row) IN THE SAME session, same commit. A permission registry that lags behind decisions is poisoning in the one file whose only job is to tell the truth.
  • Is the "Why" field a story invented after the fact for a decision already made? If so, say so in "Consequences" instead of hiding it.
  • Is it cheaply reversible, or a bet with no exit? If the answer is uncomfortable, write it into "Consequences" rather than omit it.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.