agentleFS
KeremozdemirraKeremozdemirra/strategy-agent/skills/karar-notu/SKILL.md

karar-notu

Skill0 starsChanged 3 months agoMITView on GitHub

Bir karar için yapılandırılmış karar notu üretir — seçenekler, ödünleşimler, kriterler, tavsiye ve geri dönüş planı. \"Karar vermem lazım\", \"A mı B mi\", \"hangisini seçmeliyim\", \"artı eksi çıkar\", \"karar notu yaz\" dendiğinde kullan. Also triggers on \"I need to decide\", \"A or B\", \"which one should I pick\", \"help me weigh these options\", \"write me a decision memo\". Kararın dayandığı dış veriyi sıfırdan toplamak için kullanma; onun için deep-research kullan.

  • In this repositoryOne other file it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Do not move on to options until these are settled.

    line 20
  2. Distinctive:

    Write each option in its strongest form — do not weaken one so it is easy to beat.

    line 33
  3. Very specific:

    If it runs long, write it to a file (decisions/YYYY-MM-DD-<topic>.md) and put the summary in the conversation.

    line 68
  4. Distinctive:

    Do not write with more certainty than the evidence carries.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 memo

The aim is not to make the decision. It is to make the right decision visible on its own.

1. Frame the decision — the step that matters most

  • What is the real question? Under most "A or B" questions sits a badly framed one. "Which CRM should we buy" may actually be "what is broken in our sales process".
  • By when? What does delay cost?
  • Is it reversible? Reversible decisions get made fast; long analysis on them is waste. Say so explicitly.
  • Who is affected, and who has to approve?

Do not move on to options until these are settled.

2. Set the criteria BEFORE the options

Three to five criteria, weighted. Writing criteria after seeing the options is fitting the test to the answer you already want. Do not break the order.

3. Lay out the options

  • At least three. If two are already being discussed, you find the third.
  • "Do nothing" is always an option — evaluate it every time.
  • For each: what it requires (money, time, people), what it gains, what the risk is, how hard it is to undo.

4. Weigh them honestly

Write each option in its strongest form — do not weaken one so it is easy to beat. Mark what you do not know. Ask "what information would reverse this decision?" and write that down.

5. Write it

# Decision: <one sentence>
**Status:** draft | decided
**Date:** | **Owner:** | **Reversible:** | **Deadline:**

## Context  (why now? 3-5 sentences)

## Criteria
| # | Criterion | Weight | Why it matters |

## Options
### A) <name>
What it means: | Pros: | Cons: | Cost: | Risk:
### B) ...
### C) Do nothing

## Comparison
| Criterion | A | B | C |

## Recommendation
**<option>** — because <the 1-2 reasons that actually decide it>.

## What would change this recommendation
## What we do not know
## Fallback plan  (what we do if it turns out wrong, and the signal that tells us)
## Next steps
- [ ] who / what / when

If it runs long, write it to a file (decisions/YYYY-MM-DD-<topic>.md) and put the summary in the conversation.

Rules

  • Do not dodge the recommendation. "It depends" is useless. Give your recommendation and show your reasoning; the user is free to reject it.
  • Do not write with more certainty than the evidence carries.
  • On a financial or legal decision: give information, do not make the decision, and note where professional advice is required.

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.