CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plan

Lightweight planning with optional interview

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/plan/SKILL.md

The canonical home for this skill is plan in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security
Plan creates concise, actionable work plans. Auto-detects interview vs direct, supports `--interview` for Socratic clarification and `--review` for evaluation.

<Use_When>

  • Planning before implementation — "plan this", "let's plan"
  • Requirements are vague and need scoping — use --interview
  • Reviewing an existing plan — --review </Use_When>

<Do_Not_Use_When>

  • Want direct execution — execute the scoped task directly; use ultragoal only for durable goals or team for coordinated parallel work
  • Simple focused fix with obvious scope — skip planning </Do_Not_Use_When>

<Execution_Policy>

  • Auto-detect interview vs direct; --interview forces Socratic mode, --direct skips it
  • Ask one question at a time; gather codebase facts first
  • omx explore is deprecated. Use normal repository inspection for codebase facts; omx sparkshell only for explicit shell-native evidence
  • Plans must be evidence-backed: 80%+ claims cite file/line, 90%+ criteria testable
  • Right-size steps to scope; save to .omx/plans/ </Execution_Policy>

Mode Selection

ModeTriggerBehavior
Interview--interview or broad requestSocratic requirements gathering
Direct--direct or detailed requestGenerate plan immediately
Review--reviewCritic evaluation of existing plan

Interview (--interview)

  1. Classify the request and gather discoverable codebase facts before asking a question
  2. Ask one focused question for the remaining intent/preference gap through the available question surface below
  3. Build on answers; consult Analyst for hidden requirements
  4. Create plan when user signals readiness

Direct

  1. Quick analysis (optional Analyst)
  2. Generate plan immediately
  3. Optional Critic review if requested

Review (--review)

  1. Read plan from .omx/plans/
  2. Evaluate via Critic; verdict APPROVED/REVISE/REJECT
  3. Use a separate Critic reviewer when the current lane authored the plan; if independent review is unavailable, report that gap without claiming approval

Output

Every plan includes: Requirements Summary, Acceptance Criteria (testable), Implementation Steps (with file refs, adaptive count), Risks/Mitigations, Verification. Saved to .omx/plans/.

Outcome-first framing: apply outcome-first framing, concise visible updates for multi-step planning. Local overrides for the active workflow branch apply via newer user task updates. If the user says continue, continue the current branch instead of restarting.

<Tool_Usage>

  • omx explore is deprecated. Use normal repository inspection; omx sparkshell only for explicit shell-native evidence
  • In attached OMX tmux, use omx question with OMX_QUESTION_RETURN_PANE set to the current pane. Outside tmux, use native structured input when available; otherwise ask one concise plain-text question and wait for the answer
  • Use only the host's exposed native subagent tools with the installed planner/analyst/critic roles when the selected planning step needs them; report an unavailable required reviewer instead of inventing a tool </Tool_Usage>

<Escalation_And_Stop_Conditions>

  • Stop interviewing when requirements are clear — do not over-interview
  • Escalate on irreconcilable trade-offs requiring business decision
  • "just do it" / "skip planning" → continue the authorized scoped task through direct execution; use $ultragoal only when explicitly requested or required for durable goals, preserving any active workflow's gates </Escalation_And_Stop_Conditions>

<Final_Checklist>

  • Acceptance criteria testable (90%+ concrete)
  • Claims cite file/line (80%+)
  • Risks have mitigations, no vague terms
  • Plan saved to .omx/plans/ </Final_Checklist>
## Question Classification | Type | Examples | Action | |------|----------|--------| | Codebase Fact | "Where is X?" | Explore first, do not ask | | User Preference | "Priority?" | Ask through the available question surface above | | Scope Decision | "Include Y?" | Ask user |

Review Quality Criteria

CriterionStandard
Clarity80%+ claims cite file/line
Testability90%+ criteria concrete
VerificationFile refs exist
Repository

Yeachan-Heo/oh-my-codex

Path

plugins/oh-my-codex/skills/plan/SKILL.md

Last updated
First committed

Canonical home

Yeachan-Heo/oh-my-codex
In sync

since Sep 22, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.