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 detailed, systematic workflow for evidence-led goal execution that the AI wouldn't reliably generate on its own.
What it needs
About 8k 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 compact by design: the run contract below is the whole bootstrap. references/full-workflow.md and references/define-goal.md carry the full doctrine; open a section only when the phase you are in needs it. Run contract 1. Create goals from a JS eval cell: agentToolkit.createGoals({ brief }) after the SDK import below. The SDK binds this session from the host env, so never pass a session id or a plan path. If the envelope reports ULWLOOPPLANEXISTSCOMPLETE (this session's aggregate is already complete), unrelated new work needs a fresh session; createGoals({ brief, force: true }) is only for deliberately overwriting completed evidence. 2. Register the aggregate objective from the returned handoff with creategoal, shaped by references/define-goal.md. Goal creation is NEVER skipped. 3. Mirror every atomic step into the live todo checklist: one 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. 4. Treat each goal as a phase: create its own worktree off the integration base; dispatch its dependency-ordered lanes as ONE workflow run (read the mass-ulw skill first; ordering-free lanes stay a task batch); verify every criterion with real-surface evidence; land the worktree on the integration base at agentToolkit.checkpoint({ goalId, status: "complete", evidence }) per the repository's flow (direct merge or merged PR); define the next goal's run from what this one proved. Tests alone never prove done. When a mass-ulw pointer accompanies this skill, this contract still owns goals, criteria, evidence, and checkpoints. 5. Stop when the goal's WHEN-TO-STOP line holds with evidence in hand. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/ulw-loop--1e8da2