ulw-loop (Ultrawork Goal Loop)
A goal-driven execution loop that decomposes long work into atomic steps and only marks them done with real, tree-bound evidence.
AutomationAdvanced★ 67,531⑂ 5,507AI score 6/10Last updated: Aug 9, 2026
What it does
ulw-loop enforces a "goal → atomic step → evidence" discipline for long-running delivery.
- Registers goals in the
omo ulw-loopCLI state (.omo/ulw-loop) and mirrors every step into a live checklist with exactly onein_progressitem. - Passing tests never count as done. Each success criterion needs observable evidence from a real surface: terminal/TUI, HTTP, browser, computer-use, CLI stdout, DB diff, or parsed config dump.
- Evidence is bound to the git tree hash it was captured at, so it goes stale when tracked content changes and must be re-captured at the current HEAD.
- Code edits, test writing, fixes, and QA are delegated to right-sized subagents via the native
tasktool, run in the background withWORKING:/BLOCKED:progress reporting andtask_sendcorrections. - Team mode (
team_create) is a deliberate decision, only when work units genuinely overlap — with one git worktree per member and per-unit merges. - After compaction, it re-reads brief + goals + ledger and
omo ulw-loop status --jsonbefore resuming instead of re-planning.
Who it's for
- Engineers running multi-day refactors or migrations where context loss is inevitable.
- Teams tired of "tests passed but it didn't actually work" and wanting verifiable receipts.
- Anyone orchestrating many parallel agents who needs file-scope isolation and clean atomic commits.
- Best suited to users already on (or willing to install) the omo-senpi /
omoCLI stack.
Examples
- Large migration: "use ulw to move the auth module to the new SDK" — goals are registered, steps decomposed, and each step captures a real login run in a terminal or browser as evidence.
- Parallel feature work: batch-spawn three background workers for three features in disjoint files, while the lead reports active subagent count and the latest
WORKING:phase. - Manual QA checkpoint: before release, collect evidence per success criterion (HTTP response, DB diff) and commit each verified unit atomically in the repo's own message style.
· · · Install guide · · ·
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the packages/omo-senpi/skills/ulw-loop folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/code-yeongyu-ulw-loop/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/code-yeongyu/oh-my-openagent.git && mkdir -p ~/.claude/skills/ulw-loop && cp -r oh-my-openagent/packages/omo-senpi/skills/ulw-loop/* ~/.claude/skills/ulw-loop/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal and go to a working directory.
- Clone the repository:
git clone https://github.com/code-yeongyu/oh-my-openagent.git - Create the skill folder:
mkdir -p ~/.claude/skills/ulw-loop - Copy the whole skill, including the
references/folder:cp -r oh-my-openagent/packages/omo-senpi/skills/ulw-loop/* ~/.claude/skills/ulw-loop/ - Verify
references/full-workflow.mdexists in the copied folder — without it the skill cannot read its core workflow. - This skill depends on the
omo ulw-loopCLI; follow the repository root README to install omo-senpi / theomoCLI. - Restart Claude Code and trigger it with a request like "run this with ulw-loop".
View source on GitHub ↗License: NOASSERTION