Agent skill

orchestrate

Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.

Rohit Ghumare73,165★ · +3,601/wk · 3 repos on radarProfile →
claude-codecodexcursor
Install
npx skills add rohitg00/pro-workflow --skill orchestrate --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 2 KB
Bundled scripts: none
Path: skills/orchestrate/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,760 · +95 this week
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 │ └── P

More from pro-workflow
All skills →
About this skill
What does the orchestrate skill do?

Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.

How do I install it?

Run `npx skills add rohitg00/pro-workflow --skill orchestrate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rohitg00/pro-workflow, a repository with 2,760 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going