一键导入
wf
Use for /wf in Claude Code, $wf or /skills wf in Codex. WF is explicit only — the user must type /wf, $wf, or /skills wf to enter.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use for /wf in Claude Code, $wf or /skills wf in Codex. WF is explicit only — the user must type /wf, $wf, or /skills wf to enter.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 |
| description | Use for /wf in Claude Code, $wf or /skills wf in Codex. WF is explicit only — the user must type /wf, $wf, or /skills wf to enter. |
This skill is a thin tool adapter. The authoritative workflow lives in
Harness/specs/workflows/WF.md; do not duplicate or override it here.
/wf <task> or select the wf skill.$wf or /skills then choose wf./ menu, depending on the
current surface and feature state./wf-help are exempt.CLAUDE.md, Harness/MEMORY.md index only, then Harness/README.md before planning, dispatch, edits/deletes, validation, or peer review.Harness/memory/* only when MEMORY_PROTOCOL.md scenario hints match; otherwise record "memory hints: none".CLAUDE.mdHarness/MEMORY.md (index only per Memory Preflight)Harness/README.mdHarness/PROGRESS.mdHarness/specs/workflows/WF.mdHarness/specs/runtime/subagents.md before any role splitFollow Harness/specs/runtime/context-loading.md#Cache-First Context Contract: keep the
listed loads in order, load only routed skills/tools, append task state and
latest tool output after stable docs, and return compact evidence instead of
logs or transcripts.
Harness/tasks/<task-id>/; new task
ids MUST match task-<verb>-<noun>[-detail].Harness/specs/workflows/WF.md: intake, bounded exploration, second
plan, implementation, review, verification, recovery, and closeout.Harness/tasks/<task-id>/PROGRESS.md#Heartbeat current before long
commands, after failures, and at closeout.