super-boardlisted

# super-board — autonomous GitHub Project pipeline Spec: `docs/superpowers/specs/2026-05-21-super-board-design.md` ## Five verbs | Verb | Where | What it does | |---|---|---| | `super-board onboard` | interactive | one-time setup wizard; writes `.claude/super-board/configs/<slug>.json` | | `super-board lint` | interactive | walks active-pipeline issues, flags vague ACs, runs pre-flight readiness | | `super-board status` | interactive (read-only) | snapshot of active config, column counts, in-flight workers | | `super-board run` | headless | the autonomous loop; spawned via `scripts/super-board-run.sh`. Also the resume command — state lives on the board, not in process memory. Accepts a model-tier flag: `--low` (haiku/sonnet/opus ladder), default = medium (sonnet/opus/session), `--high` (opus/session — strongest models only). | | `super-board stop` | interactive | graceful shutdown: posts "stopped mid-flight" comments on every in-flight issue + PR, releases assignee mutexes, kills workers + dispatcher. Next `super-board run` resumes. | If invoked with no verb, ask which (see no-verb behavior in spec §8). ## Routing | If user says | Load | |---|---| | `super-board onboard ...` | `references/onboard.md` | | `super-board lint ...` | `references/lint.md` | | `super-board status ...` | `references/status.md` | | `super-board run ...` (default — `worker_backend` unset or `"workflow"`) | `references/run-workflow.md` (lane lifecycles still come from `references/run.md`) | | `sup