crew

Orchestrate multi-agent teams across separate git worktrees for parallel development.

86|9|Updated Nov 12, 2025
One-click install
npx skills add https://github.com/arpitnath/claude-capsule-kit --skill crew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew
Source: https://github.com/arpitnath/claude-capsule-kit/tree/main/skills/crew
Command: npx skills add https://github.com/arpitnath/claude-capsule-kit --skill crew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate multi-agent teams for parallel multi-branch work across separate git worktrees, handling the full lifecycle from config to cleanup to avoid merge conflicts and siloed context.

Core Features & Use Cases

  • Orchestrates team formation, lead prompts, task creation, and parallel spawning of teammates.
  • Manages per-worktree isolation, branch coordination, and health monitoring.
  • Supports a four-phase lifecycle (ASSESS, SETUP, LAUNCH, COORDINATE) to scale collaboration across multiple branches.

Quick Start

Invoke the crew orchestrator to spawn and coordinate parallel teammates across git worktrees using the /crew command.

Frequently Asked Questions about crew

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate parallel agents across git worktrees to avoid merge conflicts?

You orchestrate parallel agents by spawning teammates across separate git worktrees, ensuring per-worktree isolation for parallel development without merge conflicts. The crew command manages team formation, task creation, and lifecycle coordination.

What is the best way to coordinate multiple independent workstreams using git worktrees?

The best way to coordinate multiple workstreams is using a four-phase lifecycle: ASSESS, SETUP, LAUNCH, and COORDINATE. This manages per-worktree isolation, lead prompts, task assignment, and safe shutdown for parallel development.

Can I auto-spawn teammates for parallel development across different branches?

Yes, you can auto-spawn teammates for parallel development across different branches. The orchestrator handles teammate spawning, task creation, and health monitoring while maintaining isolation across separate git worktrees.

Do I need separate git worktrees for each agent when coordinating parallel tasks?

Yes, you need separate git worktrees for each agent to maintain per-worktree isolation. This prevents merge conflicts and siloed context, allowing 2 or more independent workstreams to operate simultaneously without interference.

How does health monitoring work for multi-agent teams in separate worktrees?

Health monitoring tracks the status of spawned teammates across separate worktrees during the COORDINATE phase. It ensures parallel development agents remain active and functional throughout the lifecycle until safe shutdown is initiated.

When should I avoid using parallel worktree orchestration for development?

You should avoid parallel worktree orchestration when managing a single independent workstream, as the overhead of config management, teammate spawning, and lifecycle coordination is designed for scaling to 2 or more parallel branches.