The pipeline

Six fixed stations, one work item. Drag the scrubber to move it down the line and watch each station stamp its artifact on.

gather contextplanbuildreviewtestship

Stamped so far

The problem this replaces

Same six things, no fixed order

Everyone touches the same six things — but in a different order, on a different day, with no way to point at where the ticket actually is.

How it works

Review has no code to review until Build's exact artifact exists. The order isn't a suggestion — it's a dependency.

That's why the scrubber above only moves forward through stations in order — there's no "review" artifact to jump to before "build" has produced one.

See it in action

"add customer export" → context package → plan approved → branch + commits → review passed → tests passing → PR opened

Same six stamps, every time — whichever developer runs the command.

So what

One command puts your ticket on this line — and you can always point at exactly where it is.