templates/skills/team-stop/SKILL.md
Clean up an agent team. Removes team resources, optionally cleans worktrees and branches. Use after team work is complete and merged. Use when told to "stop team", "cleanup team", "disband team".
npx skillsauth add samwang0723/claudecode-setup team-stopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/team-stop <team-name>
.claude/tasks/{slug}/_status.md.dev-{N}.md reports exist.Present what will be cleaned up:
## Team Cleanup: {slug}
Resources to remove:
- Team config: ~/.claude/teams/{slug}/
- Worktrees: .worktrees/{slug}/dev-{1..N}/
- Branches: {slug}/dev-{1..N}
Resources to KEEP:
- Task docs: .claude/tasks/{slug}/*.md
- Integrate branch: {slug}/integrate (if exists)
Proceed? (awaiting confirmation)
TeamDelete tool (via ToolSearch) → delete team config.cd .worktrees/{slug}/dev-{N} && git status --porcelain
If any worktree has uncommitted changes, warn Master and list the affected files.
Do NOT proceed with removal until Master confirms it is safe to discard or commits are made.git worktree remove .worktrees/{slug}/dev-{N} --force
git branch -D {slug}/dev-{N}
_status.md:
(cleaned up {date})TeamDelete not working and sub-agent not responding, Kill all idle agent tmux panes but leave the main session intact.
List tmux panes, identify agent/teammate panes, and kill them individually:
# Kill agent panes (NOT the main session pane)
tmux list-panes -a -F '#{pane_id} #{pane_title}' | grep -i 'teammate\|agent\|dev-' | awk '{print $1}' | xargs -I{} tmux kill-pane -t {}
## Team Cleaned Up: {slug}
- Removed: {N} worktrees, {N} branches, team config
- Preserved: .claude/tasks/{slug}/ (all reports)
- Integrate branch: {kept/removed} based on merge status
NEVER auto-clean without Master confirmation.
Team: $ARGUMENTS
development
Generate a technical specification document using the DDD template in template.md. Use when the user says 'write tech spec', 'create tech spec', 'technical specification', or needs a structured design document for a new feature or major change covering architecture, domain models, APIs, data design, security, and operations.
testing
Write a Product Requirements Document (PRD) using the standard TMAB template with stakeholders, user stories (Given-When-Then), success metrics, and A/B testing plans. Use when the user asks to write a PRD, create product requirements, document a feature spec, or plan a new product feature.
testing
Check progress of an active agent team. Shows member status, completed tasks, pending work, and any messages. Use when asked "team status", "how's the team", "check team progress", "team update".
development
Spawn an agent team with multiple parallel Claude instances in tmux panes. Each teammate is a separate session with its own context window. Creates git worktrees and markdown state tracking alongside JSON tasks. Supports: --agents (comma-separated), --members N, --devs N. Use when told to "team up", "parallel team", "spawn a team", or "standby".