multitask-coordinator

Coordinates hierarchical subagent scheduling with dependency-aware task graphs and ownership boundaries.

3|Updated Aug 8, 2026
One-click install
npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill multitask-coordinator-jose-polanco-oxte
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multitask-coordinator
Source: https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer/tree/main/.agents/skills/multitask-coordinator
Command: npx skills add https://github.com/Jose-Polanco-Oxte/Echos-Live-Music-Visualizer --skill multitask-coordinator-jose-polanco-oxte

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Complex multi-step work often fails when parallel agents collide on shared files, duplicate effort, consume stale decisions, or get cancelled mid-flight. This Skill provides an explicit coordination model that decomposes large tasks into a dependency-aware task and decision graph, assigns one owner per decision domain and write boundary, and integrates evidence-backed results safely. ## Core Features & Use Cases - Hierarchical Scheduling: Build a task and decision graph, appoint subplanners for exclusive decision domains, and dispatch ready work up to safe capacity. - Ownership & Conflict Routing: Enforce one writer per shared surface, route semantic conflicts to decision owners, textual conflicts to merge arbiters, and acceptance conflicts to independent verifiers. - Ephemeral Shared Memory: Materialize an owned, single-writer-per-file run root for cross-agent state, with strict placement, lifecycle, and cleanup rules. - Scheduler Auditing: Diagnose hidden serialization, decision split-brain, stale contracts, and verification gaps using the bundled audit reference. - Use Case: When migrating a large repository across multiple modules, invoke this Skill to freeze shared contracts, dispatch isolated workers per module, preserve healthy long-running workers, and integrate only evidence-backed results. ## Quick Start Ask the assistant to use $multitask-coordinator to plan and execute your large multi-part task with parallel subagents and verified integration.

Frequently Asked Questions about multitask-coordinator

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

FAQPage Schema
How do I coordinate multiple AI subagents on a large coding task?

Invoke $multitask-coordinator explicitly to build a task and decision graph, assign one owner per decision domain and write boundary, then dispatch ready work up to safe capacity. The root parent integrates evidence-backed results and retains final verification responsibility.

When should I use hierarchical subagent scheduling?

Use it for non-trivial multi-step work such as large migrations, multi-module repositories, or parallel workstreams with dependencies. Skip it for trivial single-step tasks where dispatch and synthesis overhead exceeds the benefit.

How are conflicts between parallel workers resolved?

Semantic conflicts route to the decision owner or nearest common ancestor planner, textual conflicts between compatible decisions go to a neutral merge arbiter, and acceptance conflicts go to an independent reviewer or verifier using stated acceptance criteria.

Can subagents share state across context boundaries?

Yes, through ephemeral shared memory: one owned run root with single-writer files for decisions, subtrees, and handoffs. Workers receive only exact relevant paths, and the root parent owns cleanup after all dependents are reconciled.

What happens to healthy long-running workers during coordination?

Healthy workers are preserved: they are not cancelled, restarted, reassigned, or scope-changed. Intervention occurs only for reported failures, blockers, timeouts, safety risks, or superseding instructions, using the least disruptive response.

When should I not use multi-agent orchestration?

Avoid it for trivial fixes, subtrees dominated by one shared file, unresolved root decisions, or when parent integration capacity is saturated. Handle such work directly instead of adding a planner layer.