goal

name	goal
description	Run or manage a Codex-style persistent goal loop in Pi chat using the goal CLI. Use for /skill:goal, /goal, goal pause, goal resume, goal clear, durable objectives, verification loops, and evidence-based completion.

Goal Skill (Pi)

Use this skill when the user invokes /skill:goal, /goal, or asks for a Codex-style persistent goal loop.

Run the loop in this Pi chat session. You are the agent. Do not spawn external agent APIs.

Use the local goal CLI (or cursor-goal) for durable state, verification, and checkpoint accounting.

Resolve the CLI as the first working command:

goal status 2>/dev/null || cursor-goal status 2>/dev/null || node "$GOAL_CLI" status

If neither goal nor cursor-goal is on PATH, set GOAL_CLI to a built @nikomohr/goal-cli entrypoint and use node "$GOAL_CLI".

Command mapping

• /skill:goal or /goal → goal status.
• /skill:goal <objective> or /goal <objective> → set state, then work the goal in this chat.
• goal pause / /goal pause → goal pause.
• goal resume / /goal resume → goal resume, then continue in this chat.
• goal clear / /goal clear → goal clear.
• goal edit "<objective>" → replace objective, then continue.

When setting a goal from the CLI:

goal "<objective>" --verify "npm test"

If the objective names verification, pass --verify. Otherwise infer a safe command when obvious.

Checkpoint loop (each turn)

1. Load active goal with goal status. If missing on a new objective, set it with goal.
2. If status is not active, report status and stop unless the user asked to resume.
3. Optionally run goal prompt for the formatted continuation contract.
4. Make one bounded checkpoint of concrete progress with normal Pi tools.
5. End your response with exactly:

GOAL_STATUS: COMPLETE | CONTINUE | BLOCKED
GOAL_REASON: <one short evidence-based sentence>

6. Record the checkpoint:

goal checkpoint --tool-calls <n>

Pipe your final assistant text on stdin when needed.

7. If still active, continue in follow-up turns until complete, blocked, budget_limited, or the user pauses.

Operating contract

• Treat the goal text as both the starting prompt and the completion criteria.
• Prefer small, auditable changes over sweeping rewrites.
• Use repository evidence: files, diffs, tests, command output, artifacts.
• Do not declare complete unless verification passed or you justify why it no longer applies.
• If blocked, use GOAL_STATUS: BLOCKED.
• Default to at most 8 checkpoints unless state sets a different budget.

Safety

• Do not run destructive verification unless explicitly requested.
• Do not expose secrets.