orchestrator

To plan multi-skill execution, you invoke the orchestrator at the start of a multi-domain task. It analyzes dependencies, token costs, and execution order to generate a ranked invocation list and a structured task plan.

Dependency resolution and sequencing for multi-skill task plans determines the correct execution order across installed skills. It outputs a ranked invocation list that enforces proper sequencing for tasks spanning multiple domains.

Yes, you can optimize token usage when orchestrating multi-skill tasks through cost-aware planning. The orchestrator evaluates token costs across installed skills to make cost-aware decisions and generate an optimal execution sequence.

Yes, multi-skill orchestration works for building a product or auditing a codebase by planning an optimal execution order across installed skills. It applies phase-based orchestration to structure and monitor these broad, multi-domain tasks.

The best way to structure phase-based execution for a systems-wide plan is to use cost-aware planning and dependency ordering. This generates a structured task plan with an actionable task list and a ranked invocation order for monitoring.

You need phase-based orchestration for multi-domain tasks when they span multiple installed skills and require dependency ordering. It outputs a structured task plan and ranked invocation list to manage complex executions like building a product.