start-work

To execute a Prometheus work plan in Claude Code, invoke the start-work command with your plan name. It orchestrates the end-to-end execution from planning to completion while coordinating parallel subagents.

Boulder state management tracks plan progression by updating a state file located at .omo/boulder.json. It enforces safe, auditable advancement with mandatory checks and ledger entries to preserve reproducibility.

Yes, you can run parallel subagents and maintain an evidence ledger. The execution supports Stop-hook continuation to handle long-running workflows and ensures all plan updates are auditable.

A dedicated git worktree is optional for starting a work plan. You can provide a worktree path using the --worktree flag to isolate worktree-aware planning, but it is not strictly required.

The session-scoped codex prefix enforces workflow rules by mandating prefixed sessions during plan execution. This ensures safe, auditable plan progression with mandatory checks and continuous ledger entries.

Plan orchestration is limited to plans stored under the .omo/plans directory. It requires strict adherence to mandatory checks and ledger entries, meaning any workflow bypassing these rules cannot be safely advanced.