minion-orchestrator

Coordinate durable shell and subagent job queues with progress tracking.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/ltdrew/Agent-brain-2 --skill minion-orchestrator-ltdrew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: minion-orchestrator
Source: https://github.com/ltdrew/Agent-brain-2/tree/main/skills/minion-orchestrator
Command: npx skills add https://github.com/ltdrew/Agent-brain-2 --skill minion-orchestrator-ltdrew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates durable, observable background work for two lanes: deterministic shell jobs and LLM subagent workflows, reducing manual coordination and state leakage across jobs.

Core Features & Use Cases

  • Unified routing and queueing for shell and subagent jobs with progress tracking and lifecycle controls.
  • Durable execution across restarts with pause/resume, cancel, and fan-out support.
  • Steering and observability via structured transcripts and in-flight messages.

Quick Start

Submit a deterministic shell job or a subagent run using the gbrain CLI to begin routing tasks.

Frequently Asked Questions about minion-orchestrator

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

FAQPage Schema
How do I orchestrate shell jobs and LLM subagent workflows with durable execution?

You can orchestrate shell jobs and LLM subagent workflows using a durable, observable queue that supports progress tracking, pause/resume, cancel, and fan-out across restarts.

What is the best way to track progress and manage the lifecycle of background shell and LLM tasks?

Track progress and manage task lifecycles using structured progress data and steering interfaces like MCP or CLI, which provide observability through structured transcripts and in-flight messages.

Can I pause and resume background tasks across system restarts?

Yes, background tasks are durable across restarts, allowing you to pause, resume, and cancel queued shell jobs or LLM subagent workflows without losing execution state.

Do I need a Postgres-backed queue to route and manage subagent tasks?

Yes, routing and lifecycle control for shell and subagent tasks requires a Postgres-backed queue to ensure durable execution and structured progress tracking.

How do I route deterministic shell jobs alongside LLM subagent tasks?

Route deterministic shell jobs and LLM subagent tasks through a unified queueing system that coordinates both lanes, reducing manual coordination and preventing state leakage across jobs.

How does fan-out work when orchestrating LLM subagent workflows?

Fan-out is supported as part of the lifecycle controls, allowing a single LLM subagent workflow to expand into multiple parallel tasks managed within the same durable queue.