Remove

remove — uninstall project-local teams governance

Remove the files and registrations created by install, without disturbing unrelated Claude settings, project instructions, or harness's own files. The deterministic work lives in remove.mjs.

Process

1. List what will be removed unconditionally: .claude/team.json, .claude/teams-dispatch.json, the fenced <!-- teams:begin --> block in CLAUDE.md, and the teams lines in .gitignore. .claude/.harness-markers/ is removed too, unless .claude/harness-gate.json is present, in which case harness also owns that directory and it is kept.
2. Conventions, .teams_output/ (run history), and this project's tasks under ~/.harness/tasks/ are kept by default. Ask for explicit confirmation, one at a time, before passing purgeConventions, purgeRuns, or purgeTasks as true — conventions may hold project edits, and run/task history may still be wanted for review.
3. Run:

   node "<plugin>/skills/remove/remove.mjs" '{
     "projectDir": "<abs project root>",
     "purgeConventions": false,
     "purgeRuns": false,
     "purgeTasks": false
   }'
   

4. Read the JSON report and pass it through as-is: marker-error means CLAUDE.md had unmatched teams:begin/end markers and was left untouched; kept-harness means the marker directory was left for harness; refused-alive (only under tasks, with purgeTasks: true) means a task rooted at this project still has a live driver process and was skipped — tell the user which task id and that its driver must stop first.
5. Verify the listed paths are gone and that unrelated settings, CLAUDE.md content, and harness's own files remain untouched.

The operation is idempotent: a second run reports absent for everything already removed.

Related

• install — scaffold the files this skill removes
• patch — prepare a teams plugin source release
• harness:remove — the harness's own uninstaller (shares the marker directory)