一键导入
teamwork-clean
Reset and clean up teamwork project state. Use when project is stuck, failed, or needs a fresh start. Uses native TeamDelete API for cleanup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Reset and clean up teamwork project state. Use when project is stuck, failed, or needs a fresh start. Uses native TeamDelete API for cleanup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | teamwork-clean |
| description | Reset and clean up teamwork project state. Use when project is stuck, failed, or needs a fresh start. Uses native TeamDelete API for cleanup. |
| user-invocable | false |
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 |
Event-driven coordination for teamwork orchestrators. Replaces polling-based monitoring loop with TeammateIdle and TaskCompleted hooks.
Hybrid task decomposition strategy for teamwork projects. Covers plan-based and semantic decomposition, granularity rules, role assignment, dependency management, and complexity assessment.
8-phase task execution lifecycle for teamwork workers using native Claude Code APIs. Covers task discovery, claiming, structured description parsing, TDD workflow, implementation, verification, selective commit, and completion reporting.
Architecture design review skill for reviewer agents. Component boundaries, separation of concerns, modularity, and design pattern validation. Use during PLANNING phase to validate design decisions and VERIFICATION to ensure adherence.
API design, database operations, error handling, and backend architecture patterns. Use when creating APIs, database schemas, or server-side logic.
Code quality verification skill for reviewer agents. Provides checklists for logic clarity, error handling, maintainability, and performance. Use during VERIFICATION phase to assess implementation quality.