agentleFS
kings0527kings0527/pi-harness/skills/storm/SKILL.md

storm

Skill9 starsChanged 3 months agoMITView on GitHub

Multi-model adversarial debate (storm mode). Trigger when hitting judgment calls with multiple defensible positions.

8 other projects use a version of this.

Adopted by

Most recently taken up by

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 8 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:

    After advocate completes and posts to board, Critic (model 2) is spawned — reads advocate's arguments and posts the strongest case AGAINST.

    line 27
  2. Distinctive:

    After debate, you synthesize: where do they agree?

    line 29

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

Storm Mode (Multi-Model Debate)

When to trigger

  • You have exhausted your own approaches and lack confidence in your conclusion.
  • The question is inherently a judgment call with multiple defensible positions.
  • You realize you might be in a blind spot (the same logic keeps looping without new insight).

How to trigger

spawn action=debate, topic="<current-topic>", question="<the specific point to debate>"

Prerequisites

  • Storm must be enabled: /storm on <model1>,<model2>
  • A board topic must be open (the debate posts to it)

What happens

  1. Advocate (model 1) is spawned first — posts the strongest case FOR the position.
  2. After advocate completes and posts to board, Critic (model 2) is spawned — reads advocate's arguments and posts the strongest case AGAINST.
  3. Both follow strict debate discipline (evidence-based, steel-man, no drift).
  4. After debate, you synthesize: where do they agree? Where is evidence strongest? What remains unresolved?

Do NOT trigger when

  • Storm is disabled (/storm shows OFF)
  • The task is factual/mechanical with clear answers
  • You haven't first tried to solve it yourself

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.