From teamwork
Reset and clean up teamwork project state. Use when project is stuck, failed, or needs a fresh start. Uses native TeamDelete API for cleanup.
How this skill is triggered — by the user, by Claude, or both
Slash command
/teamwork:teamwork-cleanThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Teamwork-clean resets a project to start fresh by cleaning up team and task state.
Teamwork-clean resets a project to start fresh by cleaning up team and task state.
TeamDelete() to remove team and all associated tasksWhen task state becomes inconsistent, workflow fails, or you need to restart execution with the same project configuration.
USE teamwork-clean for:
DON'T use teamwork-clean for:
Before cleaning, send shutdown messages to all active teammates:
# Notify all workers to stop
SendMessage(
type="shutdown_request",
recipient="worker-backend",
content="Project cleanup in progress. Please stop."
)
SendMessage(
type="shutdown_request",
recipient="worker-frontend",
content="Project cleanup in progress. Please stop."
)
Use the native TeamDelete API to remove the team and all associated tasks:
# Delete team (removes all tasks and team state)
TeamDelete()
This removes:
If restarting with the same goal, create a new team:
# Create fresh team
TeamCreate(team_name="<team-name>", description="<project goal>")
# Recreate tasks from scratch
TaskCreate(subject="...", description="...")
| Item | Method | Impact |
|---|---|---|
| All tasks | TeamDelete() | Task definitions, status, evidence, ownership |
| Team state | TeamDelete() | Team metadata and configuration |
| Worker associations | TeamDelete() | Worker-to-team bindings |
After cleanup: The team no longer exists. You start with a blank slate.
| Item | Why |
|---|---|
| Project files on disk | Code changes remain in the git repository |
| Git history | All commits from previous run are preserved |
| Project metadata files | Plugin-level project.json if used by project-create.js |
/teamwork-clean
# 1. Check current status
/teamwork-status
# 2. Clean the project
/teamwork-clean
# 3. Start fresh
/teamwork "same goal or updated goal"
# Project failed, want to retry with different approach
/teamwork-clean
# Orchestrator will plan from scratch
/teamwork "updated goal with more context"
Before recommending /teamwork-clean, verify:
Is the project stuck?
Are workers stopped?
Is cleanup the right solution?
/teamwork-status only| Situation | Recommend Clean? | Alternative |
|---|---|---|
| First project attempt failed | Yes | Clean and retry |
| Multiple tasks stuck | Yes | Shutdown workers, clean, restart |
| Single task needs retry | No | Release the task |
| Want to change goal | Yes | Clean and start with new goal |
| Checking progress | No | Use /teamwork-status |
| Command | Purpose | When to Use |
|---|---|---|
/teamwork | Start or resume project | After cleaning, to begin fresh execution |
/teamwork-status | Check project progress | Before cleaning, to diagnose issues |
npx claudepluginhub mnthe/hardworker-marketplace --plugin teamworkCreates and manages dynamic teams of domain-specific agents. Analyzes project to propose 5-20 agents with tracking framework. Modes: create, update, status, cleanup.
Orchestrates TASKS.md execution at scale with team (Agent Teams API, 3-level hierarchy), auto (task dispatch), or thin (minimal context) modes; auto-selects by task count and infrastructure.
Use when a task benefits from multiple Claude instances collaborating with peer-to-peer messaging - parallel research, multi-module features, cross-layer changes, or competing hypothesis debugging. Not for simple independent tasks (use parallel-execution) or sequential tasks (use delegated-execution).