Vibe Squad

One coordinator. Five model families. Seventy-one specialists, all written in Markdown you can read and edit.

Seven specialists live at once across Claude and Codex — each card its own model, profile, elapsed clock and scoped surface — while the coordinator works in the pane beside them.

---

Vibe Squad is for people who like vibe coding but want more structure than one enormous chat. You talk to Chrono, the coordinator. Chrono turns your goal into a plan, picks the specialist and model that fit each part, runs workers in isolated git worktrees, and calls for independent review when the risk warrants it.

You can ask it to:

• "Build a polished landing page, test it in the browser, and show me the result."
• "Research this product idea, compare the competitors, and turn it into a cited brief."
• "Audit this authorized smart-contract target, keep every test in scope, and package only reproduced findings."

What's underneath

• The right model for each job — every specialist is tied to the model that suits its work, not to whichever one you happen to be chatting with.
• Each task runs in its own worktree — a copy of the repo, with a written list of the files it may change, and nothing merges until its checks pass. That list is enforced when changes are integrated, not while the worker runs: a worker executes on your host with your permissions, so treat this as an autonomy tool, not a containment boundary. See the note under Quickstart.
• A different model checks the work — so no model signs off on its own reasoning.
• It remembers — what a run learns is written down and read back before the next one, so a lesson paid for once isn't paid for twice.

The product is the instruction layer, and it is Markdown all the way down. Modes, specialist briefs, capability cards, and skills are files you can open and change. Code handles only what must not be guessed: launching, worktree isolation, identity checks, atomic publication, admission control, and Git-integration boundaries. Judgment stays with the models.

Quickstart

macOS, for now. You need tmux, fswatch, jq, curl, Python 3.13, uv, and authenticated native CLIs for Claude, Codex, Gemini (agy), Kimi, and Grok.

Memory lives outside the public repository. Create a private vault once:

mkdir -p "$HOME/Obsidian-Chrono"
printf '%s\n' '{"vault_id":"my-private-vault","schema_version":1}' \
  > "$HOME/Obsidian-Chrono/.chrono-vault"
export CHRONO_VAULT_ROOT="$HOME/Obsidian-Chrono"

Then clone and launch:

git clone https://github.com/mtarcure/claude-vibe-squad.git
cd claude-vibe-squad
uv sync                                # create the pinned Python 3.13 environment
bash docs/install/install-pre-commit-hook.sh  # install the reviewed local leak guard
bin/squad doctor
bin/squad up