Orchestrate

This is scaffolding for building features that need more than just coding. It walks you through research, planning, implementation, and review phases with explicit approval gates between them. The core idea is forcing yourself to stop and validate before proceeding, especially when confidence is low or you're touching more than five files. The agent selection table is practical: scout for exploration, orchestrator for planning and building, reviewer before commit. Honestly, this feels less like a skill and more like a workflow discipline you bolt onto your existing process. Use it when requirements are fuzzy or you're making architectural calls. Skip it for straightforward fixes where you already know what to do.

skills.sh installs: 167
GitHub stars: 2.9K
last updated: Jun 8, 2026

View on GitHub

Install

$ npx -y skills add rohitg00/pro-workflow --skill orchestrate --agent claude-code

Installs into .claude/skills of the current project.

Files

Orchestrate - Multi-Phase Feature Development

Build features through structured phases with validation gates.

The Pattern

/develop <feature>
  │
  ├── Phase 1: Research (orchestrator agent)
  │   └── Score confidence → GO/HOLD
  │
  ├── Phase 2: Plan (orchestrator agent)
  │   └── Present plan → wait for approval
  │
  ├── Phase 3: Implement (orchestrator agent)
  │   └── Execute plan → quality gates
  │
  └── Phase 4: Review (reviewer agent)
      └── Code review → commit

Usage

When asked to build a feature:

Start with research: Delegate to the orchestrator agent or scout agent to explore the codebase
Wait for GO/HOLD: Don't proceed if confidence is below 70
Present a plan: List all files to change, the approach, and risks
Get approval: Never implement without explicit "proceed"
Implement step by step: Quality gates every 5 edits
Review before commit: Run the reviewer agent on changes