make-setup-wizard

Copy the provided template.sh, set TOTAL_STAGES and TOTAL_MINUTES, then author one stage() per step using helpers like open_url, ask, ask_secret, write_env, and confirm. The library above the STAGES marker handles progress display, hidden input, and .env upserts and should never be edited.

Use the write_env helper, which performs an idempotent upsert: it removes any existing line for the key and appends the new KEY=VALUE pair. On re-runs, ask and ask_secret offer the existing .env value as a default so Enter keeps it.

Only when the repository's .github/workflows files actually reference secrets.* or vars.* values. The default target is a local .env file; set_secret and set_var are used solely for values CI consumes, and they degrade to a skipped note if gh is unavailable.

Gate action-only steps behind a confirm loop, such as `until confirm "Did the SQL run without errors?"; do warn ...; done`. The wizard cannot advance to the next stage until the human confirms, which prevents silent skips that a flat README checklist invites.

No, running it end to end is an anti-pattern because it opens browsers and blocks on human input. Verify statically with bash -n and shellcheck, then trace that every captured value lands in its intended destination and every set_secret name matches a CI reference.

Do not use it when a dedicated skill already owns the procedure, when the steps are not yet verified (research them first), or when the next person needs prose context rather than an executable runbook. Wizards consume verified steps; they never invent UI paths or commands.