buildlisted

This skill is the **build** orchestrator. It takes the design docs produced by `/design` and turns them into working code. Two phases, both gated. The three-part pipeline: - `/design` — produces docs in `.design/<slug>/`. - `/build` — this skill. Reads those docs, writes the code. - `/review` — reviews the code against the docs. ## Prerequisite `.design/<slug>/` must exist with at minimum `DESIGN_BRIEF.md`. If it doesn't, stop and tell the user to run `/design` first. This skill needs a brief, tasks, and (optionally) a backend brief + tokens spec — not a vibe. ## The Sequence ``` 1. Frontend Build → materialize tokens spec + implement frontend from TASKS.md 2. Backend Build → implement server from BACKEND_DESIGN.md ``` Skip either phase if the design didn't include it (e.g. no `BACKEND_DESIGN.md` → skip phase 2). ## Operating Rules 1. **Open with a scan.** Ask which feature slug to build (or infer from a single existing `.design/*/` folder). List the artifacts present in `.design/<slug>/` so the user sees exactly what's going to drive the build. Ask which phases to run. 2. **Announce each phase before entering it.** Format: "Phase N: [name]. This will [what it does]. Ready?" Wait for confirmation. 3. **Run each phase by reading its SKILL.md and following it in full.** Do not paraphrase. 4. **Thread the design docs into each phase.** Explicitly hand file paths so the sub-skill doesn't hunt for context. 5. **End each phase with a checkpoint.** Summarize files crea