ultragoal

name	ultragoal
description	Durable artifact-backed multi-goal completion workflow for Omagy on Antigravity CLI.

Omagy Ultragoal

Use /omagy:ultragoal when the user asks for durable multi-goal execution, ultragoal, create-goals, complete-goals, or execution of an approved plan through a persistent goal ledger.

Purpose

Omagy Ultragoal adapts OMX Ultragoal to agy. It owns durable state in:

• .omagy/ultragoal/brief.md
• .omagy/ultragoal/goals.json
• .omagy/ultragoal/ledger.jsonl

It does not claim native agy /goal parity. Until agy exposes a stable native goal API, .omagy/ultragoal is the source of truth and omagy ultragoal complete-goals emits a model-facing handoff for the active agy agent. When a host goal snapshot is available, pass it with --host-goal-json so Omagy can reconcile objective/status before checkpointing.

Workflow

1. Create goals:

   omagy ultragoal create-goals --brief "<brief>" --goal-mode aggregate
   omagy ultragoal create-goals --brief-file <path>
   

2. Start or resume the next goal:

   omagy ultragoal complete-goals
   

3. Execute only the current goal.

4. Checkpoint:

   omagy ultragoal checkpoint --goal-id <id> --status complete --evidence "<evidence>" --host-goal-json '<json>'
   

5. Add or steer goals only through structured commands:

   omagy ultragoal add-goal --title "<title>" --objective "<objective>" --evidence "<why>"
   omagy ultragoal steer --directive-json ./steering.json
   

6. On the final goal, include clean quality-gate JSON with cleanup, verification, and APPROVE + CLEAR code-review evidence.

7. Close workflow state only after all goals are terminal:

   omagy workflow complete --mode ultragoal --input '{"verification_evidence":["<evidence>"]}' --json
   

Boundaries

• Plan-approved execution may enter through omagy plan handoff --mode ultragoal.
• Team may execute parallel work, but Team workers do not own or checkpoint .omagy/ultragoal.
• Do not run Ralph and Ultragoal as peer persistence owners.
• Do not mutate goals from ordinary prose. Use omagy ultragoal steer with structured evidence, source, after-json/idempotency metadata when available.
• If final review is not clean, use omagy ultragoal record-review-blockers instead of completing the aggregate run.
• If a repeated authorization blocker is classified as needs_user_decision, stop retrying until the user chooses the external unblock path. After the user chooses an alternative path, use omagy ultragoal steer --kind mark_blocked_superseded to explicitly supersede the blocker before final aggregate completion.