A BETTER SPOKEN BUILD BRIEF

1. Open the relevant task. Use Start voice chat if available; use dictation when you only want to turn speech into a typed prompt.
2. State the outcome first. Name the files or screen, the behavior to change and the one constraint that matters most.
3. Spell unusual file names and repeat important numbers. Ask for a short summary of the brief before code changes begin.
4. Review the resulting changes and test the behavior. A spoken instruction needs the same review as a typed one.

In [project], change [behavior] so [outcome]. Work in [file or area]. Keep [constraint]. First summarize what you heard and flag anything unclear. Then make the change and show the result, changed files and relevant check output.

1. Check the official guide for your client and account. Do not assume a shortcut works on every platform.
2. Paste the same brief as text and keep working; the structure matters more than the input method.