claude-vibekanban-plugin

claude-vibekanban-plugin

Claude Code plugin for VibeKanban workflow automation. Plan, track, and execute development tasks through VK integration.

Credits

Based on the original claude-vibekanban commands by Eric Blue. The original project provides a set of .claude/commands/ files (v0.3.1-preview) for workflow automation.

What changed from the original

Structural

• Restructured from .claude/commands/*.md files to a Claude Code plugin with namespaced skills (/vk:*)

Command consolidation (18 → 12 commands)

• /vk:work — unified command replacing work-task, work-next, delegate-task, work-parallel, and delegate-parallel. Delegates to VK workspaces, handles single or parallel execution. Discovers parallel opportunities automatically.
• /vk:plan-status — now includes ranked top-3 task recommendations (absorbed next-task).
• /vk:session-status — task status snapshot from VK issue states.
• /vk:work-loop — new command adapted from the original's work-parallel-loop. Autonomous wave-based execution scoped to an epic, tag, or all tasks.
• Removed next-task, work-task, work-next, delegate-task, delegate-parallel, merge-parallel, work-parallel, merge. Local execution (--local) removed — all work delegates to VK workspaces.

Standardization

• Fixed VK MCP tool names from task-based to issue-based (list_tasks → list_issues, get_task → get_issue, etc.)
• Updated all internal cross-references to use /vk: namespace

Process improvements

• Added /vk:archive-epic command — archives all completed epics by default, keeps active plan under ~300 lines
• Extracted changelog to dedicated docs/development-plan-changelog.md — updated sync-plan, create-plan, add-epic, close-epic, archive-epic to write to the separate file instead of inline
• Protected epic-level acceptance criteria from auto-checking — only individual task criteria get checked off during execution; epic criteria are verified holistically via /vk:close-epic
• Improved sync-plan with drift detection — stale in-progress tasks, dependency violations, blocked-but-ready tasks, scope drift (orphaned/unlinked)
• sync-plan always fetches fresh VK status — never uses cached data from prior steps
• /vk:close-epic handles partial completion — explicit branches for full close, move tasks, descope, or mark as partial

Commands

All commands are namespaced under /vk:.

Planning

Command	Description
/vk:generate-prd	Generate a PRD from a project idea through guided interview
/vk:prd-review	Analyze an existing PRD, identify gaps, suggest epic breakdown
/vk:create-plan	Generate a development plan with epics, tasks, dependencies, and acceptance criteria
/vk:generate-tasks	Create VibeKanban issues from the development plan and link them

Execution

Command	Description
/vk:work	Delegate tasks to VK workspaces — single or parallel. No args = best next task, discovers parallel opportunities automatically.
/vk:work-loop	Autonomous wave-based loop — work through an epic, tag, or all tasks with delegate-poll-sync cycles

Plan Management

Command	Description
/vk:sync-plan	Sync plan with VK status, detect drift
/vk:plan-status	Show progress summary with task recommendations (read-only)
/vk:add-epic	Add a new epic to the development plan
/vk:close-epic	Mark an epic as complete
/vk:archive-epic	Move completed epics to archive

Monitoring & Reference

Command	Description
/vk:session-status	Show task status snapshot from VK issue states
/vk:workflow	Show command reference

Prerequisites

• VibeKanban MCP server enabled in Claude Code
• A VK project with a linked repository

Enable the MCP server

Add the following to your Claude Code MCP settings:

{
  "mcpServers": {
    "vibe_kanban": {
      "command": "npx",
      "args": ["-y", "vibe-kanban@latest", "--mcp"]
    }
  }
}

Installation

claude plugin marketplace add materemias/claude-vibekanban-plugin
claude plugin install vk@claude-vibekanban-plugin

Typical Flow

/vk:generate-prd → /vk:prd-review → /vk:create-plan → /vk:generate-tasks → /vk:work (repeat) → /vk:sync-plan

Quick start: Have a PRD? Start at /vk:prd-review. Have a plan? Start at /vk:generate-tasks. Just want to code? Run /vk:work.