Incremental Plan

Break a spec into 2-4 big steps that each deliver a working, end-to-end slice of the product.

Why

A big spec implemented in one pass is hard to debug and course-correct. But splitting it into too many tiny steps (DB schema, page shell, config inputs, etc.) creates busywork — each step is too small to be meaningful on its own and the plan becomes a rigid checklist instead of a useful guide. The sweet spot is 2-4 substantial steps where each one produces something a user can actually try.

Workflow

1. Read the Spec

Read the spec document the user provides. Identify:

• The core mechanism (the fundamental thing that makes the product work)
• The distinct technical layers (e.g., backend service, database, frontend UI, external integrations, auth)
• Dependencies between features (what requires what)

2. Ask Clarifying Questions (if needed)