super-board README

The project's README from github.com/EricTechPro/super-board. As one markdown file: README.md.

super-board kanban logo

super-board

Add tasks, walk away, get merged PRs with proof.

8 skills (5 you type, 3 the board runs) · 9 commands · 6 guard hooks

Version Host License

🌐 Live site: erictechpro.github.io/super-board

Install · Quick start · How it works · Skills · Commands · Guards

The super-board skill map: open the interactive version

The skill map. Click it for the live version: zoom, pan, open any node.

Install

In your project folder:

curl -fsSL https://raw.githubusercontent.com/EricTechPro/super-board/main/get.sh | bash

Or as a Claude Code plugin:

/plugin marketplace add EricTechPro/super-board
/plugin install super-board@super-board

[!NOTE] The plugin ships the skills only. Run /super-board:super-board onboard and its 🔍 Checks step adds the guard hooks, scripts and workflows. Needs Claude Code, gh, jq, bash 3.2+ and Python 3.9+; the installer checks.

Optional post-run learning can delegate an already installed calibrate skill after verified selected work completes. It applies only to explicitly permitted existing canonical skill files; the package bundles no private skill. See post-run calibration.

Quick start

1. Install

curl -fsSL https://raw.githubusercontent.com/EricTechPro/super-board/main/get.sh | bash

2. Onboard

/super-board onboard

Checks · GitHub · Board · Branch · AGENTS.md · Policies · Bug sources · Review. Enter takes the recommended answer.

3. Run

/super-board run my-app

Add cards to Ready. The board drains on its own.

How it works

Watch I Built a Self-Improving Software Factory by Eric Tech on YouTube

▶ Watch on YouTube: I Built a Self-Improving Software Factory

Skills

8 skills (5 you type, 3 the board runs). Uses Matt Pocock skills, ponytail, impeccable and humanizer.

You type — 5 skills

Skill What it does
/super-board Orchestrator: plans waves, runs Build → QA → Review, merges when green.
/super-collect Finds problems (Sentry, PostHog, issues, PRs, architecture) and files verified Backlog cards.
/ui-refine-loop Critique → refine loop that polishes one page or component.
/visual One HTML page: branch recap, plan, or codebase map with diagrams.
/git-sync Commit per logical change, merge-pull, push without force, report.

The board runs — 3 lanes

Skill What it does
/super-build Builder lane: worktree, smallest safe change, tests, draft PR.
/super-qa Tester lane: evidence, test-gap check, screenshots, or bounce to Build.
/super-review Reviewer lane: own hypotheses, remembers prior findings, merge gate.

Each name links to that skill's README. Adding a skill? Write its SKILL.md and README.md, add a line to skills/families.json, and this table updates itself.

Commands

/super-board onboard          # 8-step setup, resumes
/super-board lint             # vague ACs?
/super-board status           # read-only snapshot
/super-board run <slug>       # drain the board
/super-board stop             # stop workers
/super-collect [source]       # file problems to Backlog
/ui-refine-loop <route>       # polish one page
/visual [recap|plan|path]     # one HTML page
/git-sync                     # commit, pull, push

Flags: run --low|--high · run --codex[=<model>] · super-collect --since 30d

Guards & hooks

Run automatically once installed. Python stdlib, JSON in, JSON out.
guard-worktree-path Blocks git worktree add outside .claude/worktrees/
guard-secrets Blocks reading or piping dotenv files, SSH keys and credential files; key names via super-board-env-check.sh
guard-key-literals Blocks a live-looking API key written into a file; flags one already there
guard-delete-outside Blocks rm, find -delete and git clean aimed outside the project, ~ or /
guard-protected-push Opt-in (onboard asks, or install.sh --protect-main): blocks direct and force pushes to main/master/base
README sync Regenerates the skill table; pre-commit and PostToolUse hooks keep it fresh
cleanup-wt Removes merged worktrees and branches after each merge and at session start, with a recovery file
merge gate Merges only after the current base plus your non-empty project verify_commands pass (missing checks halt setup), pinned to the reviewed commit; applies merge_policy and runs allowed DB migrations

Models

A cheap router grades each card easy, medium or hard first; the run flag picks the model for each grade. With --codex, every lane runs on Codex GPT models instead of Claude.

Command Router Easy card Medium card Hard card
/super-board run Haiku 4.5 Sonnet 5.5 Opus 5.5 session model
/super-board run --low Haiku 4.5 Haiku 4.5 Sonnet 5.5 Opus 5.5
/super-board run --high Sonnet 5.5 Opus 5.5 Opus 5.5 Opus 5.5
/super-board run --codex gpt-6-luna gpt-6.1-sol gpt-6.1-sol gpt-6-astra
/super-board run --codex --low gpt-6-luna gpt-6-luna gpt-6.1-sol gpt-6.1-sol
/super-board run --codex --high gpt-6-luna gpt-6-astra gpt-6-astra gpt-6-astra

/super-board run --codex=<model> pins one model for every card and skips the router.

Run inside Codex? plain /super-board run switches to the Codex ladder by itself. Codex has no /super-board command: it finds skills in .agents/skills/ (symlinks followed), so link .claude/skills/super-board there and type $super-board run.

Writing standard

Commits, tickets, PR bodies and comments all follow one writing standard, in the pack and in every project it is installed into.

Upgrading from 2.x
  1. Re-run the install line.
  2. Run /super-board onboard; step 1 upgrades for you and keeps a backup.
  3. Try board-migrate --dry-run on a copy of your board first.

Full notes

Credits

MIT © Eric Tech (LICENSE). Built on obra/superpowers, mattpocock/skills, BuilderIO/skills and tt-a1i/archify.

Live site · Skill map · Writing standard · Setup simulator · Impeccable map · pstack map · Release notes · Release checks · YouTube walkthrough

Made by Eric Tech

Worker skill availability

Setup and dispatch resolve real, nonempty SKILL.md files for the actual Claude or Codex host. Missing required skills halt before claims or workers; lockfiles and arbitrary plugin caches do not count. The shared registry in scripts/super-board-skills-ready.py owns lane dependencies, overrides and the two declared ponytail fallbacks. Setup's full helper union may be red while a selected card is runnable. Read-only checks never install; explicit onboard repair rechecks files after installation.

The CLI accepts --home <fixture-home> and --catalog <active-skills.json>. Launchers accept the same inventory through SUPER_BOARD_SKILLS_HOME and SUPER_BOARD_SKILLS_CATALOG; neither changes the actual host. Catalog shape: {"host":"codex","skills":[{"name":"vendor:skill","path":"/exact/SKILL.md", "enabled":true,"scope":"project","project_root":"/exact/project"}]}. User entries use scope:"user". Restart explicitly after repairing missing skills; readiness certifies availability, not their content or external tools.

super-board (EricTechPro/super-board)

agentic-coding
Searching Database…

402 ·GitHub
Super-board
What is this?super-board is an autonomous Build → QA → Review loop for Claude Code: you drop cards into a Ready column and the system plans the work, codes it, tests it, reviews it, and merges the PR once everything passes.
Is this a standalone app, or does it run inside Claude Code?It is a Claude Code skill/plugin pack, not a separate application: it adds 8 skills (5 you type, 3 the board runs automatically), 9 slash commands, and 6 guard hooks to your existing project.
How do I get it running on a project?Run the one-line installer in your project folder (or install it as a Claude Code plugin), then run the onboard command to configure checks, GitHub, branch policy and bug sources. After that, just add cards to the Ready column and the board works through them on its own.
What do I need installed before setting this up?You need Claude Code itself, plus the gh CLI, jq, bash 3.2+ and Python 3.9+; the installer checks for these automatically.
Does the plugin install everything I need right away?No — the Claude Code plugin install only brings the skills themselves. You still have to run the onboard command, whose Checks step adds the guard hooks, scripts and workflows that actually enforce safety rules.
What do the guard hooks actually block?They stop risky actions automatically: creating worktrees outside the allowed folder, reading or piping secrets like dotenv files and SSH keys, writing a live-looking API key into a file, deleting things outside the project, and force-pushing to main unless you opted in.
How does it decide which AI model to use for a task?A cheap router first grades each card as easy, medium or hard, then the run flag you chose (default, --low or --high) maps that grade to a specific Claude model, from Haiku up to Opus.
Can I use Codex/GPT models instead of Claude?Yes — passing --codex switches every lane (Build, QA, Review) to GPT models via the same router logic, and since Codex has no native /super-board command, it finds the skills through symlinks in .agents/skills/.
What happens if I'm upgrading from an older version?Re-run the install line, then run the onboard command, which upgrades your setup and keeps a backup; it's recommended to test board-migrate --dry-run on a copy of your board first.
What are similar projects?Archon, agent-orchestrator, orca, agor, 1code, shipyard, swarm-forge, emdash
Which topics is it in?workflow-engine, coding-assistant, kanban, git-worktrees, project-management, agentic-coding, bash, code-review, playwright, agent-framework, claude-skills, github
Creator
EricTechPro
Size
6.5 MB
Stars
402
Updated
CommitOct 19Releasev3.1.2Oct 12
Age
4mo
Commits · 90 Days