viban
Visual Kanban — Issue tracking designed for AI agents.
Register bugs. Claude picks them up, resolves them, and creates PRs — while you keep finding the next issue.
# You find a bug and register it
/viban:add "Login fails after password reset"
# Claude assigns itself the top-priority issue and starts working
/viban:assign
# Or resolve 3 issues in parallel — each in its own git worktree
/viban:parallel-assign 3
Why viban?
GitHub Issues, Linear, and Jira are built for humans coordinating with humans. viban is built for humans coordinating with AI agents.
| Traditional trackers | viban |
|---|
| Who resolves issues? | Human developers | AI agents (Claude Code) |
| Parallel work | Manual branch management | Isolated worktrees, zero conflicts |
| Where it lives | External SaaS | Your repo (single JSON file) |
| Setup | Accounts, permissions, integrations | npm install -g claude-plugin-viban |
| Context switching | Browser ↔ terminal | Everything in terminal |
| Already using GitHub Issues? | — | Two-way sync included |
Quick Start
For Claude Code Users
/install claude-plugin-viban
/viban:setup
For Terminal Users
npm install -g claude-plugin-viban
Then start tracking:
viban add "Fix login error" "Users cannot login after password reset" P1 bug
viban add "Add dark mode" P2 feat
viban # Open TUI board
How It Works
Sequential Mode
Run multiple terminal sessions — one for QA, one for resolution, one for monitoring:
┌───────────────────┐ ┌───────────────────┐ ┌───────────────────┐
│ Session 1 │ │ Session 2 │ │ Session 3 │
│ │ │ │ │ │
│ Product QA │ │ Issue Work │ │ viban TUI │
│ + /viban:add │ │ + /viban:assign │ │ │
│ │ │ │ │ (always open) │
│ Find bugs, │ │ Pick & resolve │ │ Monitor board │
│ register issues │ │ issues │ │ in real-time │
└───────────────────┘ └───────────────────┘ └───────────────────┘
Parallel Mode
Resolve multiple issues at once with /viban:parallel-assign:
┌───────────────────┐
│ Coordinator │ /viban:parallel-assign 3
│ │
│ Assigns issues, │──┬──────────────────────────────────────┐
│ creates worktrees│ │ │
│ collects results │ ▼ ▼ ▼
│ │ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ │ │ Agent 1 │ │ Agent 2 │ │ Agent 3 │
│ │ │ wt/#12 │ │ wt/#13 │ │ wt/#14 │
│ │ │ Analyze │ │ Analyze │ │ Analyze │
│ │ │ Implement│ │ Implement│ │ Implement│
│ │ │ Commit │ │ Commit │ │ Commit │
│ Push, create PRs │ └──────────┘ └──────────┘ └──────────┘
│ Run tests, report│
└───────────────────┘
- Each agent works in an isolated git worktree (
.viban/worktrees/{ID})
- Zero interference between agents — no merge conflicts
- Coordinator pushes branches, creates PRs, and runs tests after all agents finish
Claude Code Skills
These are the core AI-agent commands. Each one is a Claude Code slash command.
/viban:add — Register an issue
Analyzes your description and creates a structured issue with proper priority, type, and description.
/viban:add "Search is broken on mobile"
→ Infers: P1 bug, enriches description, registers to backlog
/viban:assign — Assign and resolve
Picks the highest-priority unblocked backlog issue, assigns it, and follows your project's workflow to resolve it.
/viban:assign
→ Picks #7 (P0 bug), analyzes code, implements fix, creates PR
/viban:parallel-assign — Parallel resolution
Assigns N issues (default 3, max 5) and spawns one agent per issue in isolated git worktrees.
/viban:parallel-assign 3
→ Assigns #8, #9, #10 — three agents work simultaneously
→ Each commits on its own branch, coordinator creates PRs
/viban:review — Checkout for IDE review
Checks out the issue branch and soft-resets so all changes appear as staged diffs in your IDE.
/viban:review
→ Finds first review card, checks out branch, staged diffs ready in IDE
/viban:review 12
→ Checks out branch for issue #12
/viban:approve — Approve and merge
