Spec to pull request

The spec says what should be true. Turning it into reviewed, tested code still takes a dozen handoffs between people and tools.

How it runs

A product spec becomes a merge-ready change.

The spec is broken into tasks against your codebase, your Catalogue, and the decisions already made on similar work.

Where it stops

A person decides scope, accepts the risk, and merges. You choose how much of the loop runs before it stops.

What the next run learns

Every review round and decision feeds the next spec, so the loop gets shorter and cheaper.

Run it on your own agents.

Start from a starter or build it your way, with the gates and limits you choose.