菜单
Use for /wf-update in Claude Code, $wf-update or /skills wf-update in Codex, or any request to check for or apply Harness scaffold updates.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Perpetual auto-optimization mode. Never stops until 8-angle exhaustion. Inherits WF acceptance gates and subagent orchestration per cycle. Use for Claude /wf-auto, Codex $wf-auto, auto mode, or unbounded self-directed optimization.
Perpetual inspiration mode for /wf-auto-spark or $wf-auto-spark. Inherits WF-AUTO/WF execution gates while using external spark search, roadmap anchoring, and <=50% deviation guard.
Use for /wf-learn in Claude Code, $wf-learn or /skills wf-learn in Codex, or when the user wants a learning cycle from repeated errors, corrections, patterns, or session history.
Use for /wf-max in Claude Code, $wf-max or /skills wf-max in Codex, or maximum-parallelism Harness work with WF strict-superset gates and CEO -> manager -> worker decomposition.
| name | wf-update |
| description | Use for /wf-update in Claude Code, $wf-update or /skills wf-update in Codex, or any request to check for or apply Harness scaffold updates. |
/wf-update or select the wf-update skill.$wf-update or /skills then choose wf-update.Harness/.harness-versionHarness/scripts/wf-update-check.mjsHarness/scripts/scan-clean.mjsHarness/scripts/validate-harness.mjsnode Harness/scripts/wf-update-check.mjs --json first and use the
agent block as the action plan.agent.safeApplyCommand is present, run it to apply SAFE, NEW, and
adopted metadata-only files before spending AI time on conflicts. Default command:
node Harness/scripts/wf-update-check.mjs --apply-safe.agent.aiMergeRequired entry, compare the local file with
templateHint or remoteUrl, then choose merge, keep-local, or
overwrite-from-template. Record the decision through the script with
--accept-local <file>, --accept-merged <file>, or
--accept-template <file>; do not hand-edit Harness/.harness-version.
Ask the user only when the intent is ambiguous.node Harness/scripts/wf-update-check.mjs --finalize after all
conflicts have script-recorded decisions. Use strict --apply only when the
JSON plan has zero conflicts.Report version, SAFE/NEW updates, conflicts and decisions, preserved files, partialUpdate status if any, validation output, scan-clean result, and remaining risks.