team-shutdown

Tears down completed multi-agent teams by deleting agents, removing worktrees, and updating AGENTS.md.

3|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill team-shutdown-arangogutierrez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-shutdown
Source: https://github.com/ArangoGutierrez/claude-toolkit/tree/main/.claude/skills/team-shutdown
Command: npx skills add https://github.com/ArangoGutierrez/claude-toolkit --skill team-shutdown-arangogutierrez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a multi-agent team engagement finishes, leftover agents, worktrees, and stale status records waste resources and pollute context. This Skill closes out a completed or abandoned team engagement in one verified pass instead of manual cleanup. ## Core Features & Use Cases - Completion Verification: Checks for open PRs and unmerged branches with gh pr list and git branch --no-merged, warning and asking for confirmation before tearing down work in progress. - Ordered Teardown: Delegates per-branch finishing to superpowers:finishing-a-development-branch, then runs TeamDelete, then removes worktrees — never in the wrong order. - Status Recording: Updates AGENTS.md with final task status (complete or abandoned) and commits it to the local-only agents-workbench branch. - Use Case: After all feature branches for the payment-retry team are merged, run the shutdown to delete the Principal Engineer, QA, and Worker agents, remove every .worktrees/<feature> directory, and mark all tasks complete in AGENTS.md. ## Quick Start Run /team-shutdown payment-retry to verify all branches are merged, shut down the team agents, remove the worktrees, and record final status in AGENTS.md.

Frequently Asked Questions about team-shutdown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I clean up a finished multi-agent team in Claude Code?▼

Run /team-shutdown <project-name> after all tasks are merged or abandoned. It verifies completion, delegates per-branch finishing, runs TeamDelete on all spawned agents, removes .worktrees directories, and updates AGENTS.md with final status.

What happens if PRs are still open when running team-shutdown?▼

The skill checks gh pr list and git branch --no-merged first. If open or unmerged work remains, it lists the branches and asks for confirmation before proceeding rather than silently discarding work in progress.

Should I run TeamDelete before removing git worktrees?▼

No. Finish each worker branch first via superpowers:finishing-a-development-branch, then run TeamDelete, then remove worktrees. A torn-down agent cannot iterate on a PR, so deletion must come after branch finishing.

When should I not use team-shutdown?▼

Do not use it while PRs are still open for review — that phase belongs to team-execute's review cycle. It is only for engagements where all tasks are merged or explicitly abandoned.

Does team-shutdown push the AGENTS.md status commit?▼

No. The final AGENTS.md status commit goes to the agents-workbench branch, which is local-only and must never be pushed to a remote.