task-orchestrator

What This Skill Does

The Task Orchestrator is a sophisticated autonomous agent skill designed for OpenClaw to manage complex, multi-issue development projects. It functions as a meta-controller that interprets, plans, and executes code-based tasks by treating large-scale development as a graph of dependencies. By leveraging git worktrees for environmental isolation and tmux for parallel process control, it allows multiple AI agent instances to work on different parts of a codebase simultaneously without interference. It continuously monitors the heartbeat of each task, ensuring that if one sub-agent hits a roadblock, the entire orchestration flow is managed effectively.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/henrino3/ec-task-orchestrator Ensure you have git, tmux, and the GitHub CLI (gh) configured in your system path, as these are critical dependencies for the orchestrator to manage worktrees and process sessions.

Use Cases

• Large Refactors: Coordinate simultaneous updates across disparate modules where dependency injection needs to be tracked.
• Bulk Bug Squashing: Process a list of open issues from a GitHub repository by automatically grouping them based on file overlap and executing fixes in parallel.
• Multi-Branch Prototyping: Experiment with several feature branches simultaneously, each in its own isolated worktree, while maintaining a master manifest of changes.

Example Prompts

1. "Orchestrate the fix for issues 45, 46, and 47 from our repo. Run the dependency analyzer first to detect any file overlaps and report back before creating worktrees."
2. "Monitor the current active tmux sessions managed by the task-orchestrator. Which tasks in Phase 2 are currently stalled?"
3. "Restart the heartbeat for the session associated with issue 102. The previous agent died mid-execution; please resume from the last saved state in the manifest."

Tips & Limitations

• Safety First: Always review the generated manifest.json before triggering mass execution. The orchestrator is powerful, and rapid file writes can conflict if file dependencies are incorrectly mapped.
• Resource Usage: Running too many parallel tmux sessions can exhaust system memory. Start with small batches of 3-5 tasks.
• Conflict Resolution: If two tasks modify the same file, the orchestrator will force sequential execution. Use the manifest to explicitly set dependencies if you anticipate logic conflicts.