Skip to content

rohitg00/pro-workflow / skills/orchestrate

orchestrate

Unverified

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

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
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).Stars: 195kUpdated Claude CodeCodexVerifiedInstall