bemyagent vs Trellis
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 — Spec, 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.
Same 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.
| bemyagent | Trellis | |
|---|---|---|
| Stars | 22 | 13k |
| Forks | 6 | 739 |
| Language | HTML | TypeScript |
| License | MIT | AGPL-3.0 |
| Last activity | 20 days ago | today |
| Topics | coding, memory | coding, memory |
| Curated connections | 5 | 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.
Trellis — the curator's take
Attacks the right problem — agents restart from zero every session — with the boring, durable fix: files in the repo, not a memory service. Team-shared specs are the real moat; one engineer's hard-won rules compound for everyone. It's opinionated though: the 4-phase loop (brainstorm → implement → check → update-spec) only pays if the team actually adopts the process — half-adopted, .trellis/ rots into stale paperwork. AGPL-3.0: fine to use, but check your company's license policy. Skip it for weekend projects; this is process overhead that needs a team to amortize.