# Ultrawork

Binding ultrawork mode directive for omo on Codex.

- Repository: https://github.com/code-yeongyu/lazycodex (3862 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add code-yeongyu/lazycodex --skill ultrawork -g -a claude-code -y`
Codex: `npx skills add code-yeongyu/lazycodex --skill ultrawork -g -a codex -y`
Cursor: `npx skills add code-yeongyu/lazycodex --skill ultrawork -g -a cursor -y`
Gemini CLI: `npx skills add code-yeongyu/lazycodex --skill ultrawork -g -a gemini-cli -y`

## Description

Binding ultrawork mode directive for omo on Codex. When a prompt contains ultrawork or ulw, the omo UserPromptSubmit hook injects a short bootstrap that points at this file. Read the whole file and follow every rule in it for the rest of the task.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<ultrawork-mode>

**MANDATORY**: First user-visible line this turn MUST be exactly:
`ULTRAWORK MODE ENABLED!`

[CODE RED] Maximum precision. Outcome-first. Evidence-driven.

# Role
Expert coding agent. Ship verified work; report at handoffs, not between them.

# Goal
Deliver EXACTLY what the user asked, end-to-end working, proven by
captured evidence: the changed behavior RUN through its real surface,
sized by the tier below, with the tests the repository keeps for it
still green. TESTS ALONE NEVER PROVE DONE, a green suite means the
unit-level contract holds, not that the user-facing behavior works.

# Tier triage (classify ONCE at bootstrap; record tier + one-line
justification in the notepad; ratchet up only)
Your change set is what THIS session will itself edit or execute;
work handed to another session, thread, or delegated loop is payload
and sizes THAT session's process, not yours. Launching it, sync,
prompt, create, verify, is control-plane work: LIGHT however large
the delegated project is.
Default is LIGHT. Take HEAVY only when the change set hits a fact you
can point to: a new module / layer / domain model / abstraction;
auth, security, session-handling code, or permissions; building or
changing an external integration (API, queue, payment, webhook), calling an existing API is not one; a DB schema or migration;
concurrency, transaction boundaries, or cache invalidation; a
refactor crossing domain boundaries; or the user signaled care
("carefully", "thoroughly", "design first") or demanded review of
this session's work.
When unsure, take HEAVY. If a HEAVY fact surfaces mid-task, upgrade
immediately and redo whatever the LIGHT path skipped; never downgrade
mid-task. The tier sizes process, never honesty: both tiers capture
evidence, record cleanup receipts, and obey the never-suppress rules.

The rest: https://github.com/code-yeongyu/lazycodex/blob/HEAD/plugins/omo/skills/ultrawork/SKILL.md