agentleFS
KbediakoKbediako/evergreen-codex-skills/skills/native-agent-deliberation/SKILL.md

native-agent-deliberation

Skill5 starsChanged 2 months agoMITView on GitHub

Compare competing strategies through independent agent viewpoints when a consequential decision needs evidence, tradeoffs, and dissent.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before using agents, load native-subagents-first for ownership, model selection, budgets, and lifecycle rules.

    line 10
  2. Distinctive:

    Verify material claims and compare options against the same criteria.

    line 14
  3. Distinctive:

    Use execution or validation skills for ordinary implementation and testing rather than turning those tasks into a debate.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Native agent deliberation

Frame one decision with its constraints, success criteria, known evidence, assumptions, and any real deadline. Identify what evidence could change the choice.

Before using agents, load native-subagents-first for ownership, model selection, budgets, and lifecycle rules. Select distinct viewpoints that can change the decision, such as feasibility and failure risk. Do not create a fixed number of roles merely to fill a panel.

Give each agent a bounded question and the evidence it needs. Ask for a recommendation, supporting facts, strongest counterargument, uncertainty, and a condition that would reverse the recommendation. Use structured tool controls for roles, not role markers in prompt text.

Verify material claims and compare options against the same criteria. Preserve real disagreement; distinguish evidence from inference and preference. Recommend a path or identify the specific missing fact that blocks the choice.

Return the recommendation, decisive evidence, strongest tradeoff or dissent, uncertainty, and next action. Continue implementation when already authorized. A request only for deliberation does not authorize implementation.

Use execution or validation skills for ordinary implementation and testing rather than turning those tasks into a debate.

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.