bemyagent vs squid
One markdown bootstrap file that scaffolds a structured workspace for any coding agent — persistent project docs plus a task tree run through a Think→Task→Execute→Verify cycle with human pacing gates. — versus — Claude Code plugin that turns a feature spec into a reviewed PR through a 5-agent pipeline — PA → SWE → Tester → PR-Reviewer → On-Call — with exactly two human gates.
Same job — disciplined, human-gated task execution for coding agents — different bet: squid is a Claude Code plugin driving a 5-agent spec→PR pipeline; bemyagent is a tool-agnostic markdown protocol a single agent follows. Pick squid for enforced structure on Claude Code, bemyagent for portability.
| bemyagent | squid | |
|---|---|---|
| Stars | 22 | 136 |
| Forks | 6 | 20 |
| Language | HTML | Shell |
| License | MIT | Apache-2.0 |
| Last activity | 8 days ago | 4 days ago |
| Topics | coding, memory | coding, orchestration |
| Curated connections | 4 | 6 |
bemyagent — the curator's take
Try it when your agent keeps drifting on multi-session projects and a flat CLAUDE.md isn't enough structure: one file bootstraps a disciplined docs+work tree, it's agent-agnostic (self-registers into .cursorrules/AGENTS.md), and INTERACTIVE mode gives you real plan/result approval gates. NOT for quick scripts or single-session work — the ceremony outweighs the benefit — and it's a young one-maintainer protocol: no enforcement layer exists, so compliance depends entirely on the model faithfully following a long ruleset; weaker models will ignore half of it. Expect to adapt conventions yourself rather than lean on tooling or community.
squid — the curator's take
Squid is for people who already live in Claude Code and are tired of re-explaining team conventions every session: markdown specs + five adversarial agents (no agent both writes code and judges it) turn a spec into a PR while you only show up to approve the plan and merge. When NOT: you don't use Claude Code (it's a plugin, not a standalone tool), your stack is Rust/Java/mobile (specs are Python/TS/Go for now), or you already trust an in-house pipeline. Early days and opinionated by design — adopt the opinions or skip it.