$start-work

$start-work executes a Prometheus work plan until every top-level checkbox is done. The target is .omo/plans/<slug>.md, and progress is stored in .omo/boulder.json.

Syntax

$start-work [plan-name] [--worktree <absolute-path>]

• plan-name is optional. It can be the file name or partial name of the plan under .omo/plans/<slug>.md.
• --worktree <absolute-path> is optional. It runs the work inside an isolated git worktree.

How It Works

• Boulder state in .omo/boulder.json survives turns and sessions, so progress is not lost between runs.
• A Stop-hook re-injects the next turn until the plan is done; the loop continues itself.
• Independent subtasks fan out to parallel subagents.
• It adds five evidence gates on top of strict TDD: reread the plan, automated verification, manual QA, adversarial QA, and cleanup.
• Each checked box records evidence in .omo/start-work/ledger.jsonl.
• The executor does not trust a child task's "done" report by itself. It marks a checkbox complete only after independent verification passes.

If the user explicitly invokes $start-work without an available plan, the latest workflow first bootstraps $ulw-plan to create an executable plan, then moves into execution.

Completion

When every checkbox is checked, $start-work prints an ORCHESTRATION COMPLETE block.

ORCHESTRATION COMPLETE

Typical Flow

$ulw-plan "add OAuth login with refresh tokens"

$start-work oauth-refresh-tokens

Related Docs