Why Your Vibe-Coded App Keeps Breaking: Skip Spec → Decompose → Build in Parts (ex-Shopify)

Exact instruction

Spec in Claude Desktop with Opus 4.8 — multi-markdown files covering each feature, edge cases, data flow, UI/UX.
Hook Claude Code to GitHub, convert spec to Epic → Issues → Sub-Issues.
Build issue by issue — review and sign off before moving to next. Kill problems before they snowball.
Bonus: use powerful model (Opus) for planning only; use lighter model for the actual code execution.
Comment 'Claude Code' on the original post for the one-pager.

Suggested prompt

For this planning session, we're using you to think through the full technical spec — edge cases, data flow, architecture. Don't write any code yet. Once we've agreed on the spec, we'll hand it to a lighter model to implement issue by issue.

Adopt?

Yes: The model selection tip is the new insight vs. his other video — use Opus for planning (where reasoning matters most) and a lighter model for code execution (where the spec already constrains the task). This saves significant cost without quality loss.

Find the resource

Comment 'Claude Code' on the original post (@nelsontalksmoney) for the one-page spec-to-GitHub-issues setup guide. Also see his other video (row 60) for the same workflow with additional detail.

show original caption

Your vibe coded app isn't breaking because you aren't using Fable 5 or GPT-5.5 High Thinking, it's because you're missing this one step. Comment "Claude Code" for my one pager. #claude #claudecode #vibecoding #saas