The fleet pattern: run agent loops across multiple repos in parallel, each isolated in its own git worktree, with a pluggable vendor layer spanning Claude Code, Codex, Cursor CLI, and OpenCode.
Register repos, run loops across them in parallel, each loop in its own git worktree; pluggable vendor layer (claude-code, codex, cursor-cli, opencode) — plan, review, fix, ship on a loop. Cap the run at 25 iterations; leave remaining work for the next session.
claude-code
Implementation note
When to use: you are past single-repo loops and want agent capacity across a portfolio — several services or projects receiving loop attention in parallel, the fleet pattern. How it works: register your repos with the runner, then launch loops across them in parallel, each loop isolated in its own git worktree so concurrent runs never trample each other's working state. A pluggable vendor layer means each loop can run on Claude Code, Codex, Cursor CLI, or OpenCode, and the loop shape covers plan, review, fix, and ship. Safety: worktree isolation is the core rail — parallel agents share nothing at the filesystem level, so one loop's mess cannot corrupt another's checkout. The risk that scales with the fleet is spend and review load: five parallel loops produce five streams of diffs needing human eyes. Start with one or two repos and per-loop caps before going wide.
# dare-to-be-stupid — Design (v2, refined) > A Claude Code plugin. One command, /dare , hands an idea or PRD to an autonomous > loop that authors specs, designs, builds, tests, secures, ships, fixes, and iterates > until the app passes an enterprise-production definition of done — or the budget dies. > > Named for the Weird Al song. The joke is that it runs the Ralph Loop on purpose , > with --dangerously-skip-permissions , and narrates the whole thing in the voice of an > '80s Junkion. Pre-production only. Never points at anything with users. This is v2. It keeps the strong core of the original spec (external reviewer, ratchet, guard hook, Junkion style) and adds the three phases the original left thin relative to the actual goal: PRD authoring, a design phase, and a real enterprise DoD including security, CI, docs/observability, and design quality (with quality plugins auto-installed). --- ## 0. The premise, in one paragraph The User builds documentation-first: spec → system docs → API contracts → CLAUDE.md → code. dare-to-be-stupid is the deliberate inverse, packaged as comedy that also solves two real engineering problems. It is a real build , not a joke ar