hyperbuild-reviselisted

Change something BEFORE the build starts. Invoked directly by the user as /hyperbuild-revise <plain-English change> on a run parked at the Stage-A design gate (step 12, blocked_on: "design-choice"). Classifies the request into a revision scope — idea | feature | design | epics — states the resolved plan and blast radius, then applies it: idea → a dated "## Revisions" entry appended to runs/<run_tag>/idea.md (the verbatim idea is never rewritten) plus re-runs of steps 4/4.5 and everything downstream that depends on them; feature → surgical edits to features/*.md + 00-index.md then scoped re-runs of 8/11; design → a scoped re-run of one direction's system author + mockup smiths + screenshots + 8.5 visual QA (new DIRECTIONS go to /hyperbuild-redesign instead); epics → a re-run of step 11 under the stated constraint. Always ends by re-running the step-12 gate so the run parks cleanly again, and records every revision in runs/<run_tag>/decisions/revisions.md. Does NO build work and never touches app/.
zakariaf/hyperbuild · ★ 0 · Web & Frontend · score 72

Install: claude install-skill zakariaf/hyperbuild

# /hyperbuild-revise — change the plan before it becomes an app You are executing a pre-build revision of a hyperbuild run. Step 12 parked the run at the design gate; the user wants something CHANGED rather than accepted. Your job: classify the change, state its blast radius, apply it to the artifacts that own the change, re-run exactly the steps that depend on them, and park the run at the gate again with an honest summary. **THIS SKILL DOES NO BUILD WORK AND NEVER TOUCHES `app/`.** It also does no step work by hand: every re-run goes through the owning step skill (see *Scoped re-run mechanics*). If you find yourself writing a design system, authoring mockups, drafting task files, or scaffolding a project directly from this seat, STOP — you are inside the wrong skill. ## When NOT to use this skill - **After `/hyperbuild-choose` released Stage B.** Once the manifest reads `stage: "BUILD"` (or `"DONE"`), `app/` exists and is built against a chosen design; changes belong to step 15's structural-findings path — critics' structural findings become NEW TASKS and loop back through step 14 once (see `hyperbuild-15-adversarial-review`). **You may not start this skill on a `BUILD`/`DONE` run unless the user explicitly confirms it in reply to your warning** (procedure step 1). "They typed the command" is NOT confirmation. - **Mid-run.** If Stage A is still executing (some step between 1 and 11 is `running`), STOP and say: let `/hyperbuild` finish and park at the gate,