team-lifecycle-v4

team-lifecycle-v4 is a skill for Claude Code from catlog22/Claude-Code-Workflow. It costs 41 tokens per session (1,781 once invoked), scanned A, original, MIT.

A coordinated software development workflow covering specification, planning, implementation, testing, and code review in one session.

In plain words
What is it for?
Use it to take a task from requirements through coding, tests, and review with coordinator, analyst, writer, planner, and worker roles.
Why use it?
It connects the main development stages and assigns specialized roles, reducing the need to coordinate each stage manually.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it to take a task from requirements through coding, tests, and review with coordinator, analyst, writer, planner, and worker roles.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/catlog22/claude-code-workflow/team-lifecycle-v4
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add catlog22/Claude-Code-Workflow --skill team-lifecycle-v4
Clone the repo
git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for team-lifecycle-v4

README.md
[![agentmods](https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-lifecycle-v4/github.svg)](https://agentmods.dev/skills/catlog22/claude-code-workflow/team-lifecycle-v4)
Your own site
<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/team-lifecycle-v4"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-lifecycle-v4/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for team-lifecycle-v4

Your own site · 80×15
<a href="https://agentmods.dev/skills/catlog22/claude-code-workflow/team-lifecycle-v4"><img src="https://agentmods.dev/badge/skills/catlog22/claude-code-workflow/team-lifecycle-v4.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,781 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.01781
Opus 5.5 $0.00016 $0.00712
Sonnet 5.5 $0.00008 $0.00356
Haiku 4.5 $0.00004 $0.00178

Measured 1mo ago against content hash f7d75992d1f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

team-lifecycle-v4 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/team-lifecycle-v4/SKILL.md · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Team Lifecycle v4

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-* dynamic
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 → @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>, ...)

Read the full file on GitHub · 210 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 210 lines · 41 tokens per session scan A f7d75992d1f2

Subscribe to this mod's changes

team-lifecycle-v4 is a skill published in the GitHub repository catlog22/Claude-Code-Workflow (2,124 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,781 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.