plan
SkillDev toolsThe plan skill is a lightweight planning tool for AI coding agents. It turns vague feature ideas into short, evidence-based coding plans before any code is written. The plan skill can ask clarifying questions one at a time or generate a plan directly, and it saves each plan to .omx/plans/.
Available today. Use it from your connected AI after setup.
No other account needed.
Have a repository or project where the agent can inspect codebase facts.
Then ask your AI: use the plan skill
What your AI can do with it
- Create concise work plans before implementation
- Ask clarifying questions one at a time with --interview
- Generate a plan directly with --direct
- Review an existing plan with --review
- List requirements, testable acceptance criteria, and implementation steps
- Save plans to .omx/plans/
Getting started
- Have a repository or project where the agent can inspect codebase facts.
- Add the plan skill to your agent's available skills.
- Ask the agent to plan a feature, or invoke the skill with --interview for clarifying questions.
- Review the saved plan in .omx/plans/ before starting implementation.
What this skill tells your AI
The instructions your AI receives, as published by yeachan-heo/oh-my-codex in skills/plan/SKILL.md and read by ahel’s review.
<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
ultragoalonly for durable goals orteamfor coordinated parallel work - Simple focused fix with obvious scope — skip planning </Do_Not_Use_When>
<Execution_Policy>
- Auto-detect interview vs direct;
--interviewforces Socratic mode,--directskips it - Ask one question at a time; gather codebase facts first
omx exploreis deprecated. Use normal repository inspection for codebase facts;omx sparkshellonly 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
| Mode | Trigger | Behavior |
|---|---|---|
| Interview | --interview or broad request | Socratic requirements gathering |
| Direct | --direct or detailed request | Generate plan immediately |
| Review | --review | Critic evaluation of existing plan |
Interview (--interview)
- Classify request; ask one focused question via
omx question - Gather codebase facts first, then ask informed follow-ups
- Build on answers; consult Analyst for hidden requirements
- Create plan when user signals readiness
Direct
- Quick analysis (optional Analyst)
- Generate plan immediately
- Optional Critic review if requested
Review (--review)
- Read plan from
.omx/plans/ - Evaluate via Critic; verdict APPROVED/REVISE/REJECT
- If author == reviewer, hand off to
$code-review
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 exploreis deprecated. Use normal repository inspection;omx sparkshellonly for explicit shell-native evidence- Use
omx questionfor interview questions; plain text only as fallback - Use
ask_codexwithplanner/analyst/criticas needed </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" → hand off to
$ultragoal</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>
Review Quality Criteria
| Criterion | Standard |
|---|---|
| Clarity | 80%+ claims cite file/line |
| Testability | 90%+ criteria concrete |
| Verification | File refs exist |
Signals
- GitHub stars
- 33k
- Forks
- 3k
- Last commit
- Oct 2026
Questions
- What is the plan skill?
- A skill that helps an AI agent create concise, evidence-based coding plans before writing code. It can ask clarifying questions or generate a plan directly, and saves plans to .omx/plans/.
- How do I use the plan skill?
- Ask the agent to plan a feature, or invoke the skill with --interview for Socratic clarification, --direct to skip questions, or --review to evaluate an existing plan.
- Where are plans saved?
- Plans are saved to .omx/plans/.
- What does a plan include?
- Each plan includes a requirements summary, testable acceptance criteria, implementation steps with file references, risks and mitigations, and verification notes.
- When should I not use the plan skill?
- Skip planning for a simple focused fix with obvious scope, or when you want direct execution. Use ultragoal for durable goals or team for coordinated parallel work.
Advanced
- Item type
- skill
- Key
plan-yeachan-heo- Source
- github.com/yeachan-heo/oh-my-codex