super-board
/super-board
Prowadzi autonomiczny potok z tablicy GitHub Project: od pustej tablicy do opróżnionej, przez etapy Build, QA, Review i Done.
- Autor
- Shahat87 ↗
- Repozytorium
- ams-mission-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 23
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 04.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prowadzi autonomiczny potok z tablicy GitHub Project: od pustej tablicy do opróżnionej, przez etapy Build, QA, Review i Done.
Wyzwalacze z opisu
Oryginalny opis (EN)
GitHub-Project-driven autonomous pipeline. Five verbs — onboard, lint, status, run, stop — that take a Project board from empty to drained across Build → QA → Review → Done lanes (labels qa · bug · feature route each card), with graceful shutdown / resume. Use when the user says "super-board", "/super-board", "drain my GitHub project", "set up the autonomous loop", "kick off the headless build/QA pipeline", or "stop super-board".
Jak działa
- Five verbs
- Routing
- Orchestrator vs worker — the cardinal rule
Podgląd SKILL.md
--- name: super-board description: GitHub-Project-driven autonomous pipeline. Five verbs — onboard, lint, status, run, stop — that take a Project board from empty to drained across Build → QA → Review → Done lanes (labels qa · bug · feature route each card), with graceful shutdown / resume. Use when the user says "super-board", "/super-board", "drain my GitHub project", "set up the autonomous loop", "kick off the headless build/QA pipeline", or "stop super-board". --- # super-board — autonomous GitHub Project pipeline ## 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` | in-session (default) | the autonomous loop: waves of the `super-board-wave` dynamic workflow, run from this session (`worker_backend: "claude-p"` opts into the legacy headless runner `.claude/bin/super-board-run.sh`). Also the resume command — state lives on the board, not in process memory. Accepts a model-tier flag (`--low`, default medium, `--high`) that picks a per-lane Claude ladder by card complexity: no lane builds on Opus by default, review runs on sonnet, and on opus for high-complexity cards only (sonnet on every card on `--low`), and the operator can pin models per lane via config `pilot.models` (opt-in `pilot.enabled` lets an Opus pilot propose them, bounded by the same rules). `--codex [--low|--high]` overrides the backend for every lane with the matching Codex GPT ladder; `--codex=<model>` or `codex.model` pins one model for every card (see `references/run-workflow.md`). A host with no Workflow tool (a Codex session) runs as `--codex` by itself. | | `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 one. In Codex the skill is not a slash command: it is `$super-board <verb>`, found in `.agents/skills/`. ## 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 --codex[=<model>] ...`, or any `run` from a host with no Workflow tool (overrides any configured backend) | `references/run-workflow.md` → "Codex runs" | | `super-board run ...` (default — `worker_backend` unset or `"workflow"`) | `references/run-workflow.md` (lane lifecycles still come from `references/run.md`) | | `super-board run ...` with config `worker_backend: "claude-p"` (legacy, explicit opt-in) | `references/run.md` | | `super-board run --events` / "event triggers" / "a comment or move should start a lane" / config `events` questions | `references/events.md` (flow: `references/run-workflow.md` → "Event dispatch") | | `super-board stop ...` / "stop the run" / "pause the loop" / "kill super-board" | `references/stop.md` | | "resume" / "pick up where I left off" / "restart after stop" | `references/stop.md` (resume = run; no separate verb) | | Anything about Blocked exits, 🙋 needs you, or dropping a card | `references/block-template.md` | | Optional learning after a successfully completed run | `references/calibration.md` (external installed skill; bounded receipt; explicit existing-skill edit paths) | | Config structure questions | `references/config-schema.json` | | Worker gh-call discipline / rate-limit recovery | `references/rate-limit-etiquette.md` (+ `scripts/super-board-gh-guard.sh`) | ## Orchestrator vs worker — the cardinal rule super-board is an **autonomous trader**. The interactive Claude session that invokes any of the five verbs is an **orchestrator**, not a worker. The orchestrator: - Validates preconditions, then dispatches per the config's `worker_backend`: `"workflow"` (default) → stay in-session and run the wave loop in `references/run-workflow.md` (launch workflow, reconcile, repeat); `"claude-p"` (legacy, explicit opt-in only) → `nohup .claude/bin/super-board-run.sh`, report PID + log path, exit. Explicit `--codex` overrides either backend with headless Codex waves; so does a host with no Workflow tool, or `bash .claude/bin/super-board-host.sh` printing `codex`. The orchestrator never does product work itself. - Delegates all build / QA / review work to workers — headless `claude -p` (claude-p backend), workflow lane agents (workflow backend), or headless `codex exec` (explicit `--codex`). - Must NOT do product work itself, must NOT patch the dispatcher mid-run, must NOT wait for workers, must NOT hold context for multi-card progress. If anything goes wrong during a run, the orchestrator captures the symptom and reports back — it does not silently expand the task into a fix. See `references/run.md` "Orchestrator delegation contract" for the full rule.
Pliki w paczce (23)
- README.md 2 KB
- SKILL.md 5 KB
- VERSION 1 KB
- references/agents-md-block.md 3 KB
- references/block-template.md 12 KB
- references/calibration.md 6 KB
- references/config-schema.json 34 KB
- references/design-preflight.md 3 KB
- references/events.md 8 KB
- references/lint.md 16 KB
- references/onboard.md 38 KB
- references/pr-author-notes.md 5 KB
- references/project-checks.md 1 KB
- references/rate-limit-etiquette.md 6 KB
- references/run-workflow.md 44 KB
- references/run.md 92 KB
- references/second-account.md 5 KB
- references/skills-readiness.md 3 KB
- references/status.md 24 KB
- references/stop.md 8 KB
- references/ticket-format.md 3 KB
- references/watchdog.md 8 KB
- references/writing-standard.md 16 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · Shahat87/ams-mission-kit | 90 | MIT |
| erictechpro/super-board | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki b52cb8d6e7b2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100super-build
Realizuje kartę gotową do pracy z tablicy GitHub w osobnym worktree: zmianę najpierw testowaną, szkic PR i przekazanie do przeglądu. - 100super-build
Buduje zmiany w osobnym worktree dla zgłoszenia w pipeline super-board metodą TDD, otwiera draft PR; scalanie zostawia recenzentowi. - 100super-review
Recenzuje gałąź lub PR przed scaleniem: buduje własne hipotezy, sprawdza dowody w plikach i scala tylko przez bramkę super-board. - 100super-review
Przegląda gałąź lub pull request pod kątem gotowości, formułuje własne hipotezy i sprawdza każdą uwagę z dowodem w konkretnym pliku. - 95debug-board-server
Sprawdza Node.js dla tablicy i debuguje lokalny serwer tablicy: start, status, zatrzymanie i logi przez narzędzia wiersza poleceń. - 87auto-board-task
Przerabia najwyżej położoną kartę Do zrobienia na tablicy GitHub Project: otwiera pull request, synchronizuje go z kartą i stosuje poprawki z recenzji Copilota.