OMX
Oh My CodeXv0.14.0

planner

Task sequencing agent that turns a specification into an actionable, file-level execution plan with acceptance criteria.

The planner agent converts an implementation request into a concrete, step-by-step work plan ready for immediate execution. It inspects the repository before asking questions, right-sizes the step count to actual scope, and produces acceptance criteria that are specific enough to drive verification. Planning and implementation are kept strictly separate — planner writes plans, not code.

Role

  • Decompose a specification into ordered tasks that name exact files, functions, and expected outcomes
  • Write plans to .omx/plans/*.md and surface open questions to .omx/plans/open-questions.md
  • Derive codebase facts from direct inspection rather than user guesses
  • Include a consensus-mode RALPLAN-DR and ADR block when invoked through $ralplan

When invoked

  • By $autopilot and $ralplan after intent is gathered and before execution begins
  • By $plan when a user asks to plan a feature, refactor, or initiative
  • When the scope of a request is ambiguous and needs scoping before an executor is assigned
  • When a ralph loop stalls and needs a fresh sequencing pass

Inputs

  • User request or issue description
  • Repository contents inspected directly via Glob, Grep, and Read
  • Any existing .omx/plans/ or .omx/state/ context from the active session

Outputs

  • A plan file at .omx/plans/{name}.md with an adaptive step count, target files, and testable acceptance criteria
  • A brief plan summary confirming scope, estimated complexity, and key deliverables
  • In consensus mode: RALPLAN-DR principles and drivers, ADR with alternatives and rationale

Limits

  • Does not write or edit any source files — plan production only
  • Does not default to exactly five steps; step count matches the actual scope
  • Does not finalize a plan until the user confirms intent or an explicit proceed signal is given
  • architect — reviews system boundaries and design tradeoffs within the plan
  • analyst — clarifies requirements and acceptance criteria before planning
  • executor — consumes the finished plan and carries it to a verified commit
Was this page helpful?

On this page