goal-clear

You are operating the goal-clear skill.

Flow

1. Read .claude/goals/active.json. If no active goal, tell the user and stop.
2. Read .claude/goals/<slug>/state.json to capture final status.
3. Confirm via AskUserQuestion before archiving (unless the goal is already done):
4. Archive and clear (Recommended) — proceed.
5. Cancel — abort, no changes.
6. Append a final log entry:

`` ## <ISO8601> — cleared Final status before clear: <status>. Rejection count: <n>. Archived. ``

1. Move (not copy) .claude/goals/<slug>/ to .claude/goals/_archive/<slug>-<YYYYMMDD-HHMMSS>/. Use mv via Bash to preserve files atomically.
2. Set .claude/goals/active.json to the canonical terminal shape (see goal.md "Canonical state shapes"):

``json { "slug": null, "ended_at": "<ISO8601 now>", "ended_reason": "cleared", "previous_slug": "<the slug just cleared>" } ` If a chain was active, also include "previous_chain": "<chain-name>"`.

1. If a chain is active (.claude/goals/chain.json exists with status == "active" and contains the cleared slug), set chain.json.status = "aborted" and chain.json.completed_at = <ISO8601 now>. Append a ## <ISO8601> — chain aborted entry to the cleared slug's log.md (chain-level events are reconstructible from per-link logs + chain.json — there is no separate chain-log file). Do NOT advance to the next goal — clearing kills the chain. Do NOT modify the contracts or state of unreached chain links — their contract.md files stay in place for re-use.

If chain.json.status is already done or aborted (chain not currently active), leave chain.json untouched — the cleared goal is being archived after the chain finished, not aborting an in-flight chain.

The active.json ended_reason stays "cleared" (not "aborted") — aborted is a chain-level signal carried in chain.json, while the user's clear action on the goal is per-goal terminal context.

1. Tell the user: "Cleared goal <slug>. Archived to .claude/goals/_archive/<dir>/. Run /goal or /goal-prep to start a new one."

Hard rules

• Never delete files. Always move to _archive/. The user may want to inspect the contract or log later.
• Never proceed without confirmation unless the goal is already done (in which case clear is just bookkeeping).
• Clearing kills any active chain — chains are not auto-resumed mid-stream.
• The log entry is append-only.