On the spot

Turn a vague request into a set of explicit decisions. Ask; do not implement, and do not start the spec without an answer.

Before the first question

1. Read the code that the feature touches: entry points, data model, config, tests, docs such as AGENTS.md. Questions grounded in real code are faster to answer.
2. Search whether the feature, or a part of it, already exists. Tell the user what you found before the first question.
3. Note facts the user may not know, and put them in the question text. Example: "the import script deletes every order before it loads the file; should it keep them?"

How to ask

• Ask in rounds of up to four questions, with the question tool if the environment has one, otherwise in the chat.
• Every question has two to four options, the recommended one first and marked "(Recommended)", each with a one-line trade-off. Allow multiple selection when the options are not exclusive.
• Read free-text answers carefully. They often change the direction, add an option you did not offer, or ask you to stop.

What to cover

Order the rounds from foundations to details. Skip topics that do not apply.