orchestrate

Coordinate multi-step tasks through a bounded dependency graph with acceptance checks and operator gates.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill orchestrate-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/orchestrate
Command: npx skills add https://github.com/sumitake/agent-collab --skill orchestrate-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex work that spans three or more interdependent units often fails from unclear sequencing, ambiguous authority, or unverified intermediate artifacts. This Skill structures such work as a bounded task graph with explicit dependencies, acceptance checks, budgets, and stop conditions so each node is verifiable before dependents unblock. ## Core Features & Use Cases - Bounded task graphs: Define each node's instruction, authority, dependencies, expected artifact, acceptance check, budget, and failure policy, then route work units through the co-packaged coordinator runtime. - Independent review routing: Bind caller-verified independent reviewers to governance or review nodes and verify returned lineage before accepting independent evidence. - Vertical slice decomposition: Split product-feature implementation into tracer-bullet slices that each cut through all layers, with expand-contract sequencing reserved for wide refactors. - Use Case: A user asks to ship a feature touching schema, API, and UI. The Skill decomposes it into demoable vertical slices with explicit dependencies, dispatches each to a provider via one bounded routing request, and gates integration on verified artifacts. ## Quick Start Ask the agent to orchestrate this feature as a task graph with explicit dependencies and acceptance checks for each node.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I orchestrate a multi-step task as a dependency graph?▼

Define each node's instruction, authority, dependencies, expected artifact, acceptance check, budget, and stop condition, then send one bounded JSON routing request to the plugin's coordinator.py over stdin. Use depends_on only for real dependencies and one work unit per independently useful deliverable.

How do I dispatch an independent code review to a different provider?▼

Verify the reviewer's family differs from the primary and artifact-author families before dispatch, then bind that reviewer with the explicit_target field in the routing request. Afterward, verify the returned native lineage before accepting the review as independent evidence.

When should I use vertical slices versus expand-contract sequencing?▼

Prefer tracer-bullet vertical slices where each node cuts through all layers and is independently demoable. Reserve expand-contract sequencing for wide mechanical refactors where old and new forms must coexist to keep callers and CI working during staged migration.

Can a failed provider work unit be retried automatically?▼

No. A live request consumes at most one provider attempt per work unit, and a selected attempt is never replayed, retried, or failed over. Typed failures are preserved and the graph stops on exhausted budget, ambiguous authority, or operator gates.

What are the limitations of planning-only routing requests?▼

A planning request with dispatch_requested=false reports route eligibility only, not live provider availability or authentication. Provider state remains unknown unless native evidence establishes it, and no provider attempt is consumed.