メニュー
Orchestrate the entire IMPLEMENT phase — test-driven implementation of the approved plan, resolving build/type errors as they arise. Use after /harness-plan. Sequences /implement and /build-fix, delegates to subagents, and halts if reality diverges from the plan.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Bug-fix fast lane — the entry point for fixing something already broken (a red test, a prod error, a reported defect), not building a new feature. Does the bug-specific part — reproduce as a failing test, find the root cause, write a minimal fix-plan — then hands off to the existing pipeline (/implement → /review → /security-review → /verify → /ship) so the fix rides the proven gates. The non-negotiable discipline: reproduce as a failing test FIRST, fix minimally. Opt-in; invoked explicitly. Use when something is broken and you want it fixed under the harness's gates without over-ceremonying it through /spec.
Execute a plan via test-driven development — write tests first, then minimal code, phase by phase. Use after /plan (and /architect if needed) to write the actual feature. Delegates to the harness-claude:tdd-guide agent.
Review changed code for quality, correctness, and maintainability before merge. Use immediately after implementing or modifying code. Delegates to the harness-claude:code-reviewer agent. First gate of the Verify phase.
Confirm the change actually works by running the app/feature and observing real behavior — not just that tests pass. Use late in the Verify phase, before ship. Closes the loop between "tests green" and "it works."
Orchestrate the entire PLAN phase in one command — spec, research, plan, plan-check, and (if warranted) architecture. Use at the start of any non-trivial feature/change. Sequences the atomic skills, delegates to subagents, and pauses for your input at each decision gate.
Run the FULL SDLC pipeline end-to-end — Plan → Implement → Verify → Maintain — with a checkpoint between every phase. Use for a complete feature from a one-line idea to merge-ready. Chains the four phase orchestrators; you approve each phase boundary.
| name | harness-implement |
| description | Orchestrate the entire IMPLEMENT phase — test-driven implementation of the approved plan, resolving build/type errors as they arise. Use after /harness-plan. Sequences /implement and /build-fix, delegates to subagents, and halts if reality diverges from the plan. |
Thin orchestrator over the Implement skills. Requires an approved plan from
/harness-claude:harness-plan (or /harness-claude:plan). Refuse to start without one for non-trivial work.
For each plan phase, in order:
/harness-claude:implement — delegate to the harness-claude:tdd-guide agent: failing test (RED) →
minimum code (GREEN) → refactor, against the phase's acceptance criteria./harness-claude:orchestrate — name the file split and let the user choose.
The offer is not optional (that's the only way parallel mode fires); acting on it stays
opt-in — never auto-start a multi-agent run./harness-claude:build-fix (delegate to
the harness-claude:build-error-resolver agent), minimal diffs only.Plan-divergence gate: if reality contradicts the plan (a phase is wrong, missing, or bigger than scoped), HALT — report the divergence, update the plan with the user, then resume. Never silently improvise scope.
rules/git.md
(branch-at-first-write in /harness-claude:implement).Phase-by-phase summary (what was built, tests added, build status). Then hand off to
/harness-claude:harness-verify.