Confirm

Before writing any code, align with the user on what the task actually is.

Asking questions

Whenever you put a question to the user — one of the steps below, or an ad-hoc question when something is unclear — ask it and wait for their answer before carrying on.

Step 1's summary is the context step 2's questions need, so give it to the user alongside them.

Workflow

1. Summarize understanding — In your own words, state:

   • The goal (what outcome the user wants)
   • The scope (what's in, what's out)
   • The approach you'd take (key files, structure, libraries)
   • Any assumptions you're making

2. Ask clarifying questions — Only ask about things that genuinely change the implementation. Skip questions whose answers won't affect the code. If you have no real questions, say so.