orchestrate · rohitg00 — Claude Code skill: what it does, how to install
orchestrate coordinates multi-phase feature development with research, planning, gated implementation, and code review in Claude Code.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat orchestrate does
This skill enforces a structured development pipeline across multiple specialized agents. It starts with a research phase using the scout or orchestrator agent. If the confidence score drops below 70, work stops immediately until risks are clear.
Implementation cannot start without explicit user approval. Once the plan is approved, the orchestrator executes changes, triggering quality checkpoints every 5 edits. Any issues during editing invoke an internal self-correction loop. Finally, a reviewer agent checks the code for quality and security before committing.
Without at least 5 modified files or complex architectural choices, orchestrate adds overhead: single-file edits and simple bug fixes should bypass this workflow.
What it helps with
- Coordinate research and planning for features spanning over 5 files
- Prevent coding when agent confidence score falls below 70
- Enforce mandatory user approval on plans before modifying code
- Trigger quality gates after every 5 code modifications
- Run automated security checks via a reviewer agent before commit
Example prompts for the agent
- Use orchestrate to research and plan the new payment integration
- Run orchestrate to handle cross-cutting error handling across services
- /develop user-authentication
How to install orchestrate
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill orchestrate -a claude-code3Manually: put the files in place
~/.claude/skills/orchestrate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/orchestrate/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill orchestrate -a codex2Manually: put the files in place
.agents/skills/orchestrate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill orchestrate -a cursor2Manually: put the files in place
.cursor/skills/orchestrate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/orchestrate2Manually: put the files in place
.github/skills/orchestrate/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill orchestrate -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/orchestrateManually: put the files in place
.devin/skills/orchestrate/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about orchestrate
How to install orchestrate in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow in your Claude Code console, then run /plugin install pro-workflow@pro-workflow.
What does the orchestrate skill do?
It guides multi-phase development: research with scout, planning with human approval, staged edits with quality gates every 5 changes, and code review prior to commit.
When should you skip orchestrate?
Avoid it for single-file changes, quick bug fixes, documentation updates, or tasks following existing, well-understood patterns.
Source text
SKILL.md · MIT
---
name: orchestrate
description: Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
user-invocable: true
---
# Orchestrate - Multi-Phase Feature Development
Build features through structured phases with validation gates.
## The Pattern
```text
/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
| Phase | Agent | Why |
|-------|-------|-----|
| Research | scout (background, worktree) | Non-blocking exploration |
| Plan | orchestrator (opus, memory) | Deep reasoning, pattern recall |
| Implement | orchestrator (opus, memory) | Full tool access |
| Review | reviewer (read + bash) | Security and quality focus |
| Debug | debugger (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
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar skills
All skills for Agent setup: memory, context, orchestration →orchestrate by other authors comes first.