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.”
“Coding agents do not only need better prompts.
They need better repositories.”
The repo itself lacks agent-addressable context — so constraints get lost to chat history, validation is skipped, and architecture decisions get re-litigated every session.
“The app is what users touch.
The harness is what agents touch.”
Build a thin, git-operable control layer for the agent — classification, proof, and guardrails it can read and act on.
Ceremony scales with risk. Interruption scales with ambiguity — not risk.
Invocable /skills that do the work: brainstorm · research · plan · build · review · ship. Each with hard gates and a defined handoff.
Decides before the engine runs: how much process a change needs, and when to ask a human. Intake · hooks · rules · evidence.
Engine answers “how do I build this?” · Harness answers “how careful, and who approves?”
Intake decides how many of these steps actually run.
“The human does not need to classify risk.
The harness does.”
/feature-intake runs a 10-flag risk checklist + hard gates → a lane, and a confidence score → whether to ask a human. Deterministic, every time.
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.
secrets scan · debug-artifact check · targeted tests · risk corroboration · blast-radius · ruff
A knowledge graph gives structural context; /compound captures every bug, decision & insight into docs/solutions/ for future agents.
Typo / copy / narrow edits skip planning entirely.
Auth, migrations, contracts → full plan + reviews + rollback.
Approval gates on ambiguity, not on every step.
“Done” needs a re-runnable verify artifact.
The human moves from per-task gatekeeper to rule author & exception handler.
An interactive guide — with a live /feature-intake classifier you can play with.
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 — gated by risk.
github.com/minhtran3124/agent-harness