VibeFlow OS
Spec-driven development plugin for Claude Code, published by picmakpro and Samuel Neveu. You describe what you want in plain language, the `vibeflow-head` agent reads the intent and starts a team of agents that challenges the request, writes the spec, plans with tests first, builds in atomic commits, then has the work reviewed by a judge that did not write it. Each step leaves a file on disk (`PROJECT.md`, `ROADMAP.md`, `STATE.md`), so a session can stop without the project going backwards. It is not a planning engine of its own: the dev cycle relies on GSD Core for phases and plans, and on Superpowers for TDD and debugging, which VibeFlow calls for you. The repo doubles as a marketplace and ships 19 modules, including the `conductor` base, dev and design labs, and business teams (content, growth, business). It also runs on Codex and kimi-code, without the hooks.
Strengths
- The judge that signs off is never the agent that wrote the code, and tests are written red before the fix
- Project state lives in files on disk, not in the session context
- No plugin-level hooks: module hooks are only set by `/vibeflow-install`, which lists every write before making it
Limitations
- Proprietary licence: use reserved for VibeFlow course students, redistribution and resale forbidden
- Depends on GSD Core and Superpowers: three layers to understand when a behaviour goes wrong
- Requires bash, `jq` 1.6 or later and `python3`; on Windows you need Git Bash and `winget install jqlang.jq`
- Ambiguous name: the `@magicpro97/vibeflow` npm package and the oai-labs `vibe-flow` plugin are unrelated projects
Best for
- VibeFlow course student who wants the full cycle in Claude Code without learning the GSD commands
- Studying how check scripts and a separate judge stop an agent from declaring "done" without proof