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
Reckless autonomy — the agent executes fast, skips validation and understanding, and you inherit a diff you can't trust.
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.”
What users touch.
What agents touch: a thin control layer in the repo that classifies each change, requires proof, and enforces the guardrails.
Ceremony scales with risk. Interruption scales with ambiguity — not risk.
Design the change in writing before any code.
Split the design into tasks, each with a verify command.
Build task by task, with a separate reviewer on each.
Hunt for runtime bugs across the whole diff.
Check the diff against what was actually asked.
Open a PR. A human merges.
Small changes skip most of this. /feature-intake decides which steps apply.
Proof is required, not asserted — and it scales down for small work.
Only a human narrowing scope can lower them — and a gate found mid-task escalates regardless of the original lane.
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
Typo and copy fixes go straight through.
Auth and migrations get a plan, reviews and a rollback point.
A human is interrupted for unclear intent, not for every step.
Browse the skills, or watch a scripted run in the vibe demo.
install: curl … install-harness.sh | bash -s -- --yes
@obra — skill engine
@gsd-build — spec-driven dev
Every — learning loop
@hoangnb24 — risk/trust
Thanks. Now go ship.
github.com/minhtran3124/agent-harness