The build cycle — Throughliner

In Throughliner, we consider the "build cycle" as roughly equating to one use of /plan, /next, and /done in roughly that order.

Four slash commands drive the workflow:

/setup — asks a short questionnaire about your project and scaffolds everything. This is only run once at project setup time.
/plan — organise the queue, capture ideas, resolve design questions. But you can "capture" ideas at literally any time in the build cycle and they will be appended to QUEUE under unprocessed.
/next — Claude builds the next piece of ready work, scope-locked so Claude stays focused. It can build several pieces of cleared work back-to-back without you confirming each one.
/done — Claude records what happened, commits.

Use them like this:

Run /setup once, when you first set up a project. After that you work in sessions, and every session ends the same way: /done to record what happened, then /clear or open a new chat to start fresh.

/plan — think and organise: manage the queue, add ideas, resolve questions. Run it as often as planning needs; a long planning stretch is just /plan → /done → /clear, repeated.
/next — build: it picks the top piece of ready work and builds it. You'll run /next many times, working down the queue. When several pieces are cleared, one /next can build them back-to-back without you confirming each one.