// 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 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 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 exploring has locked CONTEXT.md and the work needs planning before validation.
Use when planning has an approved work shape and needs feasibility validation before swarming.
| name | using-khuym |
| description | 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. |
| metadata | {"version":"2.2","ecosystem":"khuym","dependencies":{"nodejs-runtime":{"kind":"command","command":"node","missing_effect":"unavailable","reason":"The bootstrap scripts run in Node.js."},"beads-cli":{"kind":"command","command":"br","missing_effect":"degraded","reason":"Bead planning and execution flows rely on br."},"beads-viewer":{"kind":"command","command":"bv","missing_effect":"degraded","reason":"Triage and readiness checks rely on bv robot commands."},"cass-cli":{"kind":"command","command":"cass","missing_effect":"degraded","reason":"Session-history lookups are part of the default workflow."},"cass-memory":{"kind":"command","command":"cm","missing_effect":"degraded","reason":"Memory context retrieval is part of the default workflow."},"bash-shell":{"kind":"command","command":"bash","missing_effect":"degraded","reason":"Dependency-contract verification runs bash helper scripts."},"gkg-cli":{"kind":"command","command":"gkg","missing_effect":"unavailable","reason":"Supported-repo planning may require gkg index and gkg server start during session readiness."},"gkg-mcp":{"kind":"mcp_server","server_names":["gkg"],"config_sources":["repo_codex_config","global_codex_config","plugin_mcp_manifest"],"missing_effect":"unavailable","reason":"Supported-repo planning and exploration depend on gkg-backed architecture intelligence."}}} |
Bootstrap meta-skill. Load this first in Khuym repos. It checks onboarding, reads runtime state, selects the next skill, and protects the human approval gates.
For full routing tables, go-mode detail, communication standards, and file maps, open references/routing-and-contracts.md.
Before normal bootstrap, verify Node.js and repo onboarding.
node --version.
node scripts/onboard_khuym.mjs --repo-root <repo-root>
status = "up_to_date": continue.status = "warning" in details.dependency_warning: continue in degraded mode, but report affected skills and this exact split:
Missing commands: ...Missing MCP server configuration: ...--apply after approval.requires_confirmation = true: explain that existing compact_prompt will be preserved unless the user explicitly approves replacement.--allow-compact-prompt-replace after explicit approval.Onboarding manages root AGENTS.md, repo-local .codex/ guardrails, .khuym/onboarding.json, .khuym/state.json, and the local reservation helper. If onboarding is not complete, do not continue into the rest of the Khuym workflow.
After onboarding succeeds, run the read-only scout whenever available:
node .codex/khuym_status.mjs --json
Use it to orient on onboarding health, gkg readiness, .khuym/state.json, .khuym/HANDOFF.json, and recommended next reads.
For active worker coordination, inspect reservations:
node .codex/khuym_reservations.mjs list --active-only --json
If .khuym/HANDOFF.json exists, surface it to the user and wait for confirmation before resuming.
Treat gkg as a first-class discovery dependency for supported repos.
gkg index <repo-root> and gkg server start before planning.Use the scout's supported_languages and primary_supported_language fields instead of guessing.
Every packaged Khuym skill must declare one of three dependency states:
metadata.dependencies.<dependency-id> with kind: command, command, truthful missing_effect, and reason.metadata.dependencies.<dependency-id> with kind: mcp_server, server_names, config_sources, truthful missing_effect, and reason.metadata.dependencies: [].Use dependency IDs as mapping keys instead of YAML arrays of objects:
metadata:
dependencies:
beads-cli:
kind: command
command: br
missing_effect: unavailable
reason: The skill reads and updates beads.
If the normal operator path uses both a CLI and MCP server for the same product, declare both separately. For example, using-khuym depends on gkg CLI readiness commands and the gkg MCP server for architecture discovery.
Do not leave a packaged skill with an undeclared dependency posture.
When changing packaged Khuym skills, keep docs and live dependency reporting aligned by running:
node plugins/khuym/skills/using-khuym/scripts/test_onboard_khuym.mjs
bash scripts/check-markdown-links.sh plugins/khuym/skills/using-khuym/SKILL.md
bash scripts/sync-skills.sh --dry-run
khuym:using-khuym
-> khuym:exploring
-> khuym:planning
-> khuym:validating
-> khuym:swarming
-> khuym:executing
-> khuym:reviewing
-> khuym:compounding
Supporting skills:
khuym:writing-khuym-skills: improve or create Khuym skills.khuym:debugging: root-cause blocked beads and execution failures.khuym:gkg: codebase intelligence after gkg readiness is green.khuym:exploringkhuym:planningkhuym:planning in small_change modekhuym:reviewingkhuym:compoundingkhuym:writing-khuym-skillskhuym:debugging/go or full pipeline: go mode.khuym/HANDOFF.json, present state, wait for user confirmationWhen in doubt, invoke khuym:exploring first.
small_change: at most 3 files, no API/data model change, low risk, no gray areas. Still run planning and validating.standard_feature: normal default Khuym chain; use a phase plan or epic map, whichever explains the work honestly.high_risk_feature: cross-cutting or hard-to-reverse work; default to epic map, feasibility proof, explicit spikes, and slower approval.Go mode chains all skills but still has exactly four human gates:
CONTEXT.md before planning.Never skip these gates. Load references/go-mode-pipeline.md for the full sequence.
.khuym/HANDOFF.json and pause.CONTEXT.md is the source of truth.history/learnings/critical-patterns.md is mandatory context before planning or executing..khuym/onboarding.json: onboarding status and managed versions.khuym/state.json: runtime state for agents, tools, and humans.khuym/HANDOFF.json: pause/resume data.khuym/reservations.json: local file reservations.codex/khuym_status.mjs: read-only scout.codex/khuym_reservations.mjs: reservation helperhistory/<feature>/CONTEXT.md: locked decisions and source of truth.beads/: Beads task graphEach skill reads upstream artifacts and writes for downstream:
CONTEXT.mdEvery skill ends with an explicit handoff: [Outcome]. Invoke [next-skill] skill.
CONTEXT.md existsstate.json after phase transitionsHANDOFF.json