Skip to content
sinc-LLMBook a 30-minute call

Public project · Claude Code

Crews

Plan a crew around the work, then check the handoffs.

A crew planner with task-specific roles, model and effort seats, and a guard for planned dispatch.

MIT

Software use follows the repository’s terms. Installation, integration and model usage are separate considerations.

Usage pattern
  1. Describe roles
  2. Generate crew plan
  3. Dispatch matched seats

A guide to how the project is used. Read its requirements and limits before installation.

Your starting point

A task that needs several bounded roles and a clear check at the end.

Ad hoc subagents can duplicate work, exceed scope or review their own results.

The capability to add

Know who owns each deliverable and which work can run together.

Typed role requirements produce a crew plan; an enabled seat guard checks dispatch against that plan.

What’s in the project

A tool you can inspect.

Capabilities

  • Task-specific research, produce, integrate and check roles
  • Model and effort selection within the configured catalog
  • A seat guard for matching planned dispatch

Requirements

  • Claude Code on Linux or macOS; uv for the plugin MCP server
  • Working hooks for dispatch enforcement; hooks use Python 3.9+ or fall back to uv

Important limits

  • The planner does not dispatch work itself; the host executes its plan.
  • If plugin hooks are disabled or their runtime is unavailable, guard enforcement is unavailable.

A useful fit

Consider this when…

Claude Code users splitting a larger task into explicit roles and handoffs.

A different starting point

Choose another approach when…

Teams expecting a hosted service, universal agent control or Windows support.

Inspect the implementation

Public source, with a specific scope.

The repository and the files below show the implementation available to inspect. They do not establish results for your workflow.

Reviewed source snapshot: 93a0c61c6e35.

Compatibility and behavior must be checked in your environment. No customer-result or quality-improvement guarantee is implied.

Code and implementation help

Choose the help you need.

Software. MIT. Read the repository’s terms and installation guide.

Setup and integration. Bring your current tools, a workflow and your desired result. Scope, fees, delivery and support are confirmed before work starts.

Operating costs. Existing CLI subscriptions, model-provider usage and hosting may apply depending on the tool and your configuration.

Compare published service scopes and prices ↗

Your next step

Inspect it. Then decide what to add.

Use the source and requirements to judge fit. If you want help adapting it to your workflow, start with a scoped conversation.

Discuss Crews setup ↗

No setup fee is agreed or payment taken on this page.

A closer look

Which scope fits your work?

Prices describe different engagements. Final scope, timing and fees are confirmed in the proposal.