メニュー
This skill should be used only when the user explicitly asks to use `$ralphharness-research`, or explicitly asks RalphHarness in Codex to run the research phase.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Canonical rules for the external-reviewer bootstrap, liveness heartbeat freshness gate, and convergence detection. This skill is the single source of truth for reviewer-warmup behavior.
Use only when the user explicitly invokes `$ralphharness`, requests RalphHarness in Codex, asks RalphHarness to handle a named phase, or explicitly requests autonomous or quick mode or continuation without pauses.
Load this skill suite for any spec that involves end-to-end testing, browser automation, Playwright, MCP browser tools, VE tasks, user flow verification, UI testing, or integration tests that drive a real browser. Covers session lifecycle, environment setup, navigation anti-patterns, stable-state detection, auth flows, selector stability, and cleanup guarantees.
This skill should be used only when the user explicitly asks to use `$ralphharness-design`, or explicitly asks RalphHarness in Codex to run the design phase.
This skill should be used only when the user explicitly asks to use `$ralphharness-design`, or explicitly asks RalphHarness in Codex to run the design phase.
This skill should be used only when the user explicitly asks to use `$ralphharness-implement`, or explicitly asks RalphHarness in Codex to run implementation for approved tasks, quick mode, or an explicit continue request.
| name | ralphharness-research |
| description | This skill should be used only when the user explicitly asks to use `$ralphharness-research`, or explicitly asks RalphHarness in Codex to run the research phase. |
| metadata | {"surface":"helper","action":"research"} |
Use this for the research phase.
.current-spec.claude/ralphharness.local.md when present./specs.progress.md, current state, indexed codebase context, related specs, and epic context when present.research.md in the spec directory.phase: "research" and awaitingApproval: true..progress.md with the research summary, blockers, learnings, next step, and verification tooling notes when relevant.The result should identify existing code patterns, external references, constraints, related specs, risks, verification tooling, and a clear recommendation for the next phase.
research.md, name research.md and summarize the research briefly.approve current artifactrequest changescontinue to requirementscontinue to requirements as approval of research.md.