For folks using Claude Code + Vibe Kanban , I’ve been refining a workflow like this since December, when I first started using VK. It’s essentially a set of slash commands that sit on top of VK’s MCP API to create a more structured, repeatable dev pipeline. High-level flow: PRD review with clarifying questions to tighten scope before building (and optional PRD generation for new projects) Dev plan + task breakdown with dependencies, complexity, and acceptance criteria Bidirectional sync with VK, including drift detection and dependency violations Task execution with full context assembly (PRD + plan + AC + relevant codebase) — either locally or remotely via VK workspace sessions So far I’ve mostly been running this single-task, human-in-the-loop for testing and merges. Lately I’ve been experimenting with parallel execution using multiple sub-agents, git worktrees, and delegated agents (Codex, Cursor, remote Claude, etc.). I’m curious: Does this workflow make sense to others? Is anyone doing something similar? Would a setup like this be useful as a personal or small-team dev workflow? Repo here if you want to poke around: https://github.com/ericblue/claude-vibekanban Would love feedback, criticism, or pointers to related projects. submitted by /u/erictblue
Originally posted by u/erictblue on r/ClaudeCode
You must log in or # to comment.