Your engineering crew for Claude Code.

Subagents, skills, commands and hooks: specialists that plan, build, review and ship a change in any stack, with the rules that matter enforced by gates.

npx crewforth init

Read the docs ⭐ Star on GitHub

Existing repository? npx crewforth adopt lands everything on its own branch. main is never touched.

A one-minute overview: plain Claude Code, the install, the crew at work, the gates, Studio and the handoff.

Twelve specialists, one order

Every request has an owner. A routing hook names it beside your prompt, and quality rises stage by stage before anything is committed.

Understand

crew-planner

Scope and acceptance criteria when a request is unclear.

Produce

crew-backend-expert
crew-database-expert
crew-devops-expert
crew-docs-agent
crew-frontend-expert

The change itself, in any stack.

Audit

crew-performance-expert
crew-privacy-agent
crew-refuter
crew-security-expert
crew-test-expert

Run in parallel by /crew-review.

crew-commit-agent
crew-review-agent

A clean review, then a commit that waits for you.

Hand off

crew-session-manager

Session fill, and the state written down for next time.

All 40 skills behind them →

Rule → gate

A commit waits for your approval, in every permission mode.
A commit needs a clean review of that exact diff.
A destructive command is refused before it runs.
No key, token or AI-authorship trace reaches history.

Every hook and rule →

Measured in the open.

The same prompt runs in a project with Crewforth and in a bare one, graded on what each left on disk. The rule a result must meet is written down before the run.

Every result is published with its reasoning, including the ones where the rule did not hold.

Read the evals →

Install your way

npxnpx crewforth initnpx crewforth adopt

Claude Code plugin/plugin marketplace add Crewforth/crewforth/plugin install crewforth@crewforth

No Node? Use the release archive →

When a new version is published, Claude asks once at the start of a session. It never updates on its own.