bemyagent vs three-man-team
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 — A 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.
Both 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.
| bemyagent | three-man-team | |
|---|---|---|
| Stars | 22 | 877 |
| Forks | 6 | 112 |
| Language | HTML | Shell |
| License | MIT | MIT |
| Last activity | 8 days ago | 1 months ago |
| Topics | coding, memory | skills, coding |
| Curated connections | 4 | 2 |
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.
three-man-team — the curator's take
It's a process, not software: three markdown personas with strict handoffs (plan → brief → build → review → deploy) that target the classic solo-agent failure modes — scope drift, unrequested features, token burn. The five CLAUDE.md token rules ('is this speculative? kill the tool call') are genuinely good hygiene even outside the team. Everything runs in one Claude Code session via the Agent tool; works with anything that reads context files. NOT a framework, and not for exploratory hacking — the ceremony pays off on production work and taxes quick experiments. Know the two strings attached: a commercial 'Pro' waitlist, and Arch phones a version registry at session start to offer updates (auditable, consent-gated, but it's there).