Skip to main content

00— Plugin for Claude Code · v0.2.4

vibe-flowSpec to merged code.

Spec to merged code. Multi-agent orchestration for Claude Code. A pipeline of specialist skills that plan, dispatch, link, review, and merge — with verification gates at every step.

Install →Read the docs
01plan→
02ship→
03link→
04review→
05merge
01

What it is

A plugin for Claude Code. Ten coordinated skills that turn a spec into merged code.

You hand it a spec. It decomposes into atomic issues on your vibe-kanban board, assigns a complexity tier, dispatches workspaces in parallel waves, opens PRs, runs a two-stage review with an isolated subagent, merges clean, and posts a standup. When a run hits a CI failure or a conflict, it routes to the fix or rebase sub-skill and loops — with an escalation ceiling so it can’t thrash forever.

Every transition is gated. Nothing ships without a fresh verification.

02

Skills

Each one is a skill you can invoke directly. Or let the meta skill run the full loop.

/vibe-flow:vibe-initFirst-time setup. Pick project, scaffold config + state.→/vibe-flow:vibe-planSpec → issue tree. Epic, stories, dependencies, tiers.→/vibe-flow:vibe-shipWave-based parallel dispatch with executor routing.→/vibe-flow:vibe-linkWorkspace branch → GitHub PR. Move issue to in_review.→/vibe-flow:vibe-reviewTwo-stage review by fresh subagent. Post to PR.→/vibe-flow:vibe-mergeVerify gates, squash, close loop, archive workspace.→/vibe-flow:vibe-dispatch-fixRe-dispatch on review critical or CI failure.→/vibe-flow:vibe-rebaseResolve conflicts against main. Force-with-lease.→/vibe-flow:vibe-statusSnapshot of active workspaces, PRs, inconsistencies.→/vibe-flow:vibe-standupPeriodic summary in slack/discord/markdown.→/vibe-flow:vibe-flowMeta: plan → ship → review → merge → standup.→
03

Executor routing

Five tiers. The cheapest model that can do the job, and no cheaper.

TierExecutorWhen
T0Gemini flashTypo, copy, trivial CSS
T1Codex mini / Sonnet mediumSimple CRUD, <150 LoC
T2Sonnet highMulti-file, moderate
T3OpusArchitecture, migration
T4Opus + brainstormResearch, RFC
04

Install

One command to add the marketplace, one to install, one to init.

# In Claude Code:
/plugin marketplace add OAI-Labs/vibe-flow
/plugin install vibe-flow@vibe-flow

# Then, in your repo:
/vibe-flow:vibe-init

Requires the vibe-kanban MCP server. See installation for wiring.

05

Philosophy

Why it’s shaped this way.

  • Verify fresh, always.No hope-based merges. Every gate re-checked before it lets code through.
  • Humans pick scope.Plan approval, tier overrides, cost budget — human owns the contract.
  • Agents do the work.Parallel waves, strict isolation, bounded escalation. The graph stays tight.
  • State is the source of truth.state.json + vibe-kanban board mirror reality. No guessing.
  • Ship small, ship often.Atomic issues, one-PR-per-issue, squash merge. No epics that never land.
— fin —