| 1 | --- |
| 2 | name: interview |
| 3 | description: Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked. |
| 4 | invocation: model+user |
| 5 | --- |
| 6 | |
| 7 | # Interview |
| 8 | |
| 9 | ## When to use |
| 10 | Use when the request lacks a material product or implementation choice that cannot be discovered from the workspace or tools. |
| 11 | |
| 12 | ## Non-goals |
| 13 | - Do not interview for facts you can read, search, or measure. |
| 14 | - Do not ask multi-question dumps. One focused question at a time. |
| 15 | - Do not invent requirements. |
| 16 | |
| 17 | ## Workflow |
| 18 | 1. State the missing decision and why it blocks progress. |
| 19 | 2. Offer concrete options when possible. |
| 20 | 3. Record the answer and continue the work. |
| 21 | 4. Produce a short brief/spec only when enough answers exist. |
| 22 | |
| 23 | ## Failure mode |
| 24 | If the user declines to answer, proceed with explicit assumptions and label them. |
| 25 |