ls-kilo-boss-orchestrator

Automate Kilo boss-worker orchestration with repo-local state and consensus validation.

3|2|Updated Dec 25, 2025

Search Tags:#automation #workflow #consensus #sessions #orchestrator #boss #kilo

Ready to run

npx skills add https://github.com/CruxExperts/localsetup --skill ls-kilo-boss-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ls-kilo-boss-orchestrator
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-kilo-boss-orchestrator
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-kilo-boss-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Orchestrates end-to-end Kilo boss-worker cycles with repo-local state, safety gates, and consensus validation to enable robust autonomous workflows.

Core Features & Use Cases

Streams boss-driven planning and worker delegation with explicit session/state tracking.
Enforces safety gates, audit trails, and consensus steps for high-stakes tasks.
Supports task queuing, leasing, and cross-team collaboration within a repository.

Quick Start

Initialize the orchestrator state with python3 scripts/boss_ctl.py init.

Frequently Asked Questions about ls-kilo-boss-orchestrator

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

FAQPage Schema

How do I automate multi-agent boss-worker delegation with consensus validation?▼

Multi-agent boss-worker delegation with consensus validation is automated by orchestrating task queuing, leasing, and safety gates. This ensures reliable, auditable execution by streaming planning workflows and enforcing safety gates for high-stakes tasks.

How do I initialize orchestrator state for autonomous code-workflow pipelines?▼

To initialize orchestrator state for autonomous code-workflow pipelines, run the command python3 scripts/boss_ctl.py init. This sets up the repo-local state tracking required for session management and watchdog recovery in boss-worker loops.

What is Kilo boss-worker orchestration and when do I need it?▼

Kilo boss-worker orchestration is an autonomous workflow pattern that manages planning, worker delegation, and verification within code pipelines. You need it for multi-agent planning, task queuing, and watchdog recovery to ensure reliable, auditable execution of high-stakes tasks.

Does autonomous workflow orchestration support repo-local state and session management?▼

Yes, autonomous workflow orchestration supports repo-local state and session management by implementing explicit state tracking for boss-worker cycles. It maintains queueing, leasing, and audit-trail records to ensure safe, cross-team collaboration within a repository.

How do I enforce safety gates and audit trails in multi-agent code pipelines?▼

Safety gates and audit trails in multi-agent code pipelines are enforced by applying consensus validation and explicit session tracking to the boss-worker loop. The orchestrator records audit-trail entries and applies watchdog recovery to ensure reliable autonomous execution.

Do I need YAML to run the Kilo orchestrator for task leasing and queueing?▼

Yes, you need YAML to run the Kilo orchestrator for task leasing and queueing, as it is a required dependency. The orchestrator relies on YAML to configure autonomous code-workflow pipelines, safety gates, and consensus validation state.