claudeers.
// Developer Tools

multiagents-workflow

seanswarm: multi-agent workflow pack for coding agents (Claude Code / Codex / Cursor) - evidence-governed research fan-out, dual-read docs, dev delivery with…

Actively maintained
98/100
last commit 10 days ago
last release none
releases 0
open issues 0

Install with your AI

Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.

Install and set up multiagents-workflow (git-clone project) into my current project.
Found on https://claudeers.com/multiagents-workflow
Repo: https://github.com/ccai40359-wq/multiagents-workflow
Homepage/docs: —
Detected install method: git-clone → git clone https://github.com/ccai40359-wq/multiagents-workflow
Category: devtools. Platforms: api, web, mobile.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.

Claudeers Health Verdict:
active; community-verified: false. Confirm the source before running anything.
// or clone
git clone https://github.com/ccai40359-wq/multiagents-workflow

// compatibility

Platformsapi, web, mobile
Operating systems—
AI compatibilityclaude
LicenseMIT
Pricingopen-source
LanguageJavaScript

Get your FREE $2.50 API credits to access TickAtlas financial data ↗

seanswarm

seanswarm — multi-agent workflow pack for coding agents

A lightweight multi-agent workflow pack for mainstream coding agents — Claude Code, Codex, Cursor, ZCode, and other compatible hosts. Turn your coding agent into a supervised small team: research fan-out with evidence governance, dual-channel document reading, and dev delivery with independent review and visual acceptance.

中文说明


What this is

A pack of agent skills + role templates that install into mainstream coding agents (Claude Code, Codex, Cursor, ZCode). No runtime, no server, no framework — the host agent executes the protocols; the skills describe how to organize the work.

It covers four recurring scenarios:

ScenarioPiecePattern
Web researchskills/web-research-fanoutfan-out lanes → claims table → adversarial lane → cross-family arbitration → anti-scrape ladder (L0–L4)
Document readingskills/dual-readtwo independent channels read the same document, then cross-compare (match / addition / conflict)
Dev deliveryskills/dev-deliveryQA-first acceptance list → single writer → independent read-only review (diff-only) → fail-closed acceptance → fixes go back to the single writer; disjoint modules run as parallel workstreams
Visual acceptanceagents/visual-judge.md + hooks/ui-screenshot-gate.mjsrender → screenshot → per-page verdict → fix → re-render; a mechanical hook bounces "done" without screenshot evidence

Role templates live in agents/: researcher, reviewer, worker-coder, visual-judge.

Architecture

seanswarm architecture at a glance

Design principles

  • Evidence over consensus. Claims need sources; conflicts are resolved by arbitration, never by majority vote. Independent-source count > vote count; primary > secondary; newer > older.
  • Role separation, not one super-agent. A zero-write reviewer, a single writer, and a dedicated adversarial lane that hunts for counter-evidence.
  • Clean-context review. The reviewer receives the diff + requirements — never the conversation history.
  • Fail-closed acceptance. "Unknown" counts as failed; an empty diff needs an explicit waiver.
  • finder ≠ fixer. The reviewer only finds; fixes go back to the single writer; one repair round, no recursion.
  • One writer per workstream. Modules whose files are disjoint run as parallel workstreams — each still goes through the full gated pipeline, and the main session owns integration.
  • Verification before completion. No "done" without fresh run output.
  • Cheap gates beat clever prompts. The mechanical hook exists because prose alone is not enforcement.

Install

Manual (any host with skills support)

# skills → your skills directory
cp -r skills/* <skills-dir>/
# roles → your agents directory
cp agents/*.md <agents-dir>/

Common locations: ZCode ~/.agents/skills + ~/.zcode/agents; Claude Code ~/.claude/skills + ~/.claude/agents; Codex ~/.codex/skills. See adapters/ for per-platform notes.

Plugin (ZCode)

The repo ships a plugin manifest at .zcode-plugin/plugin.json. Add the repo as a plugin source and enable it.

Hook (optional)

hooks/ui-screenshot-gate.mjs is a Stop-event hook: when UI files were edited in a turn that produced no screenshot evidence, it sends the turn back to collect evidence. Wiring instructions in hooks/README.md.

Quick start

  • Research: "Research X across official docs, GitHub, and community — fan out, then verify."
  • Document: "Read this contract with a second independent pass and cross-compare."
  • Dev delivery: "Implement feature Y: QA-first, single writer, independent review. Unknown counts as failed."
  • Visual acceptance: "Render the deck to PNGs and run the visual judge page by page; fix fails and re-judge."

Skills trigger on these kinds of requests; you can also name them explicitly.

Design notes

Orchestration vs channels. The pack separates how work is organized (lanes, tiers, contracts, arbitration) from how data is actually fetched (APIs, search-index layer, direct fetch, browsers). Many failures people blame on "the model" are channel failures.

Why fan-out isn't cloning. N agents with the same question pick the same pages and reinforce the same error. Lanes must differ in at least one dimension: source type, language, stance, or model family.

Output shape. The claims-table contract every lane must return is shown in examples/claims-table-sample.md.

Cost, measured (4-lane run — the low end of the standard tier — single host): ≈0.56M tokens total, ≈5 min wall clock (parallel) + ≈1 min arbitration. Heavy tier (10–20 lanes): 1.5–4M tokens per round. Details in FIELD-NOTES.md.

The surrounding ecosystem is active. None of this pack claims to be first — the value is in the combination and the field-tested playbooks.

ProjectWhat it isHow this pack differs
Socialpranker/deepdiveResearch pipeline: parallel sub-agents, claims ledger, 5-role red team, fetch ladderClosest neighbour on the research side; this pack adds cross-family arbitration + dual-channel document reading, and stays a lightweight skill pack rather than a scripted pipeline
obra/superpowersAgentic skills framework & software-development methodologySame direction on the dev side; this pack adds the visual gate + mechanical screenshot hook and ships a much smaller surface
Weizhena/Deep-Research-skillsStructured deep-research skill, human-in-the-loop, multi-platformThis pack's research skill adds adversarial lanes, arbitration and an anti-scrape ladder
mvanhorn/last30days-skillSocial-platform research skill (single-agent checkpoint architecture)Different architecture; see its channel engineering for social platforms
zhjai/agent-arenaCross-model debate / review protocolSame "heterogeneous models" idea applied to code review; this pack applies it to research conflicts and bans majority voting explicitly
eforge-build/eforgeSpec-to-verified-code build system, blind adversarial reviewThis pack borrows the fail-closed acceptance rule and keeps it as a portable skill
lucasfcosta/backpressuredSkills for long unattended coding sessions (incl. Playwright visual review)Similar visual-gate idea; this pack adds a mechanical (non-LLM) screenshot hook

Ideas borrowed with gratitude: diff-only review input (superpowers); fail-closed acceptance (eforge); circuit breaker + dispatch ledger + model-substitution check (ai-cross); human plan gate + minority-counsel roles (deepdive); adversarial-behaviour testing (last30days).

Status & roadmap

v0.1.0. Skills ship in English (SKILL.md) with Chinese translations alongside (SKILL.zh.md); agent role templates carry bilingual descriptions. Codex/Cursor adapters are drafts pending verification.

  • v0.2: machine-checkable evals (including an adversarial-lane behaviour test); dispatch-ledger tooling; cross-round claim reconciliation.

License

MIT — see LICENSE.

// faq

What is multiagents-workflow?

seanswarm: multi-agent workflow pack for coding agents (Claude Code / Codex / Cursor) - evidence-governed research fan-out, dual-read docs, dev delivery with independent review, and visual acceptance gates.. It is open-source on GitHub.

Is multiagents-workflow free to use?

multiagents-workflow is open-source under the MIT license, so it is free to use.

What category does multiagents-workflow belong to?

multiagents-workflow is listed under devtools in the Claudeers registry of Claude-compatible tools.

5 views
★ 54 stars
unclaimed
updated 14 days ago

// embed badge

multiagents-workflow on Claudeers
[![Claudeers](https://claudeers.com/api/badge/multiagents-workflow.svg)](https://claudeers.com/multiagents-workflow)

// retro hit counter

multiagents-workflow hit counter
[![Hits](https://claudeers.com/api/counter/multiagents-workflow.svg)](https://claudeers.com/multiagents-workflow)

// reviews

// guestbook

0/500

// related in Developer Tools

🔓

The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Curs…

// devtoolsaffaan-m/⟨JavaScript⟩★ 267,519◷ MIT[ claude ]
🔓

Makes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.

// devtoolsDietrichGebert/⟨JavaScript⟩★ 148,251◷ MIT[ claude ]
🔓

Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA

// devtoolsgarrytan/⟨TypeScript⟩★ 134,274◷ MIT[ claude ]
🔓

AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…

// devtoolssafishamsi/⟨Python⟩★ 123,348◷ MIT[ claude ]
→ see how multiagents-workflow connects across the ecosystem