/goal makes Claude Code and Codex keep working until the job is done, so you stop typing "keep going." A plain guide to writing finish lines that finish.
Dude - these examples don’t make sense. Goals work best for verifiable conditions where the work would take long and require your constant input
In the example with the trip, you’re basically doing the same amount of work and setting the goal actually requires more brainpower than less - you have to write instructions, think about what you want to do, dates, constraints etc. That is MORE work than answering agent’s questions interactively. So you’re not actually saving you any time or brainpower
In my experience, the goal works best after defining a clear plan with superpowers’ brainstorming (optionally /grill-me skill). Recently I described 10 most useful features to manage Claude sessions (once Claude responds in a satisfying way). Check it out at https://productpeak.substack.com/p/10-claude-code-power-moves-most-product
https://github.com/iAAi33iAAi
Dude - these examples don’t make sense. Goals work best for verifiable conditions where the work would take long and require your constant input
In the example with the trip, you’re basically doing the same amount of work and setting the goal actually requires more brainpower than less - you have to write instructions, think about what you want to do, dates, constraints etc. That is MORE work than answering agent’s questions interactively. So you’re not actually saving you any time or brainpower
In my experience, the goal works best after defining a clear plan with superpowers’ brainstorming (optionally /grill-me skill). Recently I described 10 most useful features to manage Claude sessions (once Claude responds in a satisfying way). Check it out at https://productpeak.substack.com/p/10-claude-code-power-moves-most-product