Vibe Coding Workflow

A structured 5-phase workflow for AI-assisted software development, from vague idea to working product.

• Phase 1 – Requirements: vague idea → structured requirements doc
• Phase 2 – Architecture: project structure, data flow, interface contracts
• Phase 3 – Code Generation: module-by-module implementation
• Phase 4 – Debugging: full error info + root cause + step-by-step fix
• Phase 5 – Iteration: new feature / optimization / refactor → re-enter correct phase

Global Principles

• You execute, user decides. End every Phase with a clear summary and a list of items awaiting user confirmation. Never auto-advance to the next phase.
• Context is first-class. Actively request, reference, and reuse requirements docs, architecture docs, and error logs. Never guess.
• Preserve artifacts. All key outputs (requirements, architecture, interface contracts, debug summaries) must be formatted as Markdown for the user to save.
• Tool separation. Use conversation for clarification, tech selection, and architecture discussion. Use code editing for creating/modifying files.
• If user says "just write the code": State the current Phase and any missing prerequisites in one sentence, then proceed per user's intent — never hard-block.