Free guide

The /goal Playbook

Stop prompting Claude step by step. The 3-step method (Achieve, Plan, Goal) that lets Claude Code work a whole job on its own until it is actually done: three copy-paste prompts, the goal-line formula, and a real run to copy.

A 3D render of a coral finish-line flag standing at the end of a glowing track of three step tiles labeled ACHIEVE, PLAN, GOAL, with the Claude mark on the dark engine block behind it
Get it free →

Hand off whole jobs, not steps

Prompting keeps you as the bottleneck: ask, answer, steer, repeat. With /goal you set a finish line and Claude keeps working, checking itself after every turn, until the job is verifiably done. This guide is the method for doing that well.

The exact prompts, in order

Three copy-paste prompts: one to state what you want to achieve, one that makes Claude design the plan before touching anything, and the goal-line skeleton that hands it the finish line. Trash in, trash out, so the front two steps are what make the third one work.

A real run to copy

See the full sequence from a real job in our own system: a competitor research machine that scraped, watched, and scored 69 videos and wrote the report while we did something else. Not a demo, the actual workflow.

What's inside

  • The 3-step method: Achieve, Plan, Goal, and why the order is the whole trick
  • Three copy-paste prompts, one per step, ready to swap your job into
  • The goal-line formula: one measurable end state, the proof, the guardrail, the stop bound
  • Weak vs strong goal lines, side by side, so you can spot an uncheckable goal before Claude can't
  • The real worked run: our competitor research machine, from the first ask to the finished report
  • The when-to-use checklist, including when NOT to reach for /goal

Questions

What is /goal exactly?

A built-in Claude Code command. You give it a completion condition, and after every turn a second, separate model checks whether the condition holds. If it does not, Claude starts another turn on its own instead of handing control back to you. It keeps going until the check passes.

Do I need to be a developer?

No. The method is plain English end to end: you describe the outcome, approve a plan, and state a finish line Claude can verify. The example in this guide is a research job, not a coding one.

What do I need to run it?

Claude Code (the terminal or desktop app) version 2.1.139 or later. Type /goal in any session and you will see it. Everything else in the guide works with the Claude you already have.

Why not just prompt normally?

For a quick question, do. /goal earns its place on long, multi-step jobs with a checkable finish line: a migration, a backlog, a build, a research sweep. The checklist inside tells you which is which.

Is it really free?

Yes. Drop your email and it is yours, and a copy lands in your inbox so you keep it.

Get it free. Where should we send it?