claude-import-orchestrator-worker

Delegates bounded tasks from an orchestrator to worker sessions via shared plan files.

Updated Aug 25, 2017
One-click install
npx skills add https://github.com/loki495/dotfiles --skill claude-import-orchestrator-worker-loki495
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-import-orchestrator-worker
Source: https://github.com/loki495/dotfiles/tree/main/ai/codex-skills/claude-import-orchestrator-worker
Command: npx skills add https://github.com/loki495/dotfiles --skill claude-import-orchestrator-worker-loki495

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Complex tasks often mix expensive high-level reasoning with cheap repetitive execution in a single session, wasting context and making progress hard to track. This Skill separates planning and review from implementation by coordinating an orchestrator with bounded worker sessions. ## Core Features & Use Cases - Orchestrator/Worker Split: An orchestrator plans, delegates, and reviews while each worker executes exactly one bounded task. - File-Based Communication: Coordination happens through .ai/PLAN.md, STATE.md, QUESTIONS.md, and RESULT.md so sessions stay decoupled and auditable. - Codex Session Launching: Workers run as separate Codex sessions via codex exec with a chosen model, with flags verified against codex exec --help. - Use Case: When refactoring a large module, the orchestrator writes a plan, spawns one worker per file or subtask, answers worker questions, and reviews each RESULT.md before marking the plan complete. ## Quick Start Read the orchestrator-worker protocol file and act as the orchestrator to plan this task and delegate bounded subtasks to worker sessions.

Frequently Asked Questions about claude-import-orchestrator-worker

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

FAQPage Schema
How do I split a complex coding task across multiple AI sessions?▼

Use an orchestrator-worker protocol where the orchestrator writes a plan in .ai/PLAN.md and delegates one bounded task per worker session. Workers report through RESULT.md and ask questions via QUESTIONS.md, keeping each session focused and cheap.

How do I launch a worker as a separate Codex session?▼

Launch a worker with codex exec -m <model> followed by the worker prompt, as described in the referenced protocol file's Launching Workers section. Verify the exact flags with codex exec --help first since they may change between versions.

What files does the orchestrator-worker protocol use for communication?▼

The protocol communicates through four files in the .ai directory: PLAN.md for the task plan, STATE.md for progress tracking, QUESTIONS.md for worker questions, and RESULT.md for each worker's outcome.

When should I use an orchestrator-worker pattern instead of a single session?▼

Use it for tasks complex enough to warrant explicit planning plus delegated implementation, where one session would mix costly reasoning with routine execution. For small single-step tasks, a single session is simpler and avoids coordination overhead.

Does this Skill contain the full orchestrator-worker instructions?▼

No, it is an import shim that directs you to read ~/dotfiles/ai/skills/orchestrator-worker/SKILL.md completely before acting. That referenced file contains the full protocol including the Launching Workers section.