VibeWise
A plugin for Claude Code (and Codex) that flips the balance: you build, the AI writes. Before a single line of code it asks for your approach, then walks you through three checkpoints: a build checkpoint (you reason with the AI), a design checkpoint (you validate the design, which records it without writing code) and an implementation checkpoint (you review the exact changes, your approval authorizes the writing). Afterwards it explains what changed, why, and which tests ran. It adapts the depth of explanation to your level (beginner, intermediate, advanced) and keeps its settings, notes and project map in a `.vibe-wise/` folder. What it changes in practice, seen in [Instagram reel DePeM6Mxobz](https://www.instagram.com/reel/DePeM6Mxobz/): for a prospect-tracking tool, it asks two questions before talking tech. When I click 'follow up', does the tool send the email by itself or prepare a draft? And ten days later, counted from what, the first message or the first follow-up, and what does the prospect become after the second follow-up? The author had written a single follow-up date while following up twice. Claude in normal mode would have chosen for them, silently, and the gap would have shown three weeks later, when the tool displays nonsense.
Strengths
- Surfaces silent decisions: a rule the model would have chosen alone becomes a question asked before writing
- Three distinct checkpoints (build, design, implement): you validate the design before anything is written, then the exact changes before writing
- Adapts the explanation to your level and can reduce checkpoints or pause the learning
- Free, MIT licence, installable from the plugin directory or from GitHub
Limitations
- Slower by design: every checkpoint waits for your answer, a poor fit for a three-line fix
- Needs Python 3 on top of Claude Code, and creates a `.vibe-wise/` folder to keep out of git
- What the video shows is one case, not a measurement: nothing establishes that the questions asked cover every gap in a spec
Best for
- Anyone building a first tool with Claude Code who wants to understand what the model decides for them
- Juniors and product profiles who want to learn a stack while the AI writes the code
- Tools with states and dates (follow-ups, subscriptions, workflows) where a forgotten rule only shows weeks later