Organize after capture#
Read the transcript and mark four elements: the problem, the intended change, what must remain true and the output you want. Remove repeated explanations only after checking that they do not carry a correction or exception.
For example, “Maybe make it formal—actually, friendly, but keep the technical terms” contains a revised preference and a constraint. A summary that keeps only “make it formal” loses the final intent.
Use a visible draft#
CueSpec keeps the request reviewable before sending. Optional text refinement is intended to improve expression, but it requires a configured service and login and still needs complete real-service acceptance. You can perform the same structural edit manually today.
Ask for a draft, analysis or recommendation when the next action is not yet settled. If you intend implementation, specify the scope and any approval boundary. Fluency should not manufacture missing authorization. A shorter prompt is useful when it preserves your meaning; length alone is not the acceptance criterion.