agent-goal

name	agent-goal
description	Create a slash-command `/goal` for long-running Codex or Claude Code work when the user explicitly asks for a `/goal`, agent goal, or completion condition. Outputs one goal line with the objective, starting context, validation evidence, and stop condition.

Agent Goal

Write one /goal line that a coding agent can keep pursuing until the transcript proves the work is done.

This skill owns the slash-goal artifact. Do not use it for ordinary prompt drafting, handoffs, continuation prompts, delegation briefs, or prompt engineering.

Shape

/goal <single objective> in <lane> until <observable evidence proves completion>. First read <starting context>. Work in checkpoints and surface <validation evidence> after each checkpoint.

Answer these in order, then compress them into one line:

What should change?
Where should the agent start?
What evidence proves it changed?
When should the agent stop?

Include only execution-critical detail:

• Objective: one concrete outcome, not a backlog of unrelated wishes.
• Lane: files, packages, apps, issues, specs, or the intended work area.
• Starting context: the first files, plans, logs, screenshots, or acceptance criteria to read.
• Evidence: command output, tests, build result, screenshot check, eval score, file count, or reviewed artifact.
• Stop condition: the exact transcript-visible state that means the goal is achieved.

Rules

1. Start the answer with /goal when the user asks for the goal text.
2. Make completion judgeable by someone who can only read the transcript.
3. Prefer exact checks over vague proof: "bun test packages/auth exits 0" beats "tests pass."
4. Point long requirements at a file instead of pasting them into the goal.
5. Ask for checkpoints when the work spans multiple turns.