planner
Task sequencing agent that turns a specification into an actionable, file-level execution plan with acceptance criteria.
The planner agent turns an implementation request into a concrete, step-by-step plan you can execute right away. It reads the repository directly, sizes the step count to the real scope of the work, and writes acceptance criteria sharp enough to verify against. The boundary is firm. Planning and implementation stay separate, so the planner produces plans, never code.
Role
- Decompose a specification into ordered tasks that name exact files, functions, and expected outcomes
- Write plans to
.omx/plans/*.mdand 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
| Situation | How it's triggered |
|---|---|
Execution planning phase in $autopilot and $ralplan | Automatic |
Planning a feature, refactor, or initiative via $plan | Direct request |
| When request scope is ambiguous and scoping is needed before assigning an executor | Direct request |
| When a ralph loop stalls and sequencing needs to be reworked | Delegated from ralph |
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}.mdwith an adaptive step count, target files, and acceptance criteria - A 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