Step 6: Break the Spec Into Vibe-Sized Tasks

The final move is to slice your spec into tasks the AI can execute one at a time. A vibe-sized task is small enough that you can review the result in a minute and know whether it worked. If a task takes the AI several files and you can't tell if it's right, it's too big.

Good tasks for the book tracker:

1. Set up the basic page layout with a header and an empty book list.
2. Build the "add a book" form (title + author) that appends to the list in memory.
3. Add status (To Read / Reading / Finished) with a dropdown to change it.
4. Save the list to browser local storage so it survives a refresh.
5. Add a rating control that appears only for finished books.
6. Add status filter buttons above the list.

Each task maps to a user story or PRD line, builds on the last, and ends in something you can see working. That's the rhythm of vibe coding: small task, run it, verify, next.

You can even have the AI generate this breakdown for you:

Here is my mini PRD and data model [paste them].
Break this into 6–8 small, ordered build tasks. Each task should
be independently testable and build on the previous one. Keep each
task to something I can verify by clicking around the app.