orchestrate

Orchestrates multi-phase agentic engineering lifecycles with task contracts, provider routing, and verification gates.

Updated Jul 19, 2026
One-click install
npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill orchestrate-dagimalemayehuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/DagimAlemayehuu/AgenticEngineering/tree/main/agentic-engineering/core
Command: npx skills add https://github.com/DagimAlemayehuu/AgenticEngineering --skill orchestrate-dagimalemayehuu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Coordinating AI agents, external providers like Google Jules, NotebookLM, and Stitch, and human approvals across a full software lifecycle is error-prone without explicit contracts, state tracking, and independent verification. This Skill acts as a control plane that routes work through governed phases, enforces machine-readable task contracts, and maintains resumable audit trails. ## Core Features & Use Cases - Phase Routing and Lifecycle Management: Routes natural-language requests to the correct lifecycle phase (setup, discovery, specification, implementation, verification, release, operations, retirement) using a deterministic routing script and durable project state. - Execution Contracts and Approval Gates: Validates JSON execution plans with task DAGs, file ownership, risk levels, and HMAC-signed human approval tokens before any dispatch occurs. - Provider-Aware Delivery: Dispatches bounded tasks to Jules, NotebookLM, Stitch, or local agents through registered transport adapters, with independent review records and SHA-256-bound evidence required before tasks are marked verified. - Use Case: A team adopting an existing repository runs the control plane to audit alignment, register provider capabilities, create an approved execution plan, dispatch bounded implementation tasks to Jules, and require fresh-context verification before integration and release. ## Quick Start Ask the agent to use the agentic-engineering skill to audit and adopt this repository, then follow the routed phase guidance it returns.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I orchestrate AI agents across a full software development lifecycle?▼

Run the control_plane.py gateway with commands like start, status, route, and execute to move through governed phases from setup to retirement. Each phase requires an approved execution contract, durable artifacts, and recorded state transitions before the next phase begins.

How do I delegate coding tasks to Google Jules safely?▼

Create a schema-2 execution plan with bounded tasks, file ownership, and verification commands, then record human approval with a host-signed token. Dispatch uses orchestrate.py dispatch, which requires a registered provider transport and never treats provider completion as verification.

Can this workflow work without NotebookLM or Stitch configured?▼

Yes, the capability registry in .agentic/capabilities.json records which providers are available, and routing policy falls back to local agents when a provider is unavailable. Missing or malformed transport adapters fail closed rather than simulating external work.

What happens if a task plan has dependency cycles or overlapping file ownership?▼

The contracts validation rejects plans with dependency cycles, duplicate task IDs, unknown dependencies, or overlapping fileOwnership between parallel tasks. High- and critical-risk tasks are also restricted to the local-agent provider.

Why does task verification require an independent reviewer?▼

Review records must show a verifier with a different run ID and identity than the implementer, plus passing exit codes for every approved verification command. Schema-2 tasks additionally require stdout digests and a SHA-256 hash of the reviewed artifact to bind evidence to the approved scope.