Receber por email
← Voltar para o catálogo

mk:team-config

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

15estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add ngocsangyem/MeowKit

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/mk-team-config/svg)](https://www.skillteca.com.br/skills/mk-team-config)
#ai

Skills relacionadas

Ver todas de Automação →

Alerta por categoria

Receba novas skills de Automação toda segunda

1 email curto, só com as skills novas de Automação. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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

  1. Analyzes the task — identifies independent subtasks from the plan
  2. Generates ownership map — assigns file ownership globs per subtask
  3. Creates worktrees — one git worktree per parallel agent
  4. Initializes task queue — session-state/task-queue.json with claiming protocol
  5. 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

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:

  1. Merge all worktree branches to feature branch
  2. Remove worktrees via mk:worktree cleanup
  3. Archive session-state/task-queue.json
Compartilhar X LinkedIn