ai-team-workflow

You can coordinate multiple AI agents by assigning specific roles like PM, Architect, Dev, and QA within a tmux-based workflow. This skill handles role spawning, task routing, and artifact consolidation across subteams using a shared registry to keep work flowing.

Tmux-based multi-agent workflow orchestration is a coordination method that uses tmux sessions to manage distinct AI roles such as Ops, Coordinator, and Liaison. It provides routing logic and escalation paths to ensure cross-role communication and task delivery remain cohesive.

Yes, you can use tmux to route tasks between AI roles. The Coordinator role routes internal questions while the Liaison handles user-facing queries, ensuring proper escalation paths and task assignment across PM, Architect, Product, Dev, QA, and Ops subteams.

To initialize a multi-agent AI team workflow, run the provided script to set up the initial registry and spawn a PM-Arch-Dev-QA trio. This creates a shared registry at the skill root directory to govern routing and ownership configuration.

Yes, a shared registry is required for AI team coordination. The skill uses a centralized registry file to govern routing logic, track ownership, and consolidate design docs and task artifacts across all spawned subteams and active roles.

The primary limitation is that this tmux workflow requires the tmux-workflow skill to be installed alongside it. Without this dependency, the system cannot spawn tmux sessions or execute cross-role lifecycle operations like route and report.