hyperbuild-12-design-gatelisted

Step 12 of the hyperbuild pipeline — the Stage-A hard gate and THE ONE permitted stop. Spawns 1 hb-gate-verifier to mechanically run the full Stage-A checklist (research vault, PRD, feature specs, stack guide, 3 complete design systems with every full/partial screen mocked + screenshotted and art-direction cards for none screens, step 8.5's visual-QA findings with zero unresolved criticals, generated skills, full backlog with PRD↔epics coverage, and the research archive's shape: the four FIXED-name areas, a non-empty verify/ in each, provenance blocks everywhere), writes runs/<run_tag>/gates/design-gate-report.md and — on pass — research/README.md (the areas index + REUSABILITY GUIDE, docs/RESEARCH-ARCHIVE.md §8), then stops the pipeline with a user-facing summary ending in "run /hyperbuild-choose a|b|c", setting manifest blocked_on: "design-choice". On fail: fix artifacts, re-run the gate, max 3 rounds, then blocked + honest report. Invoked by the hyperbuild router via Skill(); not run directly by users.
zakariaf/hyperbuild · ★ 0 · Web & Frontend · score 72

Install: claude install-skill zakariaf/hyperbuild

# Step 12 — Design gate (Stage-A hard gate + THE ONE PERMITTED STOP) **⚠ READ FIRST — the two ways to violate this step.** (1) This is the ONLY point in the entire pipeline where you intentionally end the turn with a bare-text, user-facing message. Everywhere else bare text kills the run; HERE the stop IS the deliverable. (2) The inverse: **if the gate passes, do NOT invoke `Skill(skill: "hyperbuild-13-scaffold")`.** Stage B starts only when the user runs `/hyperbuild-choose <a|b|c>`. If you find yourself about to continue into Stage B after a pass, STOP. Set the manifest, emit the stop message, end the turn. You are executing step 12 (design gate) of the hyperbuild pipeline. Steps 1–11 claim Stage A is complete; this step proves it against artifacts on disk, then hands the user the one decision the pipeline cannot make: which design to build. **Goal:** a passing `runs/<run_tag>/gates/design-gate-report.md` and a final user-facing summary ending with `run /hyperbuild-choose a|b|c` — or, after 3 failed fix rounds, an honest blocked report. Gate failures are fixed by changing the artifacts, NEVER by re-interpreting the checks. --- ## Inputs - `runs/<run_tag>/manifest.json` — `run_tag`, `gear`, `platform`; steps 1–11 (including 3.5, 4.5, 8.5) must read `done`; `screenshots_skipped` (when `true`, checks 19 and 20 downgrade to WARNINGs); `visual_qa_skipped` (same effect on check 20) - `runs/<run_tag>/idea.md` — verbatim idea. GOSPEL. - `research/product-spec.md` — the canoni