Agent skill

Omh Plan

[omh] Software feature or bugfix not yet planned: structured planning before execution.

Install Omh Plan

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/omh-plan .claude/skills/omh-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "omh-plan" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan into .claude/skills/omh-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-plan", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-plan -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-plan --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/omh-plan .agents/skills/omh-plan && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "omh-plan" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan into .agents/skills/omh-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-plan", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-plan -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-plan --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/omh-plan .cursor/skills/omh-plan && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "omh-plan" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan into .cursor/skills/omh-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-plan", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/rlaope/oh-my-hermes.git --path skills/omh-plan

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-plan -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-plan --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/omh-plan .gemini/skills/omh-plan && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "omh-plan" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan into .gemini/skills/omh-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-plan", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-plan

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-plan -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/omh-plan .github/skills/omh-plan && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "omh-plan" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan into .github/skills/omh-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-plan", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add rlaope/oh-my-hermes --skill omh-plan -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install rlaope/oh-my-hermes omh-plan --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/rlaope/oh-my-hermes.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/omh-plan .opencode/skills/omh-plan && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "omh-plan" agent skill from https://github.com/rlaope/oh-my-hermes/tree/main/skills/omh-plan into .opencode/skills/omh-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omh-plan", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: omh-plan
GitHub stars: 3.2k
Token cost: ~1.7k tokens
SKILL.md length: 827 words
Files: 2 (incl. references)
Skills in repo: 143
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

[omh] Software feature or bugfix not yet planned: structured planning before execution.

The user says: plan
SKILL.md covers Why This Exists, Do Not Use When, Examples and Completion Checklist, plus 5 more sections
Calls make
Implementation plan

What it does

Omh Plan is an agent skill from rlaope/oh-my-hermes. [omh] Software feature or bugfix not yet planned: structured planning before execution. Use when the user says: plan, implementation plan, make a plan, write a plan, write the plan, task breakdown, safe feature, safely add a feature.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/project-constitution.md`).

It sits in Agent Workflows, covering Planning and Task breakdown. The repository describes itself as: All in one plugin for Hermes Agent ⚚ the coding intelligence, a long-term memory system and model optimized workflow packages. The licence is MIT.

When your agent uses it

The user says: plan
Implementation plan
Safely add a feature

Example prompts

“/omh-plan”

What it can do on your machine

Read from SKILL.md and the folder at commit 41de9dc. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- make
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Omh Plan loads about 1.7k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 827 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~61
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from rlaope/oh-my-hermes at commit 41de9dc, republished under its MIT licence (© rlaope). 827 words, ~1,665 tokens.

Download SKILL.mdSave it as .claude/skills/omh-plan/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: omh-plan
description: [omh] Software feature or bugfix not yet planned: structured planning before execution. Use when the user says: plan, implementation plan, make a plan, write a plan, write the plan, task breakdown, safe feature, safely add a feature.

Plan

This is a Hermes-native plan workflow skill.

Why This Exists

plan exists to keep planning work explicit, evidence-backed, and inside the Hermes/executor boundary instead of relying on ad hoc chat narration.

Do Not Use When

The request is casual chat, a status-only acknowledgement, or another workflow has stronger routing evidence.
The user needs implementation, review, CI, merge, or external publishing evidence that has not been delegated or observed.

Examples

Good example:

Prompt: plan: handle a planning request that needs explicit evidence boundaries and a clear stop condition.
Expected behavior: Run plan only after naming the target, evidence boundary, and stop condition.
Why: The request matches the catalog use case and keeps observed evidence separate from prepared guidance.

Bad example:

Prompt: plan: treat casual chat or unaccepted work as if this workflow already produced verified results.
Expected behavior: Ask a clarification question or route to a narrower workflow instead of forcing plan.
Why: The request lacks the required inputs or would overclaim work that Hermes did not observe.

Completion Checklist

The plan names goals, non-goals, assumptions, acceptance criteria, and verification shape.
Draft recommendations, accepted decisions, and executor handoffs are separate states.
Rejected options or unresolved tradeoffs are recorded before handoff.

Recovery Notes

If acceptance criteria or verification are missing, route back to clarification before handoff.
If assumptions materially affect the plan, keep them visible and avoid treating the plan as accepted.

Workflow Lane

Current lane: Intent -> plan (oh-my-hermes, meta-router, deep-interview, context, plan, ralplan, adversarial-consensus, codebase-onboarding, +8 more) - clarify, plan, ship, or loop goals.
If intent belongs to another lane, hand back to oh-my-hermes or name the adjacent workflow.
Shared product, routing, compatibility, and evidence rules: omh-routing/references/skill-common-rail.md.

Use When

Use for structured planning when implementation is not ready to start safely, including feature work that needs a safe plan before handoff.

Strong routing signals: `plan`, `$plan`, `implementation plan`, `make a plan`, `write a plan`, `write the plan`, `task breakdown`, `safe feature`, `safely add a feature`, `add a feature`, `feature request`, `new feature`, `product triage`, `bug triage`, `issue triage`, `reproduction plan`, `workflow hub`, `coding handoff`, `project template`, `github pr workflow`, `実装計画`, `タスク分解`, `安全に機能追加`, `機能追加の計画`, `답할 차례`, `준비할 차례`, `재현 계획`, `요구사항 정리`, `작업 허브`, `작업 허브가 필요`, `상태와 다음 행동`, `프로젝트별 운영`, `实现计划`, `任务拆解`, `安全地新增功能`, `新增功能计划`

Catalog Metadata

Category: planning Phase: plan Hermes role: planner Quality tier: acceptance-gated Reasoning demand: standard

Quality bar:

Make goals, non-goals, risks, acceptance criteria, and verification shape explicit.
Where the repository declares non-negotiable principles, load references/project-constitution.md and record the check: a plan conflicting with a MUST is resolved by changing the plan, never by reinterpreting the principle.
Keep draft plans unapproved until a user or wrapper accepts them.
Only prepare coding handoff guidance after the plan is accepted.
Plan acceptance approves the plan content, not execution: after acceptance, recommend the follow-on path that fits the work's shape — ultrawork durable checkpoints for progress that must survive sessions as a checkpointed ledger, ultrawork coordinated lanes for an accepted plan split into disjoint parallel lanes, ultrawork single-owner persistence for one already-scoped task with a single owner, ultrawork for one bounded delivery cycle, or a direct selected executor/runtime handoff for a single prepared coding change — state the fit reason in one line, and start it only after the user's explicit go-ahead.

Handoff policy:

Keep planning in Hermes; if the accepted plan requires code edits, prepare a selected executor/runtime handoff after acceptance, and start a follow-on workflow engine only after the user explicitly confirms the recommended path.

Required inputs:

requirements
constraints
known facts
non-goals

Expected outputs:

plan
acceptance criteria
verification strategy

Artifact expectations:

plan artifact when durable execution will follow

Safety rules:

Do not imply hidden Hermes runtime behavior.
Use the smallest verification that can prove the claim.

Show full SKILL.md (211 more words)Show less

Runtime Evidence

Preferred harness for this skill: planning.

omh runtime record --skill plan --harness planning --status started

Record observed delegation results; otherwise return not_available or not_observed. Prepared OMH routing is not execution, review, CI, merge-readiness, or merge evidence.

When wrapper metadata includes memory_review_card/v1 or handoff_context_pack/v1, treat it as reviewed OMH-local or wrapper-supplied context only. Use conflict-free context summaries to shape plans and handoffs, but do not claim Hermes internal memory was read or changed. Preserve workflow intent and stop conditions; verify before claiming completion. Reply in the user's own words and the host's own voice: its SOUL.md persona owns reply language, tone, speech level, and sentence endings, progress updates included (where it sets no language, use the one the user wrote in), and OMH shapes structure and content only; OMH's record terms (surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in records and tool calls, never in the sentence the user reads unless they ask about one; and when a stop condition or a decision the user owns ends the turn, offer the next action as a question rather than declaring what will not be done.

Use Hermes-native subagent/delegation features when available: native subagents -> Hermes delegation when available, otherwise sequential lanes.

Shared product, compatibility, topology, memory, harness, and execution rules: omh-routing/references/skill-common-rail.md. Load it when applicable; otherwise name an unavailable capability.

Files

SKILL.md and 1 other file (references) in skills/omh-plan of rlaope/oh-my-hermes.

SKILL.md
references/project-constitution.md

Open the folder on GitHubat commit 41de9dc

Compare with similar skills

Omh Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Omh Plan compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Omh Plan this skillrlaope/oh-my-hermes	3.2k	—	~1.7k	Automated safety check: Pass	MIT	yesterday
Planning And Task Breakdownabashev/vfs-s3	106	8 repos	~1.9k	Automated safety check: Pass	Apache-2.0	3 days ago
ULW Plan Workflowcode-yeongyu/oh-my-openagent	70k	—	~3.9k	Automated safety check: Pass	Custom licence	today
Ask NavigatorYeachan-Heo/oh-my-claudecode	40k	—	~4.1k	Automated safety check: Pass	MIT	yesterday
Implementation Plan Creatortailcallhq/forgecode	7.6k	1 repos	~1.1k	Automated safety check: Pass	Apache-2.0	today
Harness PlanChachamaru127/claude-code-harness	3.2k	—	~3.7k	Automated safety check: Notes	MIT	5 days ago

Similar skills

Planning And Task Breakdown
abashev/vfs-s3
Breaks work into ordered tasks. An agent skill from abashev/vfs-s3.
106 GitHub starsUsed in 8 repos~1.9k tokens
Agent WorkflowsAuto-check passed
ULW Plan Workflow
code-yeongyu/oh-my-openagent
Explore-first planning that turns a vague or large request into one decision-complete work plan, written only after your approval and executed by a separate worker.
70k GitHub stars~3.9k tokensUpdated today
Agent WorkflowsAuto-check passed
Ask Navigator
Yeachan-Heo/oh-my-claudecode
Charts a foggy effort into a map of decision tickets on the repo's issue tracker and works through them one per session, producing decisions rather than deliverables.
40k GitHub stars~4.1k tokensUpdated yesterday
Agent WorkflowsAuto-check passed
Implementation Plan Creator
tailcallhq/forgecode
Writes a structured Markdown implementation plan with checkbox tasks, verification criteria and risks, then checks it with a validation script; no code changes.
7.6k GitHub starsUsed in 1 repo~1.1k tokens
Agent WorkflowsAuto-check passed
Harness Plan
Chachamaru127/claude-code-harness
Creates and maintains Plans.md task plans with a spec delta, updates task markers and syncs plan progress with the implementation.
3.2k GitHub stars~3.7k tokensUpdated 5 days ago
Agent WorkflowsAuto-check: notes
Plannotator Goal Setup
backnotprop/plannotator
Guides the agent from a vague objective to a written goal package under goals/, using a confirmed restatement, a browser interview, a fact sheet and a codebase pass.
9.2k GitHub stars~2.4k tokensUpdated yesterday
Agent WorkflowsAuto-check passed

More from rlaope/oh-my-hermes

All 143 skills in this repo

Omh Accessibility Audit
rlaope/oh-my-hermes
[omh] Screen-reader or keyboard accessibility gaps: prepare WCAG, keyboard, focus, screen-reader, target-size, and reflow evidence gates for UI surfaces.
3.2k GitHub stars~2.8k tokensUpdated yesterday
Auto-check passed
Omh Agent Evaluation
rlaope/oh-my-hermes
[omh] Choosing between coding agents on evidence: compare executor or agent choices on reproducible tasks using quality, cost, time, tool, and evidence metrics.
3.2k GitHub stars~2.1k tokensUpdated yesterday
Auto-check passed
Omh Agent Instructions
rlaope/oh-my-hermes
[omh] Agent instruction file for a repo -- AGENTS.md, CLAUDE.md, a Cursor rule: write or update what an agent cannot derive from the code, inside a marked region, with every command verified or…
3.2k GitHub stars~2.2k tokensUpdated yesterday
Auto-check passed
Omh Agent Ops Review
rlaope/oh-my-hermes
[omh] AI agent progress for managers: help managers inspect AI-agent progress, blockers, quality gates, and throughput levers.
3.2k GitHub stars~1.9k tokensUpdated yesterday
Auto-check passed
Omh AI Slop Cleaner
rlaope/oh-my-hermes
[omh] Messy or AI-generated code to clean up: delete AI-generated slop, dead code, and duplication while observable behavior stays identical.
3.2k GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed
Omh App Debugging
rlaope/oh-my-hermes
[omh] Application code misbehaves -- a wrong value, a flaky test, a lost update: reproduce it first, form competing hypotheses, discriminate them with the cheapest observation, and only then fix the…
3.2k GitHub stars~2.3k tokensUpdated yesterday
Auto-check passed

Questions about Omh Plan

What does Omh Plan do?

[omh] Software feature or bugfix not yet planned: structured planning before execution. Omh Plan is an agent skill from rlaope/oh-my-hermes. [omh] Software feature or bugfix not yet planned: structured planning before execution.

When should I use Omh Plan?

Omh Plan fits situations like: the user says: plan; implementation plan; safely add a feature.

How do I install Omh Plan in Claude Code?

Run `npx skills add rlaope/oh-my-hermes --skill omh-plan -a claude-code`. Or copy the skill folder (skills/omh-plan in rlaope/oh-my-hermes) into .claude/skills/omh-plan in your project. Claude Code loads it when a task matches its description.

How do I install Omh Plan in Codex?

Run `npx skills add rlaope/oh-my-hermes --skill omh-plan -a codex`. Or copy the skill folder (skills/omh-plan in rlaope/oh-my-hermes) into .agents/skills/omh-plan in your project. Codex loads it when a task matches its description.

Can I use Omh Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rlaope/oh-my-hermes --skill omh-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omh-plan, .gemini/skills/omh-plan, .github/skills/omh-plan and .opencode/skills/omh-plan in your project.

What does Omh Plan need to run?

Going by SKILL.md and its folder, Omh Plan needs the command-line tools its instructions call (make).

Does Omh Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Omh Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Omh Plan use?

Omh Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Omh Plan use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 857 tokens, read only when the agent opens those files.

What are the alternatives to Omh Plan?

Skills that share tags, products or a category with Omh Plan: Planning And Task Breakdown (abashev/vfs-s3, 106 stars), ULW Plan Workflow (code-yeongyu/oh-my-openagent, 70k stars), Ask Navigator (Yeachan-Heo/oh-my-claudecode, 40k stars) and Implementation Plan Creator (tailcallhq/forgecode, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Omh Plan?

rlaope (a GitHub user) maintains it in rlaope/oh-my-hermes, which has 3,233 GitHub stars. The repository holds 143 skills in this directory. The repository was last updated on October 8, 2026.

Source: rlaope/oh-my-hermes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Omh Plan

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Plan

Why This Exists

Do Not Use When

Examples

Completion Checklist

Recovery Notes

Workflow Lane

Use When

Catalog Metadata

Runtime Evidence

Files

Compare with similar skills

Similar skills

More from rlaope/oh-my-hermes

Related

Questions about Omh Plan