claude-code-harness

Claude Code Harness

Plan. Work. Review. Ship.
A disciplined delivery loop for Claude Code, with bounded paths for Codex and OpenCode.

English | 日本語

Claude Code is powerful, but raw agent work drifts: plans live in chat, tests become optional, review happens too late, and release evidence gets rebuilt by memory. Harness turns that into one repeatable operating path.

After install, the default changes from "ask the agent to code" to:

1. write the spec and plan,
2. implement only the approved slice,
3. verify the result,
4. review independently,
5. package evidence for PR or release.

Claims in this README are machine-checked against the code. CI gates verify that implemented components are actually wired (no dead code claimed as done), that the task ledger's dependencies stay consistent, and that the shipped binaries rebuild from source. A feature is described here only after a gate proves it is reachable — "written" is not "working."

Quickstart

New users should start from the tool they already use. Existing users should run the migration report before cleanup or reinstall.

Path	Start
New user	Tool-first onboarding
Existing user	Migration check
Claude Code fast path	Install in 30 seconds
Trigger proof	Skill trigger gate

Install in 30 Seconds

claude
/plugin marketplace add Chachamaru127/claude-code-harness
/plugin install claude-code-harness@claude-code-harness-marketplace
/harness-setup

Next command: run /harness-plan with one small request.

/harness-plan Improve the README onboarding flow

First 15 Minutes

1. Install through your tool route.
2. Run /harness-setup or the equivalent setup script.
3. Run /harness-plan with a small request; Harness writes the spec.md and Plans.md drafts for you to check. Small typo, docs, and status updates stay lightweight.
4. Approve the generated contract or reply with the correction you want.
5. Run the smallest approved task, for example /harness-work 1.1.1.
6. Run /harness-review and keep the verification output.

Your job is not to hand-write the plan. It is to approve or correct the generated contract before execution continues.

How It Works

Harness adds a source-of-truth loop around agent work. The 5 verb skills keep that surface small: plan, work, review, sync, release.

1. You describe the outcome in normal language.
2. /harness-plan drafts or updates spec.md and Plans.md with scope, acceptance criteria, unknowns, and stop conditions.
3. Non-trivial planning records team_validation_mode and validates the plan through team/sub-agent or manual-pass perspectives for spec/Plans alignment, memory reuse, product fit, security fit, and works-in-practice.
4. Harness treats those files as the source of truth. Data the agent has not seen stays unknown instead of being silently invented.
5. /harness-work implements the approved slice with TDD and verification.
6. /harness-review separates review from implementation.
7. /harness-release packages only verified evidence.

Commands