agentleFS
tamesystemstamesystems/intent-engineering-skills/skills/decide/SKILL.md

decide

Skill0 starsChanged 39 days agoMITView on GitHub

Choose a sufficient intervention from credible alternatives using evidence, constraints, tradeoffs, and reversibility, and preserve why. Use before consequential implementation or whenever multiple materially different approaches remain viable.

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 9 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

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

  • 0

    Common

    Most of the 50 edited versions we read keep these.

  • 4

    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:

    Identify real decision drivers: Use only factors that materially distinguish acceptable approaches: correctness, simplicity, reliability, …

    line 13
  2. Distinctive:

    Generate credible alternatives: Consider more than one serious approach when consequences justify it.

    line 14
  3. Distinctive:

    Collapse risky assumptions: If the choice hinges on an uncertain claim, investigate or prototype it instead of reasoning indefinitely from …

    line 15
  4. Distinctive:

    Prefer the smallest sufficient commitment: When outcomes are comparable, avoid irreversible or speculative complexity.

    line 17

“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

Decide

Choose what to do and preserve why. Do not confuse generating options with making a decision.

Work

  1. Frame the decision. Reference the governing intent, specification, grounded state, and relevant findings.
  2. Identify real decision drivers. Use only factors that materially distinguish acceptable approaches: correctness, simplicity, reliability, compatibility, performance, security, reversibility, operational burden, cost, time, etc. Avoid decorative scorecards.
  3. Generate credible alternatives. Consider more than one serious approach when consequences justify it. Include defer/do-nothing when legitimate; do not manufacture strawmen.
  4. Collapse risky assumptions. If the choice hinges on an uncertain claim, investigate or prototype it instead of reasoning indefinitely from assumption.
  5. Compare consequences. Examine coupling, failure modes, migration, blast radius, reversibility, maintenance, and what each option makes easier or harder.
  6. Prefer the smallest sufficient commitment. When outcomes are comparable, avoid irreversible or speculative complexity.
  7. Record the rationale. Capture rejected serious alternatives and the evidence or tradeoff that decided the choice.

Return

  • Decision
  • Rationale
  • Alternatives considered
  • Tradeoffs accepted
  • Assumptions
  • Reconsider when — evidence or conditions that would invalidate the decision.

Failure signals

Watch for choosing the first workable idea, architecture by fashion, fake alternatives, unexplored assumptions that dominate the choice, and reopening settled decisions without new evidence.

Done when

There is enough justified commitment to realize the change without silently re-litigating the same decision, and the conditions that should reopen it are explicit.

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.