orchestrate

Coordinates multi-phase feature development through research, planning, implementation, and review gates.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill orchestrate-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/orchestrate
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill orchestrate-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex features that span many files or require architectural decisions often fail when implemented ad hoc, leading to missed requirements, inconsistent patterns, and unreviewed code. This Skill structures feature development into gated phases so nothing ships without research validation, plan approval, and code review. ## Core Features & Use Cases - Four-Phase Workflow: Research with confidence scoring (GO/HOLD gate), plan presentation with explicit approval, step-by-step implementation with quality gates every 5 edits, and reviewer-agent code review before commit. - Agent Selection Matrix: Maps each phase to a specialized agent (scout for exploration, orchestrator for planning and implementation, reviewer for security and quality, debugger for systematic investigation). - Use Case: When asked to add a cross-cutting feature like authentication or logging that touches more than 5 files, use this Skill to research the codebase first, present a plan for approval, implement with checkpoints, and review before committing. ## Quick Start Ask the AI to develop a new feature using the orchestrate workflow, starting with a research phase and waiting for plan approval before implementation.

Frequently Asked Questions about orchestrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a complex feature implementation with AI agents?

Use a four-phase workflow: research the codebase with a scout agent, present a plan and wait for explicit approval, implement step by step with quality gates every 5 edits, then run a reviewer agent before committing. Each phase has a gate that must pass before proceeding.

When should I use multi-phase orchestration instead of direct implementation?

Use orchestration when a feature touches more than 5 files, requires architecture decisions, has unclear requirements, or introduces cross-cutting concerns like auth or logging. Skip it for quick bug fixes, single-file changes, and well-established patterns.

What is a confidence score gate in feature research?

The research phase produces a confidence score that determines GO or HOLD. If confidence falls below 70, implementation does not proceed, preventing work based on incomplete understanding of the codebase or requirements.

Which agent should handle code review versus debugging?

The reviewer agent handles pre-commit code review with read and bash access focused on security and quality. The debugger agent handles systematic investigation of defects with full reasoning capability and memory.

What are the limitations of phase-gated development workflows?

Phase gates add overhead that slows down trivial changes, so they are counterproductive for documentation-only edits or single-file fixes. The workflow also depends on explicit human approval between phases, which blocks fully autonomous execution.