Automated development workflow using the goal command

Opus 5.5 doesn't know when your code is done. nobody tells it. /goal does you know the loop: prompt → wait → "done ✓" → 3 tests still red → "keep going" 15 rounds of you for one feature /goal breaks it with one line: /goal every test in src/auth passes and lint is clean what happens next: ↳ Claude keeps working turn after turn on its own ↳ a small overlay shows time, turns and tokens ↳ it stops the moment the condition is true. not when it feels done no "keep going". no checking every 5 minutes Opus doesn't quit early or polish forever. it just never knew where the finish line was the whole trick is the line you write ↓ bad: /goal make auth better good: /goal every test in src/auth passes, lint is clean, build succeeds a real finish line is: ↳ checkable by a command (tests, lint, build) ↳ scoped to one folder or one feature ↳ true or false. "better" is never true if a command can't check it, it's not a finish line my order now: /plan first, agree on the plan, then /goal and walk away bookmark this before your next "is it done yet?" session this is module 10 of my Opus 5.5 playbook. the other 25 are below ↓