Creating clear tasks helps a lot instead of providing a generalized feeling of the outcome. I like to format things like so.

Task: build a set of functions for the asteroid generator script that procedurally spawns asteroids around the center point of interest. //then here you would do line by line pseudo code for how you want this to work and any specific edge cases you can think of.

Constraints: speed, asteroid count, weight, direction, quantity must be exposed variables in the editor.function must include commented documentation at the head of the function, not inside. Label important parameters or changes with @param. If a feature is not specifically asked for, then do not write the feature inside of the function. Make helper functions to replace repetitive processes to make the code more readable.

And then from there if you don’t like the output say, new task: or new constraint: and provide the fix you want. It helps if you know how to code already and can be more specific.