Agent skill · operations · code-yeongyu
ulw-loop
A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution.
Why this skill is useful
Provides a structured workflow for systematic goal execution and evidence tracking that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
ulw-loop Use this skill when the user asks for ulw-loop, ulw, durable goal execution, evidence-led work, manual QA, or checkpointed long-running delivery. This skill is intentionally compact. The full workflow lives in references/full-workflow.md. Read only the sections needed for the current phase, then execute them exactly. Required First Steps 1. Open references/full-workflow.md. 2. Read through Bootstrap (including its tier triage), Execution Loop, the Manual-QA channels table, and the Stop Rules before running any ULW command or recording evidence. 3. Open references/define-goal.md and register the run's goal by it. Goal creation is NEVER skipped: shape the objective and every success criterion by that reference before any implementation. 4. If the task has code edits, tests, QA, or commit work, follow the full workflow's delegation and evidence rules. Tests alone never prove done. Non-Negotiables Use the ulw-loop CLI state under .omo/ulw-loop; do not hand-edit goal state. Register goals up front, shaped by references/define-goal.md (omo-agent-toolkit ulw-loop create-goals, then creategoal from the printed handoff), and mirror every atomic step into the live updateplan checklist: one ultra-granular step per action, exactly one inprogress, transitions marked the instant they happen. Use the ultrawork directive’s Task resources and todo rules; read those sections of the bundled ultrawork skill if absent from context. After any compaction or context loss, re-read brief + goals + ledger FIRST plus omo-agent-toolkit ulw-loop status --json, then resume; never re-plan from scratch. Every ulw-loop command needs the session scope: pass --session-id <id> (the printed handoff and resume directive carry it; CODEXTHREADID in the environment also resolves it). The CLI refuses unscoped state (ULWLOOPSESSIONSCOPEREQUIRED) instead of touching the shared .omo/ulw-loop root. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/ulw-loop