When should I use teamwork-clean instead of deleting the project directory?

Use teamwork-clean when you want to keep the same project goal and metadata but want the agents to re-plan and re-execute the task list from scratch.

Can I undo a project cleanup operation?

No, the deletion of task definitions, worker logs, and verification results is irreversible. Ensure any valuable execution evidence is backed up if needed.

Is it safe to run this skill while workers are currently active?

No, you should stop all active workers (typically using Ctrl+C in their respective terminals) before running the clean command to prevent race conditions.

Does teamwork-clean delete my project.json file?

No, the command specifically preserves project.json to keep your project name, team, goal, and creation history intact while only removing execution artifacts.

Teamwork Clean

Name: Teamwork Clean
Author: mnthe

bymnthe

•

Collaboration Tools

Resets project execution states by clearing task, worker, and verification data while preserving core project metadata.

About

Teamwork Clean is a specialized utility for the Hardworker multi-agent framework that allows developers to perform a surgical reset of a project's execution artifacts. By deleting specific directories like tasks, verification, and workers, it resolves state corruption and allows for a fresh start without losing the original project identity, goals, or timestamps. It is an essential tool for recovering from failed orchestrations or stuck agent workers during complex automated workflows, ensuring that project metadata remains intact for continuous tracking.

Key Features

Surgical deletion of execution artifacts including tasks, verification, and worker logs
Project statistics reset to 0 for accurate reporting of fresh execution runs
Idempotent operation safety, ensuring projects aren't cleaned multiple times
Automatic 'cleaned_at' timestamping to maintain a clear audit trail of resets
2 GitHub stars
Metadata preservation for project identity, goals, and creation timestamps

Use Cases

Restarting a failed orchestration attempt with the same project goal and configuration
Recovering from inconsistent task states, duplicate claims, or stuck agent workers
Cleaning up temporary test tasks and experimentation data before starting production work

About

Key Features

Surgical deletion of execution artifacts including tasks, verification, and worker logs
Project statistics reset to 0 for accurate reporting of fresh execution runs
Idempotent operation safety, ensuring projects aren't cleaned multiple times
Automatic 'cleaned_at' timestamping to maintain a clear audit trail of resets
2 GitHub stars
Metadata preservation for project identity, goals, and creation timestamps

Use Cases

Restarting a failed orchestration attempt with the same project goal and configuration
Recovering from inconsistent task states, duplicate claims, or stuck agent workers
Cleaning up temporary test tasks and experimentation data before starting production work