# You’ve been writing /goal wrong. It’s a completion condition, not a description. — retained record

> Retained reddit record from reddit:ClaudeCode.

Canonical: https://highsignal.app/data/records/a1a6be67d70627ba

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:ClaudeCode)  published 2026-09-17 16:49 ingested 2026-09-18 02:41

[original source ↗](https://www.reddit.com/r/ClaudeCode/comments/1wizdvo/youve_been_writing_goal_wrong_its_a_completion/)

## retained text



```
Spent the week actually reading what `/goal` and `/plan` do instead of assuming. I'd been writing goals wrong the whole time.

**Claude Code has three ways to take a request:**

* **Plan** — explores and proposes, touches nothing until you approve. The model can decide to enter this on its own based on how you phrased things.
* **Goal** — you type `/goal <condition>` and the session keeps working toward that condition. Nothing else starts one. If you didn't type it, you're not in it.
* **Direct** — just does it, this turn, and stops.

**The mistake is writing a goal as a description of the work.**

    /goal add refund support and make sure it's done properly

That's a wish. "Properly" isn't something anything can evaluate, so the session runs until the model decides it's finished — exactly what you'd get with no goal at all. The word `goal` is doing nothing.

A goal is the **stopping condition**. The useful content is the part that says *when this is over*.

    /goal Checkout refunds work locally. Done when partial refunds,
    retry safety and audit history are implemented, tested and
    reviewed. Don't deploy.

Three things that make the difference:

* **The outcome** — what exists at the end that doesn't now.
* **The criteria** — specific enough that something other than you could check them.
* **The constraints** — what not to touch, and what not to build. Unasked scope is the most common way this goes sideways and the least likely thing you'll write down.

**Codex isn't the same, by the way.** `/plan` there is a command you type — the model can't call it — and it's unavailable while Codex is already working. `/goal` attaches an objective to the chat with edit/pause/resume/clear, capped at 4,000 characters. A habit you build in one doesn't transfer cleanly.

Also worth knowing: `/goal` availability depends on workspace trust and your hook settings, so it's not guaranteed to be there.

How do you decide between plan mode and a goal? I still default to plan for anything I haven't scoped, but I'm not sure that's right.
```



document fetched 2026-09-18 00:41 · canonical https://reddit.com/r/ClaudeCode/comments/1wizdvo/youve_been_writing_goal_wrong_its_a_completion
