← Back to slide 07Repository →

Read more · slide 07 / 07 · when

As much as the work needs.

Rigour has a cost, and it should be paid where it buys something. dev-rigour-min starts quiet and adds only what the work calls for.

1 Specified2 Agreed3 Met

Who it is for

dev-rigour-min runs inside Claude Code, on Node.js 23.6 or newer, and you install it from a terminal. If a terminal is new to you, start with something simpler.

It suits people who know what good looks like. You start the sessions, answer the four-part asks, look at the drawings, approve them or send them back, and read the handover before the next session begins. The agent does the legwork. Whether the result is good stays yours to judge.

That is the opposite of vibe coding, by design. If you want to type a prompt and take what comes back, this will feel slow, and it will keep stopping to ask you. For a one-chat job, the set-up costs more than it saves.

When to skip it

For a quick prototype or a throwaway idea, vibe coding is fine. Nothing here is needed to find out whether an idea is worth pursuing.

The default

Out of the box it does three things. It keeps a copy before an edit. It stops the careless moves and tells you the one sentence to type. And it asks, in four parts, when a decision is yours. The process a larger team runs is present, and switched off.

Substantial work

A new mechanism, or work across several files or sessions, gets a short plan you confirm before anything is edited. Before the first build, the architecture is written down: what exists, where it must end up, the gap between. The security baseline is walked once. The plan says how the work will be checked before it is built, and the build shows those checks passing before it is called done.

High stakes

On sign-in, payments, personal data, a destructive migration or work that spans sessions, it raises its own rigour: more stops, more pushback, more looking ahead, a stricter bar before done. It says so in its reply, so you know which mode you are in.

More than one session

Turn on the orchestration profile, with one field. A unit of work then runs as a few sessions with fixed roles: a Builder, a Gatekeeper who re-runs every check, an Advisor. They share one ledger in your repository. A fuller mode adds a Supervisor and a Registrar. For a longer piece of work there are templates for a charter, a premortem and a retrospective. See it running shows the ledger.

Builder · phase 1 ready for its check Gatekeeper · checks pass Advisor · next: deliver

one shared ledger · git-stamped rows · read at step boundaries · nothing polls

What it costs to try, and to leave

dev-rigour-min sends nothing: what it reads and records stays on your machine, and nothing is pushed to a remote until you turn that on. It is open source, under the Apache-2.0 licence. It needs Node.js and nothing else: no packages are installed and nothing is compiled.

The same script installs it, updates it and removes it. Removing it takes out everything it wrote, and keeps your history. A health check, dr doctor, says in one line per check whether the install is sound.

Yours to switch off

You can pause every guard with one command in your own terminal. The agent cannot do that for you, and it cannot remove the guards either.

Carries forward: the two promises from slide 05 and the judgment rules from slide 02.