goalifylisted

# goalify ## Overview In one line, for anyone: **Hand Claude a huge task. Come back to proof it's done — not a promise that it is.** Prepare the best possible autonomous run in THIS session, then hand off so the user can `/clear` and launch it in a fresh session that has full context to work in. **goalify produces TWO artifacts, not one — and they have fixed names. Use these words everywhere:** 1. **The brief** — a *file*: a self-contained implementation Markdown file at an absolute path under `.goal/`. It is the source of truth for the **worker** (the fresh session doing the job). 2. **The condition** — a *string*: one short, plain sentence (≤ 4,000 characters, and normally nowhere near that), *derived from* the brief's success criteria. It is the source of truth for the **evaluator** (the Stop hook that decides "is this done?"), and it is what the user pastes into `/goal`. There is no third artifact and no combined one. `/goal` takes the condition string, never a path. > **The v2 correction — v1 of this skill got this wrong.** `/goal` takes a **condition string, never a > file path**. Hand it a path and that literal path string *becomes* the condition. The evaluator has > no file access, so every turn it is asked whether "`/Users/me/.goal/task.md`" is satisfied — and it > never resolves, resolves arbitrarily, or gives up and reports success. The gate looks like it works > because the *first* turn reads the path and starts working. Never put a path where a