Vibe Coding is a System Design Interview

I've been working on some fairly large vibe-coded apps (like Lion Reader ), and my process has converged on: Write a GitHub issue (If complicated enough) tell an agent to make a plan and then update the issue Have another agent read the issue and implement it As the features get more complicated, I spend more and more time on step (1), and I'm finding that just taking the time to write a detailed…