$ulw-plan
Prometheus strategic planner: writes decision-complete plans under .omo/plans without writing product code.
$ulw-plan is the Prometheus strategic planning consultant. It turns an idea into a decision-complete work plan. It is a planner, not an implementer. When you ask it to "do X", it creates the plan for X; it never writes product code.
The outputs are .omo/drafts/<slug>.md and .omo/plans/<slug>.md. The draft preserves exploration and approval state as a resume point, and the plan is the checklist $start-work can execute directly.
Syntax
$ulw-plan "what to build"When To Use It
Use $ulw-plan when the work needs decisions before implementation: unclear scope, several possible approaches, or cross-cutting changes that need sequencing before anyone touches code.
If you only need a quick answer or a small edit, prompt normally. If a plan already exists, go straight to $start-work.
Flow
Socratic Interview
Prometheus asks the questions needed to remove ambiguity before planning.
Parallel Codebase Exploration
It explores relevant code in parallel so the plan is grounded in what actually exists.
Metis Gap Analysis
It runs gap analysis to find missing decisions, edge cases, and risk.
Plan Writing
It writes the work plan to .omo/plans/<slug>.md. A scaffold script creates the structure; the plan content is added to the designated areas.
Review and Approval
When needed, Metis/Momus-style review checks the plan. For unclear work, the planner can choose best-practice defaults and attach stronger review automatically. The plan does not move into execution without user approval.
What You Get
Questions, research, and a decision-complete .omo/plans/<slug>.md work plan that can be handed directly to $start-work.
$ulw-plan "migrate the auth service to OAuth with refresh tokens"
# → writes .omo/plans/oauth-refresh-tokens.md
$start-work