---
name: ultragoal
description: "Durable goal orchestration skill for Claude Code durable goal orchestration for Claude Code: explicit success criteria, evidence ledgers, native goal surfaces, and completion gates."
---

# Ultragoal

Use this skill when a task must survive across turns or sessions. It is a
Claude-native durable goal orchestration. The central rule is simple: a goal is
not complete until every success criterion has observable evidence.

## Goal Shape

Represent work as:

- objective
- non-goals
- success criteria
- expected evidence per criterion
- current state
- blockers
- cleanup receipts
- final verification gate

When model-facing goal tools are available, use them. When they are absent,
store the same structure in plan files, handoffs, or local ledgers.

## Native Goal Surface

- Call `get_goal` before creating a new goal when exposed.
- Call `create_goal` only when there is no matching active goal.
- Call `update_goal` only when the objective is verified complete or genuinely
  blocked.
- Treat `/goal` as a user-visible Claude Code slash command, not a skill call.
- Do not invent a successful goal activation without evidence.

## Manual-QA channels

## Manual-QA Channels

Each criterion needs one channel artifact:

- HTTP call with `curl -i`
- tmux transcript
- browser action log and screenshot
- desktop automation action log and screenshot

Auxiliary CLI output can support data-shaped criteria, but user-facing behavior
needs the real surface.

## Ledger Discipline

Record:

- criterion id
- status: pass, fail, or blocked
- test command and output path
- manual QA artifact path
- cleanup receipt
- adversarial classes probed
- next action if not pass

Do not rely on memory. If a fresh agent cannot determine state from the ledger
or handoff, the workflow is not durable.

## Completion Gate

Before completion:

1. All criteria pass.
2. Full relevant test suite passes.
3. Manual QA artifacts exist.
4. Cleanup receipts are recorded.
5. Review has no blocking findings when the change is broad or risky.
6. Commit/push or publish instructions match the user's request.

## Claude Adaptation

Other runtimes may expose native goal tooling. Claude Code may expose a different
surface. Port the principle, not the literal tool name: use `Workflow`,
`EnterWorktree`, slash commands, plans, or handoffs only where that surface
actually exists.

## Recovery

When a session resumes, read the handoff or ledger before doing anything else.
If the state says work is complete, verify with one command before reopening the
task. If the state says blocked, reproduce the blocker first. Never create a
second parallel goal for the same objective just because the old state is
inconvenient.

## Minimal Artifacts

At minimum, a durable goal run should leave a brief, criteria list, ledger,
evidence directory, and final verification note. For small LazyClaude tasks,
those may be a single plan file plus `HANDOFF.md`; for large work, use a
dedicated `.omo` directory or plan-local evidence folder.
