Planning
Use $deep-interview and $ralplan when the request is still fuzzy or needs approval.
The point of this project is not just to rename commands. Skills turn recurring tasks into repeatable, productized flows so Kimi CLI feels closer to an oh-my-codex-style environment.
| Skill | What it does | Why it matters |
|---|---|---|
omk setup | Installs prompts, skills, config, and local state scaffolding. | Turns a plain Kimi CLI install into an opinionated shell. |
omk doctor | Checks install, config, and runtime health. | Keeps the shell understandable when something feels off. |
$deep-interview | Clarifies scope, constraints, and missing requirements. | Moves work away from vague prompting toward deliberate planning. |
$ralplan | Creates an approved plan with structured tradeoff review. | Makes implementation less guessy and more repeatable. |
$ralph | Runs a persistent execution loop with verification. | Pushes tasks toward done, not just discussed. |
$team | Uses tmux workers for coordinated parallel work. | Adds the “multi-lane shell” feeling people expect from this kind of layer. |
Use $deep-interview and $ralplan when the request is still fuzzy or needs approval.
Use $ralph, $team, and autopilot to carry approved work forward.
Use doctor, hud, and docs when you need visibility into the runtime shell.