orchestrator

Coordinates agent state transitions across START, INIT, IMPLEMENT, TEST, and COMPLETE.

9|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ingpoc/SKILLS --skill orchestrator-ingpoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrator
Source: https://github.com/ingpoc/SKILLS/tree/main/orchestrator
Command: npx skills add https://github.com/ingpoc/SKILLS --skill orchestrator-ingpoc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, bc, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinates and manages agent state transitions across START, INIT, IMPLEMENT, TEST, and COMPLETE within a single-orchestrator architecture, ensuring safe, predictable progression and efficient context handling.

Core Features & Use Cases

  • State-machine driven workflow to drive transitions between INIT, IMPLEMENT, TEST, and COMPLETE.
  • Automatic loading of corresponding sub-skills for each state (initialization/, implementation/, testing/, context-graph/).
  • Context management with threshold-based compression to maintain performance during long-running sessions.
  • Session lifecycle support via a safety-aware session-entry protocol that checks project health, features, and readiness before work begins.
  • Clear auditing and history of transitions to support recovery and handoff.

Quick Start

Start a session with the session-entry protocol, then progress through INIT, IMPLEMENT, and TEST while monitoring context usage and letting the orchestrator load the correct sub-skills automatically.

Frequently Asked Questions about orchestrator

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

FAQPage Schema
How do I manage agent state transitions across implementation and testing phases?

Agent workflow orchestration automates the coordination of state transitions across START, INIT, IMPLEMENT, TEST, and COMPLETE phases. It applies progressive context compression when usage crosses defined thresholds, ensuring the correct context is loaded at session start and during transitions.

How do I prevent context window overflow during long-running agent sessions?

Prevent context overflow by applying progressive context compression triggered when usage crosses defined thresholds. This context management approach maintains performance during long-running sessions by ensuring only the correct, necessary context is loaded at session start or during state transitions.

Do I need to install jq and bc to run the orchestrator state-machine?

Yes, jq and bc are required dependencies for running the orchestrator state-machine. These tools support the scripts and session lifecycle handling needed to provide deterministic workflow orchestration and manage safe state transitions.

What is the best way to ensure safe progression when automating multi-step agent workflows?

The best way to ensure safe progression is to use a safety-aware session-entry protocol that checks project health, features, and readiness before work begins. This deterministic state-machine approach provides clear auditing and history of transitions to support recovery and handoff.

How does a state-machine handle session lifecycle recovery for agent workflows?

A state-machine handles session lifecycle recovery by providing clear auditing and history of transitions. This supports reliable multi-step orchestration and recovery by ensuring the correct context is loaded at session start or during state transitions.

Can I automatically load sub-skills when transitioning between implementation and testing states?

Yes, the state-machine driven workflow automatically loads corresponding sub-skills for each state, such as initialization, implementation, testing, and context-graph. This automatic loading enables reliable multi-step orchestration and ensures the correct context is applied during transitions.