orchestrate

Route work across the Hali skill set and update an execution ledger.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/irvinesunday/Hali --skill orchestrate-irvinesunday
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/irvinesunday/Hali/tree/main/.claude/skills/orchestrate
Command: npx skills add https://github.com/irvinesunday/Hali --skill orchestrate-irvinesunday

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Routes work across the Hali skill set by establishing current engineering state, identifying the next skill, and maintaining a clean execution ledger to stop on doctrine ambiguity or blockers.

Core Features & Use Cases

  • Coordinates cross-skill workflow and governance to prevent monolithic scope creep.
  • Establishes state, determines next skill to invoke, and updates a shared ledger for traceability.
  • Use cases include starting new workstreams, sequencing multiple issues, resuming paused work, and coordinating phases (audit → triage → execute → validate → pr-hygiene).

Quick Start

Provide a clear workstream goal, then let orchestrate map current state, route to the next skill, and update the execution ledger.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I coordinate cross-skill workflow routing to prevent scope creep?

Cross-skill workflow routing coordinates multiple engineering phases by establishing current state, determining the next skill invocation, and maintaining a shared execution ledger to prevent monolithic scope creep and ensure orderly progression.

What is an execution ledger and when do I need it for workstream sequencing?

An execution ledger maintains traceability and auditing during workstream sequencing. You need it when starting new workstreams, sequencing multiple issues, resuming paused work, or coordinating phases like audit, triage, execute, validate, and pr-hygiene.

How do I resume paused work and detect blockers across multiple engineering phases?

To resume paused work, the orchestration process maps the current engineering state from the execution ledger, detects doctrine ambiguity or blockers, and outputs the next skill invocation to safely continue the workstream without specialist intervention.

Can I use workflow guardrails to stop execution automatically on doctrine ambiguity?

Yes, workflow guardrails automatically stop execution on doctrine ambiguity or blockers. The system establishes state, routes work across the skill set, and updates the ledger, providing governance without requiring deep specialist work to proceed.

Does this workflow orchestration require any specific dependencies or component installations?

No, this workflow orchestration requires no specific dependencies or component installations. It operates independently to establish state, route work, detect blockers, and update the execution ledger for governance and traceability.