meow:team-config

Create git worktrees, ownership maps, and task queues for parallel agent teams.

14|2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-team-config
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meow:team-config
Source: https://github.com/ngocsangyem/MeowKit/tree/main/.claude/skills/meow%3Ateam-config
Command: npx skills add https://github.com/ngocsangyem/MeowKit --skill meow-team-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Set up parallel agent team for COMPLEX tasks. Creates worktree structure, generates ownership map, and initializes task queue. Use when orchestrator decomposes a task into parallel subtasks, or when asked to "set up team", "parallel setup", or "configure worktrees".

Core Features & Use Cases

  • Ownership map generation: analyzes plan and assigns work ownership to agents to enable safe parallel execution.
  • Worktree orchestration: creates per-agent git worktrees so tasks can run concurrently with isolated branches.
  • Task queue initialization: builds the session-state/task-queue.json to manage task claiming and progress tracking.
  • Validation: checks for ownership overlap and prevents conflicts before parallel execution starts.

Quick Start

Run meow:team-config with a task description and the number of agents to initialize the parallel team.

Frequently Asked Questions about meow:team-config

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

FAQPage Schema
How do I set up parallel agent teams for complex task execution?

To set up parallel agent teams, an orchestrator decomposes a complex task into independent subtasks, provisions isolated git worktrees, and generates an ownership map for each agent. This enables safe concurrent execution without branch conflicts.

What is git worktree orchestration and when do I need it for parallel execution?

Git worktree orchestration creates per-agent worktrees so tasks can run concurrently on isolated branches. You need this when decomposing a complex task into independent subtasks that require safe parallel execution without overlapping file ownership.

How do I prevent ownership overlap when running parallel agents on the same repository?

You prevent ownership overlap by initializing an ownership map that assigns specific work ownership to agents before execution starts. The system validates this map and checks for conflicts to ensure safe parallel execution across isolated worktrees.

Can I manage task claiming and progress tracking for parallel subtasks in a queue?

Yes, you can manage task claiming and progress tracking by initializing a session-state task queue. The system builds this queue to orchestrate how parallel agents claim independent subtasks and track their completion progress.

Do I need an existing plan before configuring worktrees for a parallel setup?

Yes, you need an existing plan. The system analyzes your plan to generate the ownership map and assign work ownership to agents, ensuring the decomposed independent subtasks are properly allocated before creating isolated git worktrees.