agentleFS
Sign inStart free
ZaxbyHubZaxbyHub/opencode-swarm/.agents/skills/swarm/SKILL.md

swarm

Skill517 starsChanged 3 days agoMITView on GitHub

Codex adapter for enabling a higher-rigor swarm-like workflow in the current Codex thread. Use when the user asks for swarm mode, maximum quality, parallel investigation, extra review rigor, or a swarm-style approach without necessarily invoking the OpenCode Swarm plugin.

We split this skill into the rules it gives an agent

8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 79 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .opencode/skills/swarm/SKILL.md for the source behavior model, then adapt it to Codex.

    line 10
  2. Very specific:

    Treat this as a workflow posture, not an instruction to call OpenCode /swarm commands.

    line 14
  3. Distinctive:

    Use parallel local reads/searches where safe.

    line 15
  4. Very specific:

    Use update_plan for visible task tracking on substantial work.

    line 16
  5. Very specific:

    Add independent review pressure through $qa-sweep, $swarm-pr-review, or self-critic checks when subagents are unavailable.

    line 17
  6. Distinctive:

    Keep the user looped in with short progress updates during longer work.

    line 18
  7. Very specific:

    no unresolved NEEDS_REVISION/BLOCKED items, and

    line 23
  8. Distinctive:

    no edits after those approvals.

    line 24

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

Swarm

Read .opencode/skills/swarm/SKILL.md for the source behavior model, then adapt it to Codex.

Codex-specific execution notes:

  • Treat this as a workflow posture, not an instruction to call OpenCode /swarm commands.
  • Use parallel local reads/searches where safe.
  • Use update_plan for visible task tracking on substantial work.
  • Add independent review pressure through $qa-sweep, $swarm-pr-review, or self-critic checks when subagents are unavailable.
  • Keep the user looped in with short progress updates during longer work.
  • For any task that edits code, tests, docs, package metadata, release notes, or skill files, final completion requires:
    1. objective validation evidence,
    2. independent implementation reviewer approval on the actual latest diff,
    3. separate critic approval after reviewer approval,
    4. no unresolved NEEDS_REVISION/BLOCKED items, and
    5. no edits after those approvals.
  • Record reviewer and critic verdicts in durable task artifacts. For issue-tracer work, use 08b-implementation-review.md and 09-final-critic.md; otherwise use task-local review artifacts unless the repo forbids artifacts.
  • Explorer subagents, a plan critic, passing tests, or self-review do not satisfy the final implementation-review gate when subagent delegation is available and swarm work is authorized.

For implementation tasks, prefer $swarm-implement; for fresh PR review, prefer $swarm-pr-review; for known PR feedback closure, prefer $swarm-pr-feedback; for bug tracing, prefer $issue-tracer.

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.

Check your setup, free