Menu
Stop and archive the currently active goalkeeper goal. Use when the user invokes /goal-clear to abandon or finalize a goal. Files are moved to .claude/goals/_archive/, never deleted.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run a linear sequence of goalkeeper goals where the judge gates progression between them. Use when the user invokes /goal-chain "<file>" to start a chain. Also auto-invoked by the judge skill on approval to advance the chain cursor.
The gate. Reviews the active goalkeeper goal against its definition-of-done and either approves (advance / mark done) or rejects (with a structured fix-list). Auto-fired by the goal skill when the validator passes (inline mode), or invoked by the goal-chain orchestrator after executor subagent returns (subagent mode, v0.3+). Can also be invoked on demand via /goal-judge for advisory review.
Set or check status of a durable goalkeeper goal. Use this skill when the user invokes /goal "<objective>" to start a new contract-driven goal, or /goal with no arguments to see status of the currently active goal. Goalkeeper goals run autonomously across many turns with checkpoint validation and judge-gated completion.
The mission-level supervisor. One level above goals. Reads the user's mission charter and the most-recently-completed goal's artifacts, then decides whether to PROCEED (draft + activate the next goal), declare the mission DONE, or ESCALATE to the user. Use this skill when the user invokes /goal-supervisor after a goal completes, or when running a multi-goal arc where each next goal's shape is informed by the prior goal's actual output.
Interactively draft a goalkeeper contract before executing. Use this skill when the user invokes /goal-prep "<rough idea>", or when /goal is called for a slug that has no contract yet. Produces a well-formed contract.md with explicit objective, definition-of-done, validator command, and non-goals.
Pause the currently active goalkeeper goal without losing state. Use when the user invokes /goal-pause. The goal can later be resumed with /goal-resume.
| name | goal-clear |
| description | Stop and archive the currently active goalkeeper goal. Use when the user invokes /goal-clear to abandon or finalize a goal. Files are moved to .claude/goals/_archive/, never deleted. |
You are operating the goal-clear skill.
Read .claude/goals/active.json. If no active goal, tell the user and stop.
Read .claude/goals/<slug>/state.json to capture final status.
Confirm via AskUserQuestion before archiving (unless the goal is already done):
Append a final log entry:
## <ISO8601> — cleared
Final status before clear: <status>. Rejection count: <n>. Archived.
Move (not copy) .claude/goals/<slug>/ to .claude/goals/_archive/<slug>-<YYYYMMDD-HHMMSS>/. Use mv via Bash to preserve files atomically.
Set .claude/goals/active.json to the canonical terminal shape (see goal.md "Canonical state shapes"):
{
"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>".
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.
Tell the user: "Cleared goal <slug>. Archived to .claude/goals/_archive/<dir>/. Run /goal or /goal-prep to start a new one."
_archive/. The user may want to inspect the contract or log later.done (in which case clear is just bookkeeping).