Menu
Use for /wf-remove in Claude Code, $wf-remove or /skills wf-remove in Codex, or any request to uninstall Harness safely.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Built-in browser automation and E2E verification workflow. Use for Claude /wf-browser, Codex $wf-browser or /skills wf-browser, Browser Use, Playwright, Chrome DevTools/CDP, screenshots, forms, UI verification, and browser-visible acceptance.
Codex compatibility: use $wf-help or /skills wf-help in Codex to show the Harness WF command table. Claude Code and OpenCode use the direct /wf-help command.
Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex. WF-MAX is explicit only — the user must type /wf-max, $wf-max, or /skills wf-max.
Use when work needs bounded subagent coordination, parallel read-only exploration, independent review gates, broad context partitioning, or controlled handoffs.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Source-backed CLI invocation guide for Claude Code, Codex, and OpenCode automation. Use when invoking peer CLIs, writing batch tests, collecting cache telemetry, debugging command-line flags, or documenting cross-runtime agent usage for Harness workflows.
| name | wf-remove |
| description | Use for /wf-remove in Claude Code, $wf-remove or /skills wf-remove in Codex, or any request to uninstall Harness safely. |
/wf-remove or select the wf-remove skill.$wf-remove or /skills then choose wf-remove.Harness/.harness-versionHarness/scripts/wf-remove.mjsFollow Harness/specs/runtime/context-loading.md#Cache-First Context Contract: use the
script's compact JSON plan as the dynamic suffix, avoid manual directory dumps,
and keep user decisions in task progress rather than chat transcript.
/wf-remove, run node Harness/scripts/wf-remove.mjs --json for
the machine-readable plan, then run the safe default apply command yourself.--purge-user-data (alias --purge); add --keep-tasks when the user wants task records
retained while project-fact Harness docs are removed.node Harness/scripts/wf-remove.mjs --apply --yesnode Harness/scripts/wf-remove.mjs --apply --yes --purge-user-data --keep-tasks--delete-modified <path> for each
user-approved MODIFIED file..claude/agents.claude/skills.claude/commands.claude/rules.agents/skills.codex
Built-in Harness files in these locations should be gone. Custom user skills
or user-owned files may remain and must be reported, not blindly deleted.Report SAFE removals, MODIFIED keep/delete decisions, preserved USER DATA,
PURGE removals, directory cleanup, .claude / .agents / .codex residual
status, .harness-version status, and git status guidance.