How are code conflicts avoided?

The skill enforces a design-first workflow and utilizes dedicated git worktrees for each developer role to ensure isolated implementation environments.

Does this skill require any dependencies?

Yes, it requires the 'tmux-workflow' (twf) skill to be installed to manage the underlying terminal sessions and worker coordination.

How does the AI team communicate?

Roles communicate through a central Coordinator who routes internal queries, while a Liaison role handles all external communication with the human user.

Can I scale the team size?

Yes, any role can scale by spawning child workers (e.g., a Dev role hiring Dev-Interns) to handle specific sub-modules or tasks.

What is the AI Team Workflow skill?

It is a framework that allows Claude to spawn and coordinate multiple autonomous workers acting as specialized roles like Project Managers, Architects, and Developers.

AI Team Workflow

Name: AI Team Workflow
Author: kunhuang12345

bykunhuang12345

•

Collaboration Tools

Orchestrates multi-agent AI teams within tmux sessions to automate complex software development lifecycles from planning to deployment.

About

This skill enables Claude to function as a structured, collaborative AI team by leveraging a role-based multi-agent architecture built on tmux-workflow. It assigns specific responsibilities to individual Codex workers—including PM, Architect, Developer, QA, and Ops—managed through a centralized responsibility registry. By utilizing a Coordinator for internal routing and a Liaison for user interaction, it ensures complex tasks are decomposed and executed efficiently. The workflow includes standardized design consolidation, automated status reporting, and isolated development environments via git worktrees, making it perfect for scaling autonomous software engineering tasks.

Key Features

Internal routing via a Coordinator role to minimize user interruptions
Role-based worker orchestration (PM, Architect, Dev, QA, Ops)
Automated reporting hierarchy for bottom-up status updates
1 GitHub stars
Centralized shared responsibility registry for transparent task allocation
Isolated git worktree management for parallel feature development

Use Cases

Managing full-stack software projects from requirements gathering to production deployment
Orchestrating complex architectural refactors requiring coordinated module updates
Automating continuous integration and environment setup alongside core development

About

Key Features

Internal routing via a Coordinator role to minimize user interruptions
Role-based worker orchestration (PM, Architect, Dev, QA, Ops)
Automated reporting hierarchy for bottom-up status updates
1 GitHub stars
Centralized shared responsibility registry for transparent task allocation
Isolated git worktree management for parallel feature development

Use Cases

Managing full-stack software projects from requirements gathering to production deployment
Orchestrating complex architectural refactors requiring coordinated module updates
Automating continuous integration and environment setup alongside core development