I’ve been experimenting with Claude agent teams and have decided that this needs to be default in claude bootstrap. IMO, single-agent coding sessions have a pattern - Claude writes code, we review it, we catch issues, Claude fixes them, repeat. The review burden is still on us. And TDD discipline? It’s the first thing that slips when you’re moving fast. My Solution: Agent Teams with enfroced pipeline When you run /initialize-project, Claude now spawns a full team of specialized agents that implement features in parallel - each following a strict pipelin that cannot be skipped (hopefully :)): Spec → Tests → Verify Tests FAIL → Implement → Verify Tests PASS → Code Review → Security Scan → Create Branch → Create PR Task dependencies enforce this ordering structurally. A feature agent literally cannot start implementing until the Quality Agent independently runs the tests and confirms they fail. The Merger Agent cannot create a PR until the Security Agent passes the scan. The Team Every project gets 5 permanent agents + 1 feature agent per feature: Agent: Team Lead What It (He?She?:)) Does: Orchestrates everything. Breaks work into features, creates task chains, assigns work. Never writes code. Agent: Quality Agent What It Does: Enforces TDD. Verifies specs are complete, tests actually fail (RED), tests actually pass (GREEN), coverage >= 80%. Agent: Security Agent What It Does: OWASP Top 10 scanning, secrets detection, dependency audit. Blocks on Critical/High. Agent: Code Review Agent What It Does: Runs multi-engine reviews (Claude/Codex/Gemini). Blocks on Critical/High. Agent: Merger Agent What It Does: Creates feature branches, stages only feature-specific files, creates PRs with full pipeline results. (Tbh, i am not sure we need it. I’ve experimented with team lead doing merges vs merger agent and currently settled on merge agent). Agent: Feature Agents What It Does: One per feature. Writes spec, writes failing tests, implements, validates. Hands off to other agents at each gate. How It Works Say your project has 3 features: auth, dashboard, payments. /initialize-project asks for your features Spawns 8 agents (5 permanent + 3 feature agents) Creates 30 tasks total (10 per feature, each with dependency chains) All 3 features run in parallel Shared agents (Quality, Review, Security, Merger) process tasks as they unblock Result: 3 PRs, each with test results, review summary, and security scan The cross-agent verification is key: the Quality Agent independently runs tests rather than trusting the feature agent’s report. The Security Agent independently scans rather than trusting the review. Trust but verify. The 10-Task Chain (per feature) auth-spec (Feature Agent writes spec) auth-spec-review (Quality Agent reviews completeness) auth-tests (Feature Agent writes failing tests) auth-tests-fail-verify (Quality Agent confirms ALL tests fail) auth-implement (Feature Agent writes minimum code) auth-tests-pass-verify (Quality Agent confirms ALL pass + 80% coverage) auth-validate (Feature Agent runs lint + typecheck) auth-code-review (Review Agent runs /code-review) auth-security-scan (Security Agent runs OWASP checks) auth-branch-pr (Merger Agent creates branch + PR) Each task uses addBlockedBy to reference its predecessor. Structurally impossible to skip. Why Not Just a Single Agent? Well, this is a bit subjective but here’s what i think: Different agents catch different things. A feature agent focused on implementation won’t scrutinize its own security. A quality agent whose only job is checking test discipline won’t let a “tests pass” slip through without actually running them. It’s the same reason code review exists in human teams - the person who wrote it shouldn’t be the only one checking it. Quick Start
Install git clone https://github.com/alinaqi/claude-bootstrap.git ~/.claude-bootstrap cd ~/.claude-bootstrap && ./install.sh # Set the experimental flag (agent teams are experimental in Claude Code) export CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
I don’t any project without this and also added it to existing projects.
In any project claude > /initialize-project
Or spawn a team on an existing project:
/spawn-team What Else Is in Claude Bootstrap This is v2.5.0 with 54 skills total (may seem too spread thin but other ppl and I keep adding more skills). Other highlights: Multi-engine code review (v2.3.0) - Claude + OpenAI Codex + Google Gemini, run one or all three Existing repo support (v2.2.0) - /analyze-repo detects your tech stack, conventions, and missing guardrails Ralph Wiggum loops - Auto-iterating TDD loops that run until tests pass <- I will be removing it as I don’t think we really need it Workspace awareness (v2.4.0) - Multi-repo contract tracking and dependency graphs 54 skills covering Python, TypeScript, React, React Native, Flutter, Android, Supabase, Firebase, DynamoDB, Stripe, Shopify, and more GitHub: https://github.com/alinaqi/claude-bootstrap submitted by /u/naxmax2019
Originally posted by u/naxmax2019 on r/ClaudeCode