Ported from oh-my-codex prometheus-strict. OMX runtime conventions ($macro invocation, omx CLI, .omx/ state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list, .workbuddy/memory).

Prometheus Strict

Clean-room planning workflow inspired by the high-level OMO Prometheus concept only. It reimplements the idea under this repository's MIT-licensed skill conventions. It does not copy implementation, prompts, wording, control flow, or runtime code from OMO.

Credit: Inspired by OMO Prometheus (code-yeongyu/oh-my-openagent), reimplemented from concept under MIT.

Purpose

Prometheus Strict creates a rigorous plan before execution when ambiguity is still risky. It separates three planning voices: Metis clarifies requirements, Momus challenges assumptions and validation gaps, and Oracle synthesizes the handoff-ready plan.

The output is a planning-only artifact for ultragoal and, when independent lanes are justified, team. When a durable artifact is useful, store the final plan under .omw/prometheus-strict/<slug>.md.

Use When

• The task is important enough that a shallow plan could produce wrong work.
• Requirements are partially known but acceptance criteria, boundaries, risks, or validation are incomplete.
• The user wants a strict interview before execution.
• A future ultragoal story needs durable scope, tests, and handoff sequencing.
• A team split may be needed, but lanes are not yet safe to assign.