Skip to content
Skill

Omk planning

Full plan lifecycle: deep understanding → write plan with TDD checklist → parallel review → Ralph Loop execution

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
107
Last commit
8 months ago
License
MIT
Listing updated
today

When your agent uses it

Full plan lifecycle: deep understanding → write plan with TDD checklist → parallel review → Ralph Loop execution. Trigger when user says 'plan', 'design', 'implement', 'build', 'architect', '@plan', '@execute', or describes a multi-step task that needs structured breakdown. Also trigger for feature requests, system redesigns, or migration projects.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (26 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

Copy the skill folder to ~/.claude/skills/omk-planning to use it in all your projects:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/omk-planning &&
cp -R "$tmp/skills/omk-planning" ~/.claude/skills/omk-planning &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/omk-planning inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/omk-planning to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/omk-planning &&
cp -R "$tmp/skills/omk-planning" ~/.agents/skills/omk-planning &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/omk-planning inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/omk-planning to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/omk-planning &&
cp -R "$tmp/skills/omk-planning" ~/.cursor/skills/omk-planning &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/omk-planning inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/KaimingWan/oh-my-kiro.git --path skills/omk-planning

Or copy the folder to ~/.gemini/skills/omk-planning yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/omk-planning:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/omk-planning &&
cp -R "$tmp/skills/omk-planning" ~/.copilot/skills/omk-planning &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/omk-planning inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/KaimingWan/oh-my-kiro.git

Then copy oh-my-kiro/skills/omk-planning into your agent's skills folder as omk-planning. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Omk planning FAQ

How do I install Omk planning in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/omk-planning to use it in all your projects, or to .claude/skills/omk-planning in one project.

Does Omk planning run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Omk planning?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

More from KaimingWan/oh-my-kiro

  1. Distill a top-level principle into knowledge/rules.md

    • Open source
    • 107 GitHub stars
  2. Enforces coding best practices: deep-read before modify, LSP-first navigation, TDD red-green-refactor, minimal changes, self-review, verific

    • Open source
    • 107 GitHub stars
  3. Fetch current library/framework documentation via Context7

    • Open source
    • 107 GitHub stars
    • Databases
  4. Systematic debugging: reproduce → hypothesize → verify → fix

    • Open source
    • 107 GitHub stars
  5. Branch completion workflow: verify tests → present 4 options (merge/PR/keep/discard) → execute → cleanup worktree

    • Open source
    • 107 GitHub stars
  6. Capture knowledge into episodes.md

    • Open source
    • 107 GitHub stars