ultragoal

Manages durable multi-goal execution plans with a repo-native JSON ledger and final review gate.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill ultragoal-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ultragoal
Source: https://github.com/catalystctl/catcode/tree/main/.omp/skills/ultragoal
Command: npx skills add https://github.com/catalystctl/catcode --skill ultragoal-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Long-running multi-step coding work loses track of progress when sessions end or agents change, and ad-hoc goal tracking offers no audit trail or quality enforcement. This Skill provides a durable, repo-native plan ledger under .omp/ultragoal/ so multi-story work survives restarts, stays auditable, and cannot be marked complete without passing a mandatory review gate. ## Core Features & Use Cases - Durable plan ledger: Stores brief, goals, state, and an append-only ledger.jsonl audit trail in .omp/ultragoal/, with migration from legacy .omx/ultragoal/ directories. - Sequential story execution: Decomposes a brief into ordered stories with stable IDs, then drives them through start, checkpoint, steer, and completion phases via the lib/ultragoal.mjs helper. - Mandatory final quality gate: Blocks the final story from completing until verification passes, an ai-slop cleanup runs, architecture invariants are proved, and two independent reviewer agents approve. - Use Case: You need to implement a large feature spanning several sessions. Create an ultragoal plan, execute each story in order with checkpointed evidence, and let the final gate enforce independent code and architecture review before the plan closes. ## Quick Start Ask the agent to create an ultragoal plan from your feature brief and then run each story sequentially with checkpoints until the final review gate passes.

Frequently Asked Questions about ultragoal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a multi-goal execution plan in a repository?

Write a brief with constraints and architecture invariants, decompose it into sequential stories with stable IDs, then run the create command via the ultragoal helper. The plan is stored in .omp/ultragoal/goals.json with an append-only ledger for auditing.

How do I resume a multi-story coding plan after a session ends?

Run the status command, which reads .omp/ultragoal/state.json and goals.json to report the next schedulable story. Start that story and continue checkpointing; the ledger preserves all prior evidence across sessions.

Can I migrate an existing .omx/ultragoal plan to .omp?

Yes. The migrate command copies legacy .omx/ultragoal artifacts into .omp/ultragoal, rewrites path references, and appends a migration ledger event. After migration, the .omp directory is the source of truth and Codex goal tools are never used.

Why was my final story checkpoint rejected as complete?

The final story requires a passing quality gate: verification passed, ai-slop cleaner passed, code review APPROVE, architect CLEAR, distinct reviewer evidence, and every architecture invariant proved. Missing or non-clean items cause rejection; use record-review-blockers instead.

What steering changes are allowed on an active goal plan?

Allowed steer kinds are add_subgoal, split_subgoal, reorder_pending, revise_pending_wording, annotate_ledger, and mark_blocked_superseded, each requiring evidence and rationale. Completed work, the aggregate objective, and the quality-gate bar cannot be modified.