# Super Board

GitHub-Project-driven autonomous pipeline.

- Repository: https://github.com/EricTechPro/super-board (577 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add EricTechPro/super-board --skill super-board -g -a claude-code -y`
Codex: `npx skills add EricTechPro/super-board --skill super-board -g -a codex -y`
Cursor: `npx skills add EricTechPro/super-board --skill super-board -g -a cursor -y`
Gemini CLI: `npx skills add EricTechPro/super-board --skill super-board -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add EricTechPro/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".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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` (haiku/sonnet/opus ladder), default = medium (sonnet/opus/session), `--high` (opus for every card). `--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.

Not sure the board is the right tool? The [routing rule](../../docs/super-board/routing.md) says
which path to take: 1, 5 tickets go to `/implement-spec`; 6+ tickets, or you walk away, go to
super-board.

In Codex the skill is not a slash command: it is `$super-board <verb>`, found in `.agents/skills/`.

## Routing

The rest: https://github.com/EricTechPro/super-board/blob/HEAD/skills/super-board/SKILL.md