Ultragoal

<Use_When>

• The user wants a durable, repo-native way to track an ultragoal across multiple Claude sessions or worktrees
• The work is large enough to warrant multiple ordered "stories" with attempt counts and per-story evidence
• The user wants the final completion gated behind ai-slop-cleaner + verification + $code-review
• The user wants the active Claude /goal directive coordinated with the ledger so that a session restart does not lose progress </Use_When>

<Do_Not_Use_When>

• The task is a single small change — use direct delegation or ralph instead
• The user wants the assistant to literally invoke /goal itself from the shell — that is not possible; omc ultragoal only writes artifacts and prints handoff text
• The user wants a planning-only artifact with no execution loop — use plan instead </Do_Not_Use_When>

<Why_This_Exists> Claude Code /goal is a session-scoped Stop hook: it blocks the session from stopping until a condition holds, and auto-clears on success. That is a great single-session execution primitive, but it loses state across sessions and does not by itself enforce a final review gate. omc ultragoal adds a durable plan, ledger, and gating layer so a long multi-step initiative can survive session restarts, fresh worktrees, and review iterations while still leveraging Claude /goal to keep the active agent focused. </Why_This_Exists>

<How_To_Use>

1. Create a plan from a brief:

   omc ultragoal create-goals --brief-file plan.md
   

   Or with explicit stories:

   omc ultragoal create-goals --brief "ship the migration" \
     --goal "Schema::Add new columns" \
     --goal "Backfill::Backfill rows in batches" \
     --goal "Cutover::Drop old columns and switch reads"
   

   The default mode is aggregate (one Claude /goal covers the run). Pass --claude-goal-mode per-story if you want each story to have its own /goal.

   Multi-repo workspaces / parallel sessions: when several Claude sessions in the same workspace need to run /ultragoal concurrently, pass either --plan-id <stable-id> or --auto-plan-id so the plan is written to