What is manage-teams?

A guided manager for the lifecycle of coding-agent teams: creating, updating, deleting, and reviewing teams.

Use it to create teams, change their members, remove teams, or audit the full delegation workforce.

It keeps team rosters, descriptions, status, and deployment information organized as the workforce changes.

manage-teams — Skill for Claude Code by SteveGJones

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add SteveGJones/ai-first-sdlc-practices

Claude Code

/plugin install sdlc-workflows

Made for: Claude Code.

Or install sdlc-workflows, the plugin that ships this one along with the rest of its 6 skills, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/manage-teams/github.svg)](https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/manage-teams)

Your own site

<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/manage-teams"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/manage-teams/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/manage-teams"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/manage-teams.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,004 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.03004
Opus 5.5	$0.00014	$0.01202
Sonnet 5.5	$0.00007	$0.00601
Haiku 4.5	$0.00003	$0.00300

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

Security

Grade C, and why

manage-teams scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .archon/teams/.generated/<team>*

plugins/sdlc-workflows/skills/manage-teams/SKILL.md · 403 lines

How it starts

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

Manage Delegation Teams

Guided Q&A coaching for team lifecycle management. Follows the same interactive pattern as /sdlc-core:setup-team.

Modes (pass exactly one flag)

This skill has four modes. Argument autocomplete does not show flag variants, so the mode menu is always in the body — pick one before proceeding.

--create — create a new team with guided coaching (default choice when the user says "I need a team")
--update <team> — update an existing team's roster or description
--delete <team> — delete a team (removes manifest + image)
--review — audit the entire delegation workforce (fleet table, staleness, workflow usage, coaching signals). Add --team <name> for a single-team detail view.

For task-to-workflow recommendation ("I have a task, which workflow and team formation should I use?") use /sdlc-workflows:author-workflow --for-task "<description>" — that skill owns workflow+formation planning.

Lifecycle Model

Teams have a simple lifecycle:

Create → manifest written to .archon/teams/<name>.yaml with status: active
Update → manifest modified, updated timestamp set, image marked stale
Delete → manifest file removed, Docker image removed, git history provides audit trail

There are no intermediate states. A manifest exists and is active, or it has been deleted. Git history provides the full audit trail for compliance.

Mode: `--create`

Step 1: Right-sizing check

Before creating a team, assess the project's delegation maturity:

ls .archon/teams/*.yaml 2>/dev/null | wc -l
ls .archon/workflows/*.yaml 2>/dev/null | wc -l

If no teams exist (Level 1 adoption):

You don't have any delegation teams yet.

For your first team, I recommend a general-purpose team that mirrors
your current Claude Code environment — all your installed plugins,
agents, and skills.

This gets you to your first delegated workflow run with one command.
You can specialise into multiple teams later as your needs become
clearer.

  (a) Create a general-purpose team (recommended for first-time setup)
  (b) Create a specialist team (I know what I want)

Read the full file on GitHub · 403 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.

1mo ago First seen · 403 lines · 34 tokens per session scan C 7703c9a1269f

Subscribe to this mod's changes

manage-teams is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 34 tokens to every session and 3,004 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Building agents Project management

story-readiness

Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.

Donchitos/Claude-Code-Game-Studios · 48 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

manage-teams