swarm-execute
Skill0 starsChanged 4 months agoApache-2.0View on GitHub
Use to implement a plan artifact from `/swarm-plan`, or a free-text implementation task with contract-first TDD + Review-Fix Loop. Tier (`low | auto | high | max`) scales builder model, loop rounds, review breadth, and Codex code-diff gate.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- dralgorhythm/claude-agentic-frameworktheir own version, first seen Jul 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- dralgorhythm/claude-agentic-framework★ 118same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- finalizeSkill
- swarm-planSkill
- swarm-reviewSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 9 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
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
- Distinctive: line 53
When plan present, read and parse handoff block for Tier, Scope, Reversibility, Overlays.
- Very specific: line 59
Read classify.md. Apply plan-header signals first (primary).
- Very specific: line 83
Default: EnterPlanMode with meta-plan path.
- Very specific: line 133
One-shot only: never re-enter Review-Fix Loop — prevent two-family thrash.
- Very specific: line 163
Use task checkpoint for work-in-progress saves
- Distinctive: line 177
NO completing tasks without passing quality gates
- Distinctive: line 178
NO leaving work uncommitted locally
- Distinctive: line 179
NO exceeding 8 parallel workers
- Distinctive: line 180
NO pushing to remote
- Distinctive: line 181
NO running stub and test phases concurrently (sequential only)
- Very specific: line 182
NO mid-flow AskUserQuestion during classification — ambiguity resolve at meta-plan gate
- Distinctive: line 184
ALWAYS report blockers immediately
- Distinctive: line 185
ALWAYS validate git status shows clean before commit
- Distinctive: line 186
ALWAYS update design record before adding tests for unspecified behaviors
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Execution Orchestrator — Tiered
Thin dispatch layer. Phase plans in sibling tier files
(tier-low.md, tier-high.md, tier-max.md); this file parse
args, classify target (classify.md), resolve overlays
(overlays.md), optional gate on meta-plan approval, hand
off to matching tier file. Shared content (worker table, loop
design principles, constraints, handoff) stay here — phase-by-phase
execution in tier files.
Argument syntax
/swarm-execute [tier] <plan-artifact-or-task> [--flags]- tier (optional):
low | auto | high | max. Defaultauto. - target (one of): plan artifact path (
.claude/state/plans/plan_*.md); free-text task description. - flags (convention: flags before positional):
--builder=sonnet|opus--tester=sonnet|opus--reviewer=haiku|sonnet|opus--doc-reviewer=haiku|sonnet--loop-rounds=1|2|3--review=minimal|full|adversarial--codex/--no-codex--dry-run/--form— meta-plan preview (--formuseAskUserQuestion; imply--dry-run)
Workflow
1. Parse arguments and detect plan artifact
Detect target type:
- Path ending
.md(typically under.claude/state/plans/) → plan-artifact mode - Else → free-text mode
When plan present, read and parse handoff block for Tier, Scope, Reversibility, Overlays; parse phase definitions; extract "Subsystems Touched" from plan body.
2. Classify (only when tier=auto)
Read classify.md. Apply plan-header signals first (primary); fall
back to free-text signals (pointer to /swarm-plan's classify.md when
no plan artifact) only for axes plan header miss. Produce
candidate tier + confidence flag + overlay set.
3. Resolve overlays
Final config = tier defaults (overlays.md per-tier table) +
classifier overlays + user flag overrides. User flags always win
(except tier=max's mandatory --builder=opus).
4. Meta-plan gate (single consolidated approval point)
Fire when ANY of: --dry-run, --form, tier resolved to max, or
classification marked low-confidence. Only user-prompt
point — no mid-flow AskUserQuestion during classification.
Write .claude/state/plans/meta-plan_execute_[feature].md with:
Classification (tier + rationale + plan-header source), Overlays
(+ rationale), Workers per phase, loop-rounds budget, Estimated cost,
Whether Codex fires, Not Doing (push, PR creation).
Approval UI (always single interaction):
- Default:
EnterPlanModewith meta-plan path; resume on approve. If skill resume afterExitPlanModeunreliable in practice, fall back toAskUserQuestionwith Approve / Edit / Cancel options. --form: ONEAskUserQuestioncall with ≤4 batched axis questions (Tier / Builder / Loop-rounds / Codex), first option "Recommended".
On reject: re-draft meta-plan with rejection rationale and re-present once.
5. Announce final config (always)
Print before loading tier file:
Swarm execute
Tier: high (from plan header)
Target: .claude/state/plans/plan_foo.md
Overlays: builder=sonnet, loop-rounds=3 (tier default)
codex=on (signal: plan Reversibility=One-Way Door Medium)
Workers: stub/impl sonnet, 1 arch reviewer,
3 review rounds (full breadth)
Codex diff review: on (after loop converges)
Proceed? (Ctrl+C to abort; re-run with explicit tier to override)6. Dispatch to tier file
Read matching tier-{low,high,max}.md and execute its phase
plan. No phase content duplicated here.
Review-Fix Loop
Protocol: see canonical Review-Fix Loop in workflow-swarm.md. Protocol auto-load for swarm-skill contexts via workflow-swarm.md path-scoping. Per-tier loop config (rounds, perspectives) set in each tier file.
Cross-Model Adversarial Pass — shared protocol
See overlays.md "codex axis" for when fires per tier. Use
codex-adversary skill with scope code-diff against branch diff
after Claude loop converges.
- Preconditions: loop exited,
task verifygreen, working tree clean except intended diff. - Invocation: delegate to
codex-adversarywith--scope code-diff --base main --model <tier model>(high→terra, max→sol;--codex-model=luna|terra|soloverrides — seeoverlays.md). Codex loads repo context (AGENTS.mdwhen present) automatically — do not inject project context. - Triage: Actionable → one-shot
worker-builderfix pass, gatetask verify. Deferred → summary. Stated-convention / trivia → dropped with count. - One-shot only: never re-enter Review-Fix Loop — prevent
two-family thrash. If one-shot fix fails
task verify, revert and promote findings to deferred. - Unavailable path:
CLAUDE_PLUGIN_ROOTunset / companion non-zero / empty output → logCross-model gate skipped: <reason>and continue. Gate, not blocker (at tier=max, surface skip prominently).
Worker assignment (shared across tiers)
See .claude/rules/workflow-swarm.md for worker types, models, tools,
focus modes.
| Phase | Worker | Model |
| Stub | worker-builder (focus: stubbing) | sonnet / opus |
| Verify arch (high/max) | worker-reviewer (focus: spec-compliance, phase: post-stub) | sonnet |
| Verify arch (max) | worker-architect | opus |
| Specify | worker-tester (focus: specification) | sonnet |
| Implement | worker-builder (focus: implementation) | sonnet / opus |
| Review Stage 1 | worker-reviewer (spec-compliance + test-coverage) | sonnet |
| Review Stage 2 | worker-reviewer / worker-doc-reviewer / worker-architect / worker-researcher | per role |
| Cross-model | codex-adversary (code-diff) | — |
Max concurrent workers: 8 (per workflow-swarm.md).
Quality Gates & Git Protocol
task --listto discover workflows;task verifyis final gate (subsystem verify runs during review loop)- Stage and commit with conventional commit message; never push
- Use
task checkpointfor work-in-progress saves
Living Design Records
Plan artifacts = living documents. When implementation reveal behavior or edge case not in design record: update plan artifact first, write corresponding test, then implement.
Plan Status block (mutate on phase entry + advance)
Mutate the ## Status block in the plan referenced by .claude/state/current_plan.md: flip Step on phase entry / Stub→Specify→Implement→Review-Fix transitions; increment Active phase on plan-phase advance; set Step: awaiting /swarm-review when the final phase completes (don't clear current_plan.md — /finalize does that). Skip silently when no current_plan.md / no Status block. Full mutation table → plan-status.md.
Constraints
- NO completing tasks without passing quality gates
- NO leaving work uncommitted locally
- NO exceeding 8 parallel workers
- NO pushing to remote
- NO running stub and test phases concurrently (sequential only)
- NO mid-flow
AskUserQuestionduring classification — ambiguity resolve at meta-plan gate - ALWAYS report blockers immediately
- ALWAYS validate
git statusshows clean before commit - ALWAYS update design record before adding tests for unspecified behaviors
Handoff
- To
/swarm-review: after implementation complete, for adversarial review - To
/qa-engineer: for acceptance testing
Next Step — copy-paste to continue:
/swarm-review$ARGUMENTS
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
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.

