mcpField
O
orchestrate

orchestrate

github.com/rohitg00Agent workflows2.9k154 installsUpdated 5w ago
Repository

About orchestrate

orchestrate is a skill for developing features through structured phases and validation gates. It guides coding agents from research and confidence checks through an approval-based plan, implementation checkpoints, and review.

Key features

  1. 01Phased feature-development process
  2. 02Research with confidence-based GO/HOLD
  3. 03Plan approval before implementation
  4. 04Quality gates during implementation
  5. 05Review changes before commit
  6. 06Phase-specific agent selection

Use cases

  1. 01Building features across multiple files
  2. 02Handling unclear or complex requirements
  3. 03Making cross-cutting code changes
  4. 04Introducing patterns not established in a codebase

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rohitg00/pro-workflow --skill orchestrate

After installing, type/orchestratein Claude Code to confirm it loaded.

Details

From the project README

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:

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

When to Use This

  • Feature touches >5 files
  • Architecture decisions needed
  • Requirements are unclear or complex
  • Cross-cutting concerns (auth, logging, error handling)
  • New patterns not yet established in the codebase

When NOT to Use This

  • Quick bug fixes (just fix it)
  • Single-file changes
  • Well-understood patterns (follow existing code)
  • Documentation-only changes

Agent Selection

PhaseAgentWhy
Researchscout (background, worktree)Non-blocking exploration
Planorchestrator (opus, memory)Deep reasoning, pattern recall
Implementorchestrator (opus, memory)Full tool access
Reviewreviewer (read + bash)Security and quality focus
Debugdebugger (opus, memory)Systematic investigation

Integration with Pro-Workflow

  • Corrections during implementation trigger self-correction loop
  • Quality gates fire at checkpoints via hooks
  • Learnings are captured at the end of each phase
  • Session handoff works across phases

Comments

Markdown supported