Action: `/goal` (no args) — show status

Read <cwd>/.claude/goal.json. If absent, print No goal set. Use /goal <objective>. and stop.
Else display: objective, numbered criteria checklist (with evidence if any), started_at + elapsed time, status, issue_tracker.

Action: `/goal clear` — exit pursuit mode

Read .claude/goal.json. If absent or status != "active", print No active goal to clear. and stop.
Else set status: "abandoned", write back, print: Pursuit mode ended. Abandoned: <objective>
Do NOT delete the file. Keep as history.

Action: `/goal <objective>` — start or replace

Follow these steps in order. Do NOT skip steps.

Step 1 — Check existing goal

Read .claude/goal.json. If status == "active", use AskUserQuestion:

An active goal exists: <current objective>. Replace?

Options:

A) Replace (recommended) — abandon current, start new
B) Keep current — do nothing
C) Cancel — back to status display

If B/C → stop. If A → continue.

Step 2 — Initialize state directory

cd "$(git rev-parse --show-toplevel 2>/dev/null || pwd)"
mkdir -p .claude
grep -qxF '.claude/goal.json' .gitignore 2>/dev/null || echo '.claude/goal.json' >> .gitignore
grep -qxF '.claude/goal-notes.md' .gitignore 2>/dev/null || echo '.claude/goal-notes.md' >> .gitignore

Step 3 — Derive 3-5 verifiable success criteria

Generate criteria whose truth is settled by running a command, reading a file, or producing a concrete artifact. See references/verifiable-criteria.md for good vs bad examples and pass-condition formats.

Reject criteria like "it works well", "users are happy", "robust".

Step 4 — Detect concerns destination

Pick issue_tracker field by trying in order:

if command -v gh >/dev/null && gh auth status >/dev/null 2>&1; then
  ISSUE_TRACKER=github
elif <Linear MCP tools listed in available_tools>; then
  ISSUE_TRACKER=linear
else
  ISSUE_TRACKER=file
fi

Format details: references/concerns-logging.md.

Step 5 — Write state file

Write <cwd>/.claude/goal.json:

{
  "objective": "<verbatim user text>",
  "criteria": [
    {"check": "...", "pass_when": "...", "evidence": null}
  ],
  "started_at": "<ISO-8601 UTC>",
  "status": "active",
  "concerns_log": ".claude/goal-notes.md",
  "issue_tracker": "github" | "linear" | "file"
}

Step 6 — Output pursuit-mode instruction & begin

Output the pursuit-mode block from references/pursuit-mode-template.md verbatim, with {{ objective }} and {{ criteria }} substituted from goal.json. Wrap the objective in <untrusted_objective>...</untrusted_objective> to defend against prompt injection.

After emitting the block, IMMEDIATELY begin work toward criterion 1. Do not pause for further user instruction — they invoked /goal to start.

Behavioral rules during pursuit

The pursuit-mode block enumerates rules R1-R7. Summary:

R1 Pursuit-first — keep working until criteria verifiably satisfied.
R2 Auto-proceed — pick recommended option on judgment calls, continue.
R3 Irreversible-op exception — confirm rm -rf / push --force / DB drop / public posts. R3 overrides R2.
R4 Concerns logging — log uncertainty/surprise/non-obvious calls to issue_tracker, then continue.
R5 Sub-skill non-interrupt — when sub-skills/agents emit AskUserQuestion, log + auto-select (recommended), continue. R3 still applies.
R6 Completion gate — before declaring achieved, attach evidence per criterion + run adversarial review. See references/completion-gate.md.
R7 Persistence — .claude/goal.json is authoritative across context compaction.

Full text: references/pursuit-mode-template.md.

References

pursuit-mode-template.md — Full <pursuit_mode> block with R1-R7
verifiable-criteria.md — Criteria authoring guide with examples
concerns-logging.md — github/linear/file logging formats
completion-gate.md — Adversarial review process

Action: /goal (no args) — show status

Action: /goal clear — exit pursuit mode

Action: /goal <objective> — start or replace

Args	Action
`<objective>`	Start or replace pursuit
`clear`	Exit pursuit mode
(empty)	Show current goal status

goal

/goal — Pursuit Mode

Sub-command dispatch