Menu
Use when planning has an approved work shape and needs feasibility validation before swarming.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user asks to create a persistent repo-local Codex agent, scaffold `.codex/agents/*.toml`, define a reusable specialist role, or match an agent to existing local skills and MCP servers.
Use when designing or implementing a premium animated landing page with AI-generated visuals or looping video, especially when the workflow involves Higgfield-style image and video generation, Google AI Studio-style code prompting, React or Tailwind landing-page implementation, dark-mode video blending, scroll-tied playback, aspect-ratio-matched media blocks, or motion-first section design.
Use when the user asks to fine-tune on books, create an SFT dataset from books, train a style-transfer or author-voice model, extract ePub text, segment long-form book content, or prepare literary data for LoRA or small-model training.
Bootstrap a new AI-agent session by reading the repository operating docs and rebuilding project understanding from source. Use when Codex needs to start a new conversation, get up to speed on an unfamiliar repo, read AGENTS.md and README.md completely before acting, investigate the codebase to understand the project's purpose and architecture, or turn a rough onboarding prompt into an execution-ready repo-orientation prompt.
Use when reviewing completes or work is intentionally abandoned. Extract durable patterns, decisions, and failures into history/learnings, then promote only critical reusable lessons to critical-patterns.md.
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.
| name | validating |
| description | Use when planning has an approved work shape and needs feasibility validation before swarming. |
| metadata | {"version":"1.2","position":3,"chain":"exploring -> planning -> validating -> swarming","ecosystem":"khuym","dependencies":{"beads-cli":{"kind":"command","command":"br","missing_effect":"unavailable","reason":"Validation creates and closes spike beads during gating."},"beads-viewer":{"kind":"command","command":"bv","missing_effect":"unavailable","reason":"Validation depends on bv graph checks for polishing and risk review."}}} |
If .khuym/onboarding.json is missing or stale for the current repo, stop and invoke khuym:using-khuym before continuing.
Validating is the hard gate between planning and execution. It rejects beautiful fantasy plans by requiring repo/system evidence, feasibility proof, and current-story readiness.
history/<feature>/CONTEXT.mdhistory/<feature>/discovery.mdhistory/<feature>/approach.mdphase-plan.md, or epic-map.mdcurrent-story-pack.md, phase-<n>-contract.md, or story map.beads/ for the current execution surface when beads are requiredIf any mode-required input is missing, return to khuym:planning. If the shape artifact has not been approved by the user, stop immediately.
.spikes/.Load references/validation-reference.md for the detailed checklist, repair routing, spike handling, approval gate, and subagent prompts.
NO spike result returns the workflow to khuym:planning.When the user approves, update .khuym/state.json so the next action is swarming:
{
"active_skill": "validating",
"feature_slug": "<feature-name>",
"phase": "validated",
"mode": "<mode>",
"current_work": "<story/direct/phase>",
"summary": "Current work passed feasibility validation and is ready for swarming.",
"next_action": "Invoke khuym:swarming for the validated work."
}
Then hand off: Validation complete. Current work passes. Invoke khuym:swarming skill.
| File | When to Load |
|---|---|
references/validation-reference.md | Validation phases, repairs, approval, plan-checker, bead-reviewer |