Team config

Skill ngocsangyem/MeowKit/.claude/skills/team-config

Production ready. AI Agent Workflow System for Claude Code

Install

npx -y skills add ngocsangyem/MeowKit --skill team-config

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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".

SKILL.md

3.3 KB, as published. Nobody here has run it

Team Configuration

Sets up the infrastructure for parallel agent execution. Called by orchestrator when a COMPLEX task is decomposed into independent subtasks.

What It Does

Analyzes the task — identifies independent subtasks from the plan
Generates ownership map — assigns file ownership globs per subtask
Creates worktrees — one git worktree per parallel agent
Initializes task queue — session-state/task-queue.json with claiming protocol
Validates no overlap — checks ownership globs for conflicts before starting

Setup Flow

Plan approved (Gate 1)
    ↓
Orchestrator identifies parallel opportunity
    ↓
mk:team-config
    ├── 1. Parse plan for independent subtasks
    ├── 2. Generate ownership map (which agent owns which files)
    ├── 3. Validate zero overlap between ownerships
    ├── 4. Create git worktrees via mk:worktree
    └── 5. Create task-queue.json via mk:task-queue
    ↓
Parallel agents start claiming tasks

Team Coordination Rules

When team mode activates, Read references/team-coordination.md — the team-only coordination rules (file ownership per task, no force-push, worktree-branch commits, actionable completion messages, lead docs-impact ownership). These were moved out of always-loaded parallel-execution-rules.md so they load only on team activation.

Ownership Map Template

See templates/ownership-map-template.md for the format agents use to declare file ownership.

Constraints

Max 3 parallel agents (from parallel-execution-rules.md)
Only COMPLEX tasks qualify (orchestrator enforces this)
Gates (1 and 2) are never parallelized
All worktrees branch from current feature branch HEAD

Gotchas

Overlapping ownership kills parallelism — if two subtasks need the same file, they can't be parallel. Restructure the decomposition or handle the shared file in a sequential pre-step
Worktree naming with special characters — skill names with : (e.g., mk:review) need quoting in shell paths
Stale worktrees from crashed sessions — run git worktree list to check for orphaned worktrees before creating new ones
Integration test is mandatory — after merging all worktrees, the full test suite MUST pass. Don't skip this

Teardown

After all parallel agents complete and integration test passes:

Merge all worktree branches to feature branch
Remove worktrees via mk:worktree cleanup
Archive session-state/task-queue.json