agentleFS
Sign inStart free
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/decision-log/SKILL.md

decision-log

Skill1 starsChanged 23 days agoMITView on GitHub

Maintains a decision log when a programme needs traceable choices, rationale, owners and resulting actions.

46 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use product-brief, pre-mortem 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.
  • erik-kroonSkill

    product-brief

    Turn conversation context, codebase findings, and product intent into a PRD-style brief without assuming a specific issue tracker. Use when the user wants a PRD, product brief, feature spec, or implementation-ready product artifact.

    Also in 3 projects that use this

  • Ingramradical235Skill

    pre-mortem

    Pre-mortem analysis, scenario planning, future state narratives, and contingency frameworks. Use before finalizing any Strategy Kernel, when planning major initiatives, or when preparing Plan B triggers.

    Also in 3 projects that use this

  • MicrosoftSkill

    retrospective

    Review how work went and improve the next round. USE WHEN asked for a retro, delays, or process lessons. DO NOT USE for code review or transcript replay.

    Also in 4 projects that use this

  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 3 projects that use this

  • HashiCorpSkill

    changelog

    Add a `.changelog/<PR_NUMBER>.txt` entry for a GitHub Pull Request, commit, and push.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use across governance cycles to prevent repeated debate, lost rationale and unclear authority.

    line 9
  2. Distinctive:

    Use a table with Decision ID, Date, Decision, Rationale, Authority, Owner, Actions, Dependencies, Review Trigger, Status and Source.

    line 26

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

When to use it

Use across governance cycles to prevent repeated debate, lost rationale and unclear authority.

What Claude needs

  • client-context.md and governance structure
  • Meeting records, papers and prior decision records
  • Decision rights and approval thresholds
  • Related actions, dependencies and due dates

Method

  1. Extract decisions separately from discussion, advice and provisional direction.
  2. Assign a unique reference and concise decision statement.
  3. Record the decision maker, date, authority and source record.
  4. Capture rationale, alternatives rejected and material assumptions.
  5. Link resulting actions, dependencies and review triggers.
  6. Flag conflicts, superseded decisions and gaps for confirmation.

Output format

Use a table with Decision ID, Date, Decision, Rationale, Authority, Owner, Actions, Dependencies, Review Trigger, Status and Source.

Quality checks

  • Each entry records an actual choice in unambiguous language.
  • Decision authority and source can be verified.
  • Superseded or conditional entries remain traceable.

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.

Check your setup, free