agentleFS
DeepExtremaDeepExtrema/Tesseract/skills/decide/SKILL.md

decide

Skill4 starsChanged 14 days agoMITView on GitHub

Use when Taimoor states or asks to record a real decision — "we're going with X", "log this decision", "decide between A and B" — or when a session produces a choice that future sessions must honor. Checks Claude/Decisions.md for conflicts, then appends the decision with rationale and supersession markers.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use redesign, weekly and 10 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.
  • arjunkshahSkill

    redesign

    Redesign existing interfaces to premium quality while preserving product goals and functional behavior.

    Also in 3 projects that use this

  • gaiaaiagentSkill

    weekly

    Generate a weekly digest rolling up dailies into higher-level pattern analysis

    Also in 3 projects that use this

  • SethGammonSkill

    experiment

    Automated optimization loop with scalar fitness function. Proposes changes in isolated worktrees, measures with a metric command, keeps improvements, discards failures. Supports convergence detection and diminishing returns.

    Also in 3 projects that use this

  • kv0906Skill

    inbox

    Quick capture mode (with content) or batch processing mode (no content). GTD-style routing of inbox items to proper folders. Use "/inbox thought to capture" or "/inbox" to process.

    Also in 3 projects that use this

  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 5 projects that use this

  • genomewalkerSkill

    health

    Soul system health check with remediation

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 54 edited versions we read keep these.

  • 2

    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. Distinctive:

    If a prior entry conflicts with or is replaced by the new decision, quote it verbatim in chat and ask Taimoor to confirm the supersession.

    line 18
  2. Very specific:

    If the decision implies follow-up work, add_task each item (with due if Taimoor gave one).

    line 31
  3. Distinctive:

    If the decision changes how agents should behave in a specific repo, say so: the repo's AGENTS.md/CLAUDE.md is the enforcement point for …

    line 33

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

Decide — the decision ledger ritual

Requires the tesseract MCP server. Claude/Decisions.md is APPEND-ONLY: history is the point. Existing lines are never edited, reworded, or deleted — supersession is expressed by the new entry.

Steps

  1. read_note("Claude/Decisions.md") in full, and search_brain("<decision topic>", limit=5) for related sessions and answers — a decision made blind to its predecessors is how the ledger contradicts itself.
  2. If a prior entry conflicts with or is replaced by the new decision, quote it verbatim in chat and ask Taimoor to confirm the supersession. Do not file a conflicting decision without that call — two live contradictory entries poison every future recall.
  3. Append the new entry: rewrite the file with write_note(overwrite=True), keeping all existing content byte-identical and adding one entry at the end. Match the file's existing entry format; if in doubt: - YYYY-MM-DD <decision> — <one-line rationale> with (supersedes YYYY-MM-DD "<old decision>") when step 2 applies.
  4. Record the why, not just the what — the rationale line is what makes the entry worth reading in six months. One line; link evidence notes as [[wikilinks]] where they exist.
  5. If the decision implies follow-up work, add_task each item (with due if Taimoor gave one).
  6. If the decision changes how agents should behave in a specific repo, say so: the repo's AGENTS.md/CLAUDE.md is the enforcement point for per-repo behavior — the ledger records, it does not enforce.

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.