ct-orchestrator

Coordinate multi-agent CLEO workflows with manifest-driven handoffs and protocol injection.

160|20|Updated Dec 6, 2025

Search Tags:#subagents #manifest #orchestrator #HITL #workflow-management #dependency-waves #protocol-injection

Ready to run

npx skills add https://github.com/kryptobaseddev/cleo --skill ct-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ct-orchestrator
Source: https://github.com/kryptobaseddev/cleo/tree/main/skills/ct-orchestrator
Command: npx skills add https://github.com/kryptobaseddev/cleo --skill ct-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The ct-orchestrator skill provides a HITL-aware coordination layer that centralizes orchestration, enforces strict delegation rules, and protects the main context window during multi-agent CLEO workflows.

Core Features & Use Cases

On-demand subagent spawning with protocol injection to ensure isolation and compliance.
Manifest-driven handoffs that carry key findings and allow agents to read only summaries.
Dependency-wave planning and context budget enforcement to maintain performance and traceability.
Parallel task coordination and cross-epic orchestration while maintaining audit trails.

Quick Start

Start an orchestrator session for epic T1575, then spawn the next subagent (e.g., T1586) to observe protocol injection and manifest update. Review the manifest to confirm a key_findings entry and link it to the parent task.

Frequently Asked Questions about ct-orchestrator

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

FAQPage Schema

How do I coordinate multi-agent workflows with human in the loop decision points?▼

Multi-agent workflow coordination with HITL control is managed by enforcing strict delegation rules and manifest-driven handoffs. This centralizes orchestration while applying dependency-wave planning and context budget enforcement to maintain performance and traceability.

What is manifest-driven handoff in subagent orchestration?▼

Manifest-driven handoff in subagent orchestration carries key findings between agents, allowing downstream agents to read only summaries instead of full context. This mechanism protects the main context window and enforces strict delegation during multi-agent task execution.

How do I spawn subagents with protocol injection for workflow isolation?▼

Subagent spawning with protocol injection is handled through on-demand loading of references and assets. This ensures isolation and compliance by automatically injecting required protocols into the subagent context during the orchestration session.

Can I use dependency-wave planning for parallel task coordination across epics?▼

Dependency-wave planning supports parallel task coordination and cross-epic orchestration while maintaining audit trails. It enforces context budget adherence and validates subagent spawning within an epic to ensure traceability across complex workflows.

Does context budget enforcement work with cross-epic orchestration?▼

Context budget enforcement applies to cross-epic orchestration by validating subagent spawning and maintaining dependency-wave plans. It ensures agents read only manifest summaries, protecting the main context window while preserving audit trails across parallel tasks.

What's the best way to verify compliance checks in multi-agent CLEO workflows?▼

Compliance checks in multi-agent CLEO workflows are verified through manifest verification and protocol injection during on-demand loading. The orchestrator validates handoffs, enforces delegation rules, and confirms key_findings entries are linked to parent tasks.