claude-crew

Claude Crew

A Claude Code multi-agent orchestration plugin for solo SaaS developers.

한국어

Pipeline

crew-interview → crew-plan → crew-dev
   WHAT            HOW         DO

Stage	Role	Output
crew-interview	What to build — requirements interview, product design	spec.md
crew-plan	How to build it — technical analysis, task decomposition	contract.md
crew-dev	Build it — implementation, code review, QA	working code + PR

Installation

In Claude Code:

/plugin marketplace add jjlabsio/claude-crew
/plugin install claude-crew

Or install locally:

/plugin install /path/to/claude-crew

Initial Setup

Run once after installation:

/crew-setup

• .gitignore / .gitattributes migration (.crew/ git tracked)
• HUD statusline installation
• Per-agent provider/model configuration

Usage

Development Pipeline

/crew

The orchestrator starts and briefs the current status.

Quick Task Delegation

/crew-do "clean up login error messages"
/crew-do                         # runs the active task if one exists

/crew-do invokes the Dev agent in direct mode for small fixes, bug patches, and clearly scoped tasks. If Dev's default provider is Codex, code exploration, editing, and verification happen inside the Codex runtime; Claude handles only result summarization and follow-up coordination.

/task remains dedicated to memory/queue management. To execute a saved task, mark it active with /task work {id} then run /crew-do.

Task Management

/task add "description"          # add a task (captures conversation context)
/task add "description" --next   # urgent — insert at top of queue
/task work 3                     # start working on task #3 (reads related files + briefs)
/task start                      # start working on the top-priority task
/task done                       # mark active task complete
/task bump 4                     # raise priority by one
/task top 7                      # move to top of queue
/task note 3 "note"              # add a note to a task
/task drop 3                     # delete a task

/tasks                           # project task board
/tasks stale                     # review tasks untouched for 30+ days
/tasks clean                     # clean up tasks completed 7+ days ago

Tasks are managed as individual files in .crew/tasks/. Each file carries state, priority, and context so work can resume across sessions without re-entering context.

Agent Team

Agent	Role	Used in
Orchestrator	Talks with the user, decides delegation, drives the pipeline	all
Explorer	Codebase exploration (read-only)	interview, plan
Researcher	External research (WebSearch)	interview, plan
TechLead	Technical analysis, architecture direction	plan
Planner	Task decomposition, implementation planning	plan
PlanEvaluator	Plan validation (hard thresholds)	plan
Dev	Code implementation	dev
CodeReviewer	Code review	dev
QA	Execution verification	dev

Two Modes

claude-crew is a plugin installed into other projects. It operates in two distinct modes.

User Mode

General users who install this plugin into their own project for SaaS development.

• Slash commands to invoke directly: /crew, /crew-setup, /crew-do, /task, /tasks, /crew-interview, /crew-plan, /crew-dev.
• Debug command: node scripts/crew-agent-runner.mjs resolve --role <role> --json (shows combined provider/model/contract table).
• Works regardless of where the plugin is installed (~/.claude/plugins/... etc.) — the plugin script auto-detects its own location.

Developer Mode

People developing claude-crew itself (working inside this repo).

• node scripts/crew-agent-runner.mjs build: derives agents/{role}.md + plugin.json agents array from contracts/instructions.
• node scripts/crew-agent-runner.mjs validate: checks build output against source files + sandbox consistency.
• node scripts/crew-agent-runner.mjs install-hooks: installs pre-commit hook (prevents drift).

These commands only work inside the plugin source repo. They are blocked when called from a user environment (detected via .claude-plugin/plugin.json + package.json.name === "@jjlabsio/claude-crew").

Model Configuration

Configure per-agent provider/model via /crew-setup. Agents without explicit configuration fall back to agent_defaults in data/provider-catalog.json.

Default recommendations are grouped by the nature of each agent's role: