// Use when exploring has locked CONTEXT.md and the work needs planning before validation.
Use when the user asks to commit everything, smart commit, group commits, organize staged or unstaged changes, create logical commits, push current work, or preserve a clean commit stack from an existing working tree.
Use when starting or resuming any Khuym project session, choosing the next Khuym skill, running go mode, checking onboarding/scout state, or enforcing workflow gates. Bootstrap meta-skill for routing across the Khuym agentic development ecosystem.
Use when the user wants to turn a rough idea, vague task, feature wish, bug-fix intent, or Codex /goal objective into a clear verifiable goal prompt. Use when the user mentions goal mode, /goal, set_goal, long-running autonomous Codex work, or asks to be interviewed/grilled before creating a goal.
Create self-contained interactive HTML visual explainers that turn difficult topics, concepts, code, math, systems, or arguments into memorable explorable artifacts. Use when Codex should research a topic, choose an interaction model, and build an artifact with simulations, diagrams, charts, sliders, hover inspection, scrollytelling, or small game mechanics so readers can explore and understand the message.
Use when Codex should turn a concept, topic, tutorial, lesson, algorithm, system, workflow, or abstract idea into a playable browser game that teaches through interaction. Use for planning or implementing educational web games with the Game Studio plugin, including concept-to-mechanic translation, gameplay loop design, learning progression, and browser-game QA.
Use when planning has an approved work shape and needs feasibility validation before swarming.
| name | planning |
| description | Use when exploring has locked CONTEXT.md and the work needs planning before validation. |
| metadata | {"ecosystem":"khuym","dependencies":{"beads-cli":{"kind":"command","command":"br","missing_effect":"unavailable","reason":"Planning creates and links real bead graphs with br."},"beads-viewer":{"kind":"command","command":"bv","missing_effect":"degraded","reason":"Planning relies on graph-aware triage and validation checks."},"cass-cli":{"kind":"command","command":"cass","missing_effect":"degraded","reason":"Planning searches prior sessions to avoid re-solving problems."},"cass-memory":{"kind":"command","command":"cm","missing_effect":"degraded","reason":"Planning retrieves reusable playbook context before deep work."},"gkg":{"kind":"mcp_server","server_names":["gkg"],"config_sources":["repo_codex_config","global_codex_config","plugin_mcp_manifest"],"missing_effect":"degraded","reason":"Discovery architecture snapshots rely on gkg-backed analysis."}}} |
Planning turns locked CONTEXT.md decisions into the smallest believable path to execution. Tough work uses capability/risk epics and a current story for feasibility validation.
If .khuym/onboarding.json is missing or stale, stop and invoke khuym:using-khuym.
CONTEXT.md is source of truth.node .codex/khuym_status.mjs --json when available.Epic Map -> Current Story Pack over forced 2-4 phases.khuym:validating.Mode -> Shape -> Epic Map? -> Current Story Pack -> Beads.
Phase = optional milestone; epic = capability/risk area; story = end-to-end outcome; bead = worker task for validated work.
Load references/planning-reference.md for quality rules and artifact templates.
CONTEXT.md, read learnings.approach.md with path, risks, proof needs, files, and validating questions.khuym:validating.Planning has chosen the smallest work shape. Approve it before current story/work prep. Tough work uses an epic map; beads wait until feasibility passes.
CONTEXT.md