doey-add-team

Spawn a tmux team window from a .team.md definition file.

6|2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FRIKKern/doey --skill doey-add-team
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doey-add-team
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-add-team
Command: npx skills add https://github.com/FRIKKern/doey --skill doey-add-team

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawns a new, fully configured Doey team window from a .team.md definition, eliminating manual setup of panes, roles, and workflows.

Core Features & Use Cases

  • Load a .team.md definition from project locations or common Doey directories and parse pane and workflow data.
  • Create a tmux window with panes configured by the team definition and assign roles (manager, worker) per pane.
  • Launch Claude instances for each pane with configured names and models, coordinating startup order.
  • Persist team metadata and session state to enable quick reuse and continuity across sessions.

Quick Start

Place a valid .team.md in your project or common Doey locations and run /doey-add-team <name> to spawn a new team window.

Frequently Asked Questions about doey-add-team

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

FAQPage Schema
How do I spawn multiple Claude instances in tmux panes from a definition file?

You can spawn a fully configured team by placing a valid .team.md definition in your project and running the add-team command. It parses pane and workflow data to automatically create tmux windows, assign roles, and launch Claude instances for each configured pane.

What is a .team.md definition file used for in automation workflows?

A .team.md file defines pane configurations, roles like manager or worker, and workflows for your team. The Skill parses this metadata to coordinate session and window management via tmux, eliminating manual pane setup and enforcing a consistent team structure.

How do I automate tmux window and pane creation for a Claude team?

Automate tmux window creation by loading a .team.md definition from common project locations. The Skill reads the pane configurations and uses the Doey CLI to create the tmux environment, assign roles, and launch Claude instances in the correct startup order.

Do I need the Doey CLI to manage tmux sessions and team metadata?

Yes, the Doey CLI is required to coordinate session and window management. The Skill relies on it to parse the .team.md definition, persist team metadata and session state, and launch Claude instances within the created tmux panes for quick reuse.

Can I persist team metadata and session state across tmux sessions?

Yes, the Skill persists team metadata and session state after spawning from the .team.md definition. This enables quick reuse and continuity across sessions, allowing you to resume coordinated Claude instances and tmux pane configurations without manual reconfiguration.

What are the limitations when defining panes and workflows in a .team.md file?

The Skill enforces a defined .team.md format for panes and workflows, meaning definitions that deviate from this structure will not parse correctly. You must ensure your team definition follows the required format for pane roles and workflow metadata to spawn successfully.