Orchestrate Agent Skill
Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/rohitg00/pro-workflow --skill orchestrateThe instruction itself
7 sections, as written by the authorOrchestrate - 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
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
Other skills for the same job
different authors, same section of the catalogue
Creates detailed, sectionized implementation plans through research, stakeholder interviews, and multi-LLM review. Use when planning features that need thorough pre-implementation analysis.
This skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
Research ideation partner. Generate hypotheses, explore interdisciplinary connections, challenge assumptions, develop methodologies, identify research gaps, for creative scientific problem-solving.
Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to "run" any process. Also handles Perplexity-based research and Google Sheets data tracking.
Provide qualitative-first, evidence-traceable developmental review of scholarly works and audit low-stakes research-assessment rubrics with optional local quality controls. Never use for ranking people or consequential decisions.
Guides researchers through structured ideation frameworks to discover high-impact research directions. Use when exploring new problem spaces, pivoting between projects, or seeking novel angles on existing work.
Loop 2 of the Three-Loop Integrated Development System. META-SKILL that dynamically compiles Loop 1 plans into agent+skill execution graphs. Queen Coordinator selects optimal agents from 86-agent registry and assigns skills (when available) or custom instructions. 9-step swarm with theater detection and reality validation. Receives plans from research-driven-planning, feeds to cicd-intelligent-recovery. Use for adaptive, theater-free implementation.
Loop 1 of the Three-Loop Integrated Development System. Research-driven requirements analysis with iterative risk mitigation through 5x pre-mortem cycles using multi-agent consensus. Feeds validated, risk-mitigated plans to parallel-swarm-implementation. Use when starting new features or projects requiring comprehensive planning with <3% failure confidence and evidence-based technology selection.
How to use it
Take rohitg00/orchestrate from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.