agentleFS
wrg32786wrg32786/aigent-os/skills/decide/SKILL.md

decide

Skill25 starsChanged 7 days agoMITView on GitHub

Apply a 12-lens decision framework. Use when weighing options, making a call, or asking for help deciding.

51 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use redesign, weekly and 8 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

  • genomewalkerSkill

    health

    Soul system health check with remediation

    Also in 3 projects that use this

  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 3

    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:

    Run any decision through the evaluation framework from system/04_decision_frameworks.md.

    line 9
  2. Distinctive:

    If confidence is low, structure it as an experiment, not a commitment.

    line 54
  3. Distinctive:

    If it's Level 3, present the analysis but explicitly say "this is your call."

    line 55
  4. Distinctive:

    Always name the trade-off.

    line 56

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

Run any decision through the evaluation framework from system/04_decision_frameworks.md. Produces a structured recommendation.

Usage

/decide [decision or opportunity to evaluate]

Process

  1. Parse the decision — What's being decided? What are the options?
  2. Run relevant lenses — Not all 12 apply to every decision. Select the 4-6 most relevant:
    • Leverage — disproportionate output?
    • Alignment — advances an active priority?
    • Reversibility — can it be undone?
    • Time Sensitivity — does waiting cost anything?
    • Revenue Impact — creates/protects/accelerates revenue?
    • Asymmetry — large upside, bounded downside?
    • Dependency — unblocks other work?
    • Cost — money, time, attention?
    • Compounding — gets better over time?
    • Simplicity — simpler path available?
    • Confidence — how certain are the inputs?
    • Opportunity Cost — what are we NOT doing?
  3. Check against principal's decision framework — system/14_decision_framework.md
    • Does it pass the pattern filter?
    • Where does it sit in the priority stack?
    • Does it pass the asymmetry test?
  4. Check authority level — system/12_authority_matrix.md
    • Is this Level 1 (just do it), Level 2 (recommend), or Level 3 (human only)?

Output Format

DECISION: [What we're deciding]
OPTIONS: [A vs B vs C]
RECOMMENDATION: [What to do and why]
KEY LENSES: [3-4 lenses that drove the recommendation]
TRADE-OFF: [What we're giving up]
CONFIDENCE: [High / Medium / Low — and why]
AUTHORITY: [Level 1/2/3 — can the AIgent act or needs approval]
NEXT ACTION: [Specific immediate step]

Rules

  • Be direct. Recommend, don't waffle.
  • If confidence is low, structure it as an experiment, not a commitment.
  • If it's Level 3, present the analysis but explicitly say "this is your call."
  • Always name the trade-off. Every yes is a no to something else.

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.

Reviews can't be read right now.

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.