buildlisted

This skill is the **build** orchestrator. It takes the design produced by `/design` and turns it into working code. Two phases, with a go/no-go between them unless the caller says to run them all. The three-part pipeline: - `/design` — produces `.design/YYYY-MM-DD-<slug>.md`. - `/build` — this skill. Reads it, writes the code. - `/review` — reviews the code against it. ## Prerequisite `.design/YYYY-MM-DD-<slug>.md` with at minimum `## Problem`, `## Solution` and `## Tasks` filled is what this skill is built for. **No design file: ask, then do what they say.** Do not decide this on your own, in either direction — not by refusing, and not by judging the change small enough to wave through. The user knows whether this needs a plan; you are guessing. State what you would build and ask one question: > No design file here. Build the token change directly, without a plan? Or run `/design` first to settle it properly. > > Building direct: no task list, no recorded decisions, and `/review` will have nothing to check the result against. Then: - **They say build** — build it. That is the answer, whatever the size. Say in one line what you are building, load the [House Conventions](#house-conventions), do the work, run the tests. Skip the `## Implementation` bookkeeping: there is no design file to record against, and the diff plus the commit message carry it. - **They say design** — hand off to `/design` and stop. Ask once. Do not re-raise it later in the same build, and do not