project-orchestrator

Orchestrate multi-phase project implementation by delegating coding to background Claude agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/cncorp/arsenal --skill project-orchestrator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-orchestrator
Source: https://github.com/cncorp/arsenal/tree/main/dot-claude/skills/project-orchestrator
Command: npx skills add https://github.com/cncorp/arsenal --skill project-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill orchestrates the complete implementation of a project plan by delegating all work to background Claude agents. The orchestrator manages the process but NEVER writes code itself, and it coordinates isolated development, review, and integration across multiple phases.

Core Features & Use Cases

  • Orchestrates multi-phase project implementation by delegating all coding to background agents
  • Enforces branch isolation for each phase: one branch per phase for implementation, review, and fixes
  • Implements review-driven quality gates to ensure issues are resolved before progression
  • Generates and updates an orchestration log and phase tracking, keeping stakeholders aligned
  • Ideal when you have a PROJECT_PLAN.md and want deterministic, agent-driven execution without hand-coding

Quick Start

  • Prepare a PROJECT_PLAN.md that outlines Implementation Roadmap with clearly defined phases
  • From your integration branch, initiate the orchestration process to spawn agents for Phase 1
  • Monitor progress, collect reviews, and iterate phase-by-phase until all phases pass

Frequently Asked Questions about project-orchestrator

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

FAQPage Schema
How do I orchestrate multi-phase project implementation with Claude agents?▼

Orchestrate multi-phase projects by delegating all coding to background Claude agents spawned with isolated branches per phase. The orchestrator manages workflow, enforces code review gates, and updates PROJECT_PLAN.md tracking without writing code itself, ensuring deterministic phase-by-phase execution.

What's the best way to automate branching and code review workflows across project phases?▼

Create branch-isolated workflows where each phase gets its own branch for implementation, review, and fixes. Spawn Claude agents via background jobs to handle coding while the orchestrator monitors progress, collects reviews, and gates progression until quality standards pass.

Can I use Claude agents to automatically implement a project plan without manual coding?▼

Yes. Prepare a PROJECT_PLAN.md with clearly defined phases, then initiate orchestration to spawn agents for each phase. Agents handle all coding in isolated branches while the orchestrator coordinates reviews, tracks progress in logs, and gates advancement between phases.

When should I use agent-driven orchestration instead of manual development?▼

Use agent orchestration when you have a detailed PROJECT_PLAN.md, need deterministic multi-phase execution with built-in code review gates, require branch isolation per phase, and want automated progress tracking without hand-coding each implementation step.

What prerequisites do I need to set up before starting project orchestration?▼

Prepare a PROJECT_PLAN.md outlining your Implementation Roadmap with clearly defined phases. Start from an integration branch and ensure your environment supports background job monitoring and branch-based workflows for phase isolation.

How does orchestration ensure code quality between phases?▼

Orchestration enforces review-driven quality gates: each phase must pass review before progression. The orchestrator updates phase tracking and orchestration logs, monitors agent progress via background jobs, and blocks advancement until issues are resolved.