ultra-grillinglisted

# Turn a vague ask into a decision list the owner has explicitly confirmed No-one knows exactly what they want at the start. This prevents the misalignment that surfaces at the end, when both sides believed they had agreed and the finished work proves otherwise. It serves Goal 1, Intent Fidelity. ## Before you start 1. Reread what the owner said in the current request, verbatim. 2. Read `.ultra/project-brief.md`, `.ultra/north-star.md`, and `CONTEXT.md` where they exist. Raw intake is reusable input; accepted wording must not be re-asked. 3. Look up every fact you can reach on your own: repository files, Git history, installed dependencies, tool output. Facts are yours to find, decisions are the owner's to make. A question they could have answered by reading the repository spends the one input only they can give. ## Definition of done - Every field the caller named as required is either answered in the owner's own words or explicitly deferred with the reason recorded. "Every branch of the tree" is not something you can check against a file; the caller's field list is. - The reframe below was put to the owner and either confirmed or corrected. It is never skipped because the original wording sounded clear. - Each answer carries the owner's confirmation, rather than something that sounded like agreement. - The caller owns the final artifact and receives a decision list it can write: one line per decision, each with the options rejected and why. ## Extract