skills.rest
tanaka-yui
tanaka-yuiCOMMUNITY
Explore all skills by this author →
GitHub

cmux-agent-role

Coordinate cmux-team sub-agents with shared protocols and output paths.

4|Updated Mar 30, 2026
Search Tags:#conductor#task-creation#sub-agent#coordinate#cmux-team#output-protocol
One-click install
npx skills add https://github.com/tanaka-yui/yui-cc-plugins --skill cmux-agent-role
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmux-agent-role
Source: https://github.com/tanaka-yui/yui-cc-plugins/tree/main/apps/cmux-team/skills/cmux-agent-role
Command: npx skills add https://github.com/tanaka-yui/yui-cc-plugins --skill cmux-agent-role

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

cmux-team sub-agents often operate in parallel without a clear coordination protocol, leading to misaligned outputs and stalled progress. This Skill defines a standardized activation and communication flow for sub-agents spawned by a Conductor, ensuring consistent task handling and reporting.

Core Features & Use Cases

  • Output protocol: all artifacts must be written to the designated .team/output/<role-id>.md path to enable centralized review.
  • Task orchestration: can trigger and record tasks through the cmux-team task system to surface blockers and decisions.
  • Inter-agent coordination: enforces a shared, traceable communication channel via the .team directory and Conductor-driven prompts.

Quick Start

Launch the sub-agent session managed by the Conductor and begin by following the [CMUX-TEAM-AGENT] marker in the initial prompt.

Frequently Asked Questions about cmux-agent-role

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

FAQPage Schema
How do I coordinate sub-agents spawned by a conductor to prevent misaligned outputs?▼

Sub-agent coordination is managed by enforcing a standardized communication flow where all artifacts are written to a shared .team/output directory, ensuring synchronized task execution and centralized review.

What is the output protocol for cmux-team sub-agents operating in parallel?▼

The output protocol requires all sub-agent artifacts to be written to the designated .team/output/<role-id>.md path, enabling centralized review and traceable communication across the conductor workflow.

How do I start a cmux-team sub-agent session managed by a Conductor?▼

To start a sub-agent session, launch the process managed by the Conductor and begin by following the CMUX-TEAM-AGENT marker provided in the initial prompt to activate the coordination protocol.

Can I trigger task creation through the cmux-team system to surface blockers?▼

Yes, sub-agents can trigger and record tasks through the cmux-team task system, which surfaces blockers and decisions while enforcing shared work boundaries within a git worktree.

Why do parallel sub-agents stall without a clear coordination protocol?▼

Parallel sub-agents stall without a coordination protocol because they lack a traceable communication channel and explicit work boundaries, leading to misaligned outputs and unresolved task dependencies.

Does sub-agent task orchestration work within a git worktree boundary?▼

Yes, the task orchestration protocol enforces work boundaries within a git worktree, ensuring all inter-agent communication and generated outputs remain isolated and traceable.

Related Skills

Explore More Software Engineering Skills→
AshleyHollisAshleyHollis

agent-collaboration

Standardize team agent collaboration with worktree awareness and decision recording.

Community
Intermediate
catlog22catlog22
511

team-coordinate

Orchestrate multi-agent teams with DAG-based task chains and runtime role-specs.

Community
Advanced
LuminairPrimeLuminairPrime

synapse-a2a

Send and receive prioritized messages between Synapse A2A agents.

Community
Advanced
artsmcartsmc

start-phase-execute-team

Coordinate parallel task execution for multi-agent teams across start-phase workflows.

Community
Advanced