القائمة
Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work.
التثبيت باستخدام 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-readme |
| description | Use when a project README already exists and the user asks to preserve, merge, modernize, optimize, or clarify repository documentation during harness install or documentation work. |
Improve README.md without breaking project-owned public docs.
README.mdpackage.json, pyproject.toml, go.mod, etc.)Harness/PROGRESS.mdHarness/tasks/<task-id>/PLAN.md when availableHarness/project/architecture.md only when an architecture summary or diagram is requestedFollow Harness/specs/runtime/context-loading.md#Cache-First Context Contract: load project
facts in the listed order, inspect only relevant README/package/CI sections, and
keep unknowns or command output in the dynamic suffix.
Ask the user which mode they approve when the existing README is meaningful:
| Mode | Use when | Allowed edit |
|---|---|---|
| Preserve + append | default for existing projects | Add only a compact Development, Test, Build, Git, or Harness section |
| Structure pass | README is stale, hard to scan, or missing operational docs | Reorganize with headings, tables, command blocks, and links while preserving facts |
| Full rewrite | user explicitly wants a polished public README | Rewrite after approval; keep claims source-backed |
If unanswered, use Preserve + append.
Harness/project/architecture.md; README may link to it or show a short overview.CLAUDE.md/AGENTS.md, not README.Harness/tasks/<task-id>/PLAN.md when available.Before broad edits, return: