odylith-subagent-orchestrator

Plan Odylith subagent delegation with ownership, bounded fanout, and merge-safe orchestration.

34|3|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/odylith/odylith --skill odylith-subagent-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odylith-subagent-orchestrator
Source: https://github.com/odylith/odylith/tree/main/.claude/skills/odylith-subagent-orchestrator
Command: npx skills add https://github.com/odylith/odylith --skill odylith-subagent-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans and coordinates Odylith subagent delegation with clear ownership, bounded fanout, and merge-safe orchestration to reduce conflicts and miscoordination in multi-agent workflows.

Core Features & Use Cases

  • Delegation ownership planning: assigns responsibility and accountability to subagents.
  • Bounded fanout coordination: ensures scalable, safe distribution of tasks across multiple agents.
  • Merge-safe orchestration: defines safe merge points and conflict resolution strategies for coordination.
  • Use Case: coordinate two subagents to perform a split task with a clear ownership boundary and auditable merges.

Quick Start

Provide a plan outline that assigns subagent ownership, enforces bounded fanout, and defines merge-safe orchestration rules for a given scenario.

Frequently Asked Questions about odylith-subagent-orchestrator

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

FAQPage Schema
What is bounded fanout in multi-agent orchestration?

Bounded fanout limits the distribution of tasks across multiple subagents to a defined scope, ensuring scalable and safe coordination without overwhelming the system. It prevents uncontrolled task expansion during multi-agent workflows.

How do I plan subagent ownership for split tasks?

Plan subagent ownership by assigning clear responsibility and accountability boundaries to each agent before execution. This ensures tasks operate within defined limits and produce auditable merges.

Why do my subagent workflows have merge conflicts?

Merge conflicts occur when multiple subagents lack defined safe merge points and clear ownership boundaries. Merge-safe orchestration defines conflict resolution strategies to coordinate agents and prevent miscoordination.

What is the best way to coordinate multiple subagents safely?

The best way to coordinate subagents safely is defining merge-safe orchestration rules with bounded fanout. This approach assigns ownership boundaries and establishes safe merge points for auditable task delegation.

When do I need merge-safe orchestration for subagent delegation?

You need merge-safe orchestration when multiple subagents must operate on split tasks with clear ownership boundaries. It is required whenever coordination scenarios risk conflicts or miscoordination without auditable merge points.

Does bounded fanout work for scaling multi-agent coordination?

Yes, bounded fanout works for scaling multi-agent coordination by safely distributing tasks across agents within defined limits. It ensures scalable delegation while maintaining clear ownership and safe merges.