teamwork-clean

# Teamwork Clean

## Overview

Teamwork-clean resets a project's execution state to start fresh while preserving project metadata and history.

### Core Principles

1. **Surgical deletion** - Only removes execution artifacts (tasks, verification, workers)
2. **Metadata preservation** - Project identity, goal, and creation timestamp remain intact
3. **Idempotent operation** - Safe to run multiple times, won't clean already-cleaned projects
4. **Fresh start marker** - Adds `cleaned_at` timestamp to track cleanup history

### Use Case

When task state becomes inconsistent, workflow fails, or you need to restart execution with the same project configuration.

---

## When to Use

**USE teamwork-clean for:**
- Starting a new run in the same project (multiple attempts at same goal)
- Recovering from failed orchestration or stuck workers
- Cleaning up after testing or experimentation
- Resolving state corruption (duplicate tasks, conflicting claims, orphaned locks)

**DON'T use teamwork-clean for:**
- Normal project completion (state is valuable)
- Abandoning a project (use project deletion instead)
- Fixing a single task (use task-update --release instead)
- Active projects with workers running (stop workers first)

---

## What Gets Cleaned

The clean operation **deletes** these directories completely:

| Directory | Contents | Impact |
|-----------|----------|--------|
| `tasks/` | All task files (*.json) | Task definitions, status, evidence, claims |
| `verification/` | Verification results (wave-*.json, final.json) | Wave and final verification history |
| `workers/` | Worker state and logs | Worker session tracking, activity history |

**After cleanup**: These directories no longer exist. You start with a blank slate for execution.

---

## What's Preserved

The clean operation **preserves** project metadata:

| File | Preserved Data | Changes |
|------|---------------|---------|
| `project.json` | - Project name and team<br>- Goal description<br>- Creation timestamp