O que é team-lifecycle-v4?

Perfeito para Agentes de IA que necessitam de orquestração de fluxo de trabalho multi-agente simplificada e integração de endpoint MCP para gerenciamento do ciclo de vida de desenvolvimento de software. O Team Lifecycle v4 é uma ferramenta de orquestração de fluxo de trabalho que automatiza o processo de desenvolvimento de software.

Como instalar team-lifecycle-v4?

Execute o comando: npx killer-skills add catlog22/maestro-flow/team-lifecycle-v4. Ele funciona com Cursor, Windsurf, VS Code, Claude Code e mais de 19 outros IDEs.

Quais são os casos de uso de team-lifecycle-v4?

Os principais casos de uso incluem: Automatizar fluxos de trabalho de desenvolvimento de software desde a especificação até a revisão, Integrar painéis de vários agentes para colaboração e visibilidade aprimoradas, Simplificar processos de teste e revisão usando integração de endpoint MCP.

Quais IDEs são compatíveis com team-lifecycle-v4?

Esta skill é compatível com Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use a CLI do Killer-Skills para uma instalação unificada.

team-lifecycle-v4 tem limitações?

Exige gerenciamento de fluxo de trabalho baseado em CLI. Limitado ao gerenciamento do ciclo de vida de desenvolvimento de software. Dependente de arquitetura baseada em Router.

team-lifecycle-v4

Aprenda a configurar o Team Lifecycle v4, uma ferramenta de orquestração de fluxo de trabalho com suporte a MCP e painel de dashboard multiagente.

SKILL.md

Readonly

Upstream Repository Material

The section below is adapted from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

Team Lifecycle v4

Name: team-lifecycle-v4
Availability: InStock
Author: catlog22

Orchestrate multi-agent software development: specification -> planning -> implementation -> testing -> review.

Architecture

Skill(skill="team-lifecycle-v4", args="task description")
                    |
         SKILL.md (this file) = Router
                    |
     +--------------+--------------+
     |                             |
  no --role flag              --role <name>
     |                             |
  Coordinator                  Worker
  roles/coordinator/role.md    roles/<name>/role.md
     |
     +-- analyze -> dispatch -> spawn -> STOP
                                 |
                    +--------+---+--------+
                    v        v            v
             [team-worker]  ...    [team-supervisor]
              per-task               resident agent
              lifecycle              message-driven
                                     (woken via SendMessage)

Role Registry

Role	Path	Prefix	Inner Loop
coordinator	roles/coordinator/role.md	--	--
analyst	roles/analyst/role.md	RESEARCH-*	false
writer	roles/writer/role.md	DRAFT-*	true
planner	roles/planner/role.md	PLAN-*	true
executor	roles/executor/role.md	IMPL-*	true
tester	roles/tester/role.md	TEST-*	false
reviewer	roles/reviewer/role.md	REVIEW-, QUALITY-, IMPROVE-*	false
supervisor	roles/supervisor/role.md	CHECKPOINT-*	false

Role Router

Parse $ARGUMENTS:

Has --role <name> -> Read roles/<name>/role.md, execute Phase 2-4
No --role -> Read roles/coordinator/role.md, execute entry router

Shared Constants

Session prefix: TLV4
Session path: .workflow/.team/TLV4-<slug>-<date>/
CLI tools: ccw cli --mode analysis (read-only), ccw cli --mode write (modifications)
Message bus: mcp__ccw-tools__team_msg(session_id=<session-id>, ...)

Worker Spawn Template

Coordinator spawns workers using this template:

Agent({
  subagent_type: "team-worker",
  description: "Spawn <role> worker",
  team_name: <team-name>,
  name: "<role>",
  run_in_background: true,
  prompt: `## Role Assignment
role: <role>
role_spec: <project>/.claude/skills/team-lifecycle-v4/roles/<role>/role.md
session: <session-folder>
session_id: <session-id>
team_name: <team-name>
requirement: <task-description>
inner_loop: <true|false>

Read role_spec file to load Phase 2-4 domain instructions.
Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
})

Supervisor Spawn Template

Supervisor is a resident agent (independent from team-worker). Spawned once during session init, woken via SendMessage for each CHECKPOINT task.

Spawn (Phase 2 -- once per session)

Agent({
  subagent_type: "team-supervisor",
  description: "Spawn resident supervisor",
  team_name: <team-name>,
  name: "supervisor",
  run_in_background: true,
  prompt: `## Role Assignment
role: supervisor
role_spec: <project>/.claude/skills/team-lifecycle-v4/roles/supervisor/role.md
session: <session-folder>
session_id: <session-id>
team_name: <team-name>
requirement: <task-description>

Read role_spec file to load checkpoint definitions.
Init: load baseline context, report ready, go idle.
Wake cycle: coordinator sends checkpoint requests via SendMessage.`
})

Wake (handleSpawnNext -- per CHECKPOINT task)

SendMessage({
  type: "message",
  recipient: "supervisor",
  content: `## Checkpoint Request
task_id: <CHECKPOINT-NNN>
scope: [<upstream-task-ids>]
pipeline_progress: <done>/<total> tasks completed`,
  summary: "Checkpoint request: <CHECKPOINT-NNN>"
})

Shutdown (handleComplete)

SendMessage({
  type: "shutdown_request",
  recipient: "supervisor",
  content: "Pipeline complete, shutting down supervisor"
})

User Commands

Command	Action
`check` / `status`	View execution status graph
`resume` / `continue`	Advance to next step
`revise <TASK-ID> [feedback]`	Revise specific task
`feedback <text>`	Inject feedback for revision
`recheck`	Re-run quality check
`improve [dimension]`	Auto-improve weakest dimension

Completion Action

When pipeline completes, coordinator presents:

AskUserQuestion({
  questions: [{
    question: "Pipeline complete. What would you like to do?",
    header: "Completion",
    multiSelect: false,
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Export Results", description: "Export deliverables to target directory" }
    ]
  }]
})

Specs Reference

specs/pipelines.md -- Pipeline definitions and task registry
specs/quality-gates.md -- Quality gate criteria and scoring
specs/knowledge-transfer.md -- Artifact and state transfer protocols

Session Directory

.workflow/.team/TLV4-<slug>-<date>/
+-- team-session.json           # Session state + role registry
+-- spec/                       # Spec phase outputs
+-- plan/                       # Implementation plan + TASK-*.json
+-- artifacts/                  # All deliverables
+-- wisdom/                     # Cross-task knowledge
+-- explorations/               # Shared explore cache
+-- discussions/                # Discuss round records
+-- .msg/                       # Team message bus

Error Handling

Scenario	Resolution
Unknown command	Error with available command list
Role not found	Error with role registry
CLI tool fails	Worker fallback to direct implementation
Fast-advance conflict	Coordinator reconciles on next callback
Supervisor crash	Respawn with `recovery: true`, auto-rebuilds from existing reports
Supervisor not ready for CHECKPOINT	Spawn/respawn supervisor, wait for ready, then wake
Completion action fails	Default to Keep Active

team-lifecycle-v4 — orquestração de fluxo de trabalho team-lifecycle-v4, maestro-flow, community, orquestração de fluxo de trabalho, ide skills, arquitetura de software, desenvolvimento de software, automatização de processo

Sobre este Skill

Recursos

# Tópicos principais

Skill Overview

Por que usar essa habilidade

Melhor para

↓ Casos de Uso Práticos for team-lifecycle-v4

! Segurança e Limitações

About The Source

Browser Sandbox Environment

⚡️ Ready to unleash?

FAQ e etapas de instalação

? Perguntas frequentes