$ ./agent-harness --pitch

THE AGENTHARNESS

A skills framework + a risk/trust harness for the Claude Code CLI.
Brainstorm → ship — with the right amount of care at every step.

press → or Space to advance · F for fullscreen

01 / the problem

AI coding agents fail in two opposite ways

⚡

Vibe coding

Reckless autonomy — the agent executes fast, skips validation and understanding, and you inherit a diff you can't trust.

🐌

Analysis paralysis

Micromanaged into uselessness — asked to confirm every step, the speed advantage of an agent evaporates.

Both come from the same gap: the agent enters “with only a chat prompt and a shallow snapshot of files.”

02 / the fix

Give the agent a harness, not just a prompt

The app

What users touch.

The harness

What agents touch: a thin control layer in the repo that classifies each change, requires proof, and enforces the guardrails.

03 / the one principle

Two independent dials

RISK
↓ decides
how much proof & process a change carries
AMBIGUITY
↓ decides
whether a human is asked

Ceremony scales with risk. Interruption scales with ambiguity — not risk.

04 / the workflow

brainstorm → ship

/brainstorming

Design the change in writing before any code.

/writing-plans

Split the design into tasks, each with a verify command.

/subagent-driven-development

Build task by task, with a separate reviewer on each.

/correctness-review

Hunt for runtime bugs across the whole diff.

/intent-review

Check the diff against what was actually asked.

/finishing-a-development-branch

Open a PR. A human merges.

Small changes skip most of this. /feature-intake decides which steps apply.

05 / three lanes

Ceremony, sized to risk

tiny
branch + direct edit · no plan · no human gate · hooks are the net
normal
plan + per-task review · notify-and-proceed
high-risk
full chain · recorded rollback · human gate on ambiguity / hard gate

Proof is required, not asserted — and it scales down for small work.

06 / hard gates

These always force high-risk

auth
authorization
data-loss / migration
audit / security
external provider
public contract
weakening validation
high-blast file
workflow-engine

Only a human narrowing scope can lower them — and a gate found mid-task escalates regardless of the original lane.

07 / enforcement over convention

Rules enforced by code, not hope.

What can be mechanized is a hook — fail-closed. A commit-time check re-reads the diff and corroborates the declared lane: the agent can't label a risky change “tiny” and slip it through.

branch isolation · secrets scan · pending escalations · lane evidence · risk corroboration · plan scope

08 / the outcome

Humans steer. Agents execute.

Less ceremony on small work

Typo and copy fixes go straight through.

More proof on risky work

Auth and migrations get a plan, reviews and a rollback point.

Asked at the right moments

A human is interrupted for unclear intent, not for every step.

09 / see it live

Try it yourself

Browse the skills, or watch a scripted run in the vibe demo.

install: curl … install-harness.sh | bash -s -- --yes

15 / standing on the shoulders of

superpowers

@obra — skill engine

GSD

@gsd-build — spec-driven dev

Compound eng.

Every — learning loop

harness-experimental

@hoangnb24 — risk/trust

Thanks. Now go ship.

github.com/minhtran3124/agent-harness

~/agent-harness
▸ arrows / space to move · F fullscreen · swipe on mobile
1 / 16