TrellisSpec, task and memory layer that lives in your repo: .trellis/ holds conventions, PRDs and journals, auto-injected each session — one workflow across 20 coding-agent platforms.
Why switchSame insight — persist project structure into the repo so any agent starts with context — at opposite weights: bemyagent is one bootstrap markdown; Trellis is a full spec/task/journal system with sub-agents and 20-platform installers.
Full comparison → beadsDistributed graph issue tracker for coding agents on Dolt: dependency-aware beads replace markdown plans — bd ready/claim/close, cell-level merge, push/pull across machines and agents. CLI + MCP.
Why switchbemyagent bootstraps a markdown task tree in one file; beads replaces exactly that with a dependency-aware tracker once parallel agents start stepping on each other.
Full comparison → loop-engineeringReference repo plus npm CLIs (loop-init/audit/cost) for loop engineering: designing scheduled, gated control loops that prompt and orchestrate AI coding agents — Grok, Claude Code, Codex — over time.
Why switchBoth impose a disciplined, tool-agnostic operating structure on coding agents through scaffolding, an explicit work cycle and human gates. bemyagent structures a single human-paced session (Think→Task→Execute→Verify); loop-engineering structures scheduled, unattended loops that run over time. Pick bemyagent for interactive pacing, loop-engineering for autonomous automation.
Full comparison → three-man-teamA disciplined 3-agent dev process as context files — Architect plans, Builder builds the brief, Reviewer gates — running in one Claude Code session via subagents. Token-frugal by design.
Why switchBoth are markdown-first process scaffolds for coding agents. bemyagent bootstraps one structured workspace with a Think→Task→Execute→Verify cycle; three-man-team splits the discipline across three role personas with review as a hard gate.
Full comparison → squidClaude 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.
Why switchSame 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.
Full comparison → brain.mdFile-based durable memory for coding agents: brain-setup scaffolds a BRAIN.md protocol + brain/ directory of decisions, requirements and constraints — plain Markdown in your repo, written via CLI.
Why switchBoth bootstrap a persistent markdown workspace for any coding agent; bemyagent adds a task tree and workflow, brain.md goes narrower and deeper on durable decisions.
Full comparison →