the new /goal feature in codex still underperforms queueing my implementation prompt. for now e.g. when I give a goal to refactor the whole codebase, the model takes shortcuts, like only refactoring a subfolder, instead of the whole project --- presumably because it decided that it would be too big of a scope somewhere along the way, even though I instructed specifically to finish the whole thing so now I started doing both: set a goal, and then queue my regular implementation prompt. it's a stupid practice. just /goal should be enough in the long run, if implemented correctly