agent-goal
/agent-goal
Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition. Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition.
- Author
- EpicenterHQ ↗
- Repository
- epicenter ↗
- Licence
- MIT
- Last repository change
- 17.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 17.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition. Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition.
Original author description
Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition. Use when the user explicitly asks for `/goal`, an agent goal, or a completion condition.
How it works
- Shape
- Rules
- Platform Note
- Check
SKILL.md preview
--- name: agent-goal description: Draft a `/goal` line that gives long-running Codex or Claude Code work an objective, validation evidence, and a stop condition. Use when the user explicitly asks for `/goal`, an agent goal, or a completion 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 ```txt /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: ```txt 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. 6. Bound repeated failure: after three failed attempts on the same check, report the root cause and next decision. 7. Do not create a `/goal` for vague wishes, open-ended research, unrelated chores, or work with no observable evidence. ## Platform Note Different agents may evaluate goals differently, but the portable rule is the same: the goal should not rely on hidden state. Tell the agent to run checks and surface evidence in the transcript. ## Check Before handing back a goal, verify: - It has one main objective. - It names where to start. - It names the evidence that proves completion. - It tells the agent to surface that evidence. - It tells the agent when to stop.
Versions
The database has no other skills named agent-goal.
Database snapshot: 13.11.2026 · package version 0318ffc37898 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100goal-prompt
Drafts copy-paste-ready /goal commands for goal mode in Claude Code and Codex. Use when the user asks to create, write, rewrite, improve, compress, clean up, or prepare a goal prompt, goal condition, /goal command, goal-mode objective, or copy-ready long-running task objective. - 100goal-prompt
Turn a task, plan, or feature request into a ready-to-paste Claude Code /goal command — a single completion condition with a measurable end state, a demonstrable proof, and the constraints that must not drift. Use when the user says "give me a goal", "goal prompt", "make this a… - 84draft-goal-condition
Pick the repetition lever (/goal, /loop, routines and /schedule, a workflow, a Stop hook, or a one-shot prompt) and, when /goal fits, draft a transcript-demonstrable completion condition, checked against the documented limit by a deterministic counter. Use when: 'which loop… - 100codex-goals
Patterns and anti-patterns for using OpenAI Codex Goals — the persistent objectives feature introduced in Codex 0.128.0. Use this skill whenever writing, reviewing, or debugging a `/goal` invocation, deciding whether a task should be a Goal at all, drafting a research Goal that… - 100goalcraft
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for long-running autonomous work. Use when the user asks to write, improve, format, sharpen, stress-test, or activate a Codex goal, thread goal, durable goal, or /goal prompt. - 100goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user…