
Claude-Crew
Opinionated Claude Code starter kit + crew: spawn isolated Claude Code workers to ship tasks in parallel
About this project
# The Story Behind Claude Crew
Claude Crew started from a frustration I kept running into while building projects with AI coding assistants.
The promise of modern coding agents is incredible. They can write code, review code, debug issues, generate documentation, and even understand large codebases. But as projects grew larger, I found myself facing a different problem: there was still only one agent working at a time.
In a real engineering team, work naturally splits. One engineer investigates a bug while another writes tests. Someone reviews architecture decisions while another updates documentation. Progress comes from parallel execution.
With AI agents, that parallelism was missing.
I noticed that whenever I was working on something non-trivial, I would repeatedly think:
"Why can't I have another Claude instance investigate this while I continue working here?"
The obvious solution was spawning more agents, but existing approaches felt messy. Multiple terminals quickly became chaotic. Context got mixed together. Agents stepped on each other's changes. There was no clean way to manage them like teammates.
That led to the core idea behind Claude Crew:
What if AI agents worked more like a software engineering team?
Instead of one giant context window handling everything, each task could be delegated to an isolated worker. Every worker would have its own git worktree, its own objective, and its own execution environment. The main session would act as a supervisor, coordinating work rather than doing everything itself.
Once that idea clicked, the project became much larger than a simple spawning script.
I started building the environment I wished existed when starting a new AI-assisted project:
* Shared memory and project conventions * Structured planning workflows * Automatic hooks and guardrails * Token optimization utilities * Specialized agents for reviewing, researching, and validating work * Parallel workers that could operate independently * A supervision layer that tracked progress without consuming model tokens
The goal was never to build a fully autonomous software factory.




