plugins/khuym/skills/swarming/SKILL.md
Use when validating approves execution. Orchestrates bounded Codex workers, local reservations, worker results, rescues, and phase handoff. Tends the swarm but never implements beads directly.
npx skillsauth add hoangnb24/skills swarmingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
If .khuym/onboarding.json is missing or stale for the current repo, stop and invoke khuym:using-khuym before continuing.
You are the orchestrator. Launch workers, monitor coordination, handle escalations, and keep the swarm moving. Do not implement beads directly; spawned workers use khuym:executing.
Same-session swarming uses:
bv for work selection and graph state.khuym/reservations.json for local file ownership[DONE], [BLOCKED], [HANDOFF], and [NOOP] resultsNo external mail server is required for the default path.
Invoke after khuym:validating says: Validation complete. Current phase passes. Invoke khuym:swarming skill.
Prerequisites:
EPIC_ID is knownnode .codex/khuym_status.mjs --json has been run when availablehistory/learnings/critical-patterns.md has been read when presentbv --robot-triage --graph-root <EPIC_ID>.references/swarming-reference.md.agent_id, agent_nickname, bead, and status in .khuym/state.json..khuym/HANDOFF.json before pausing near context limits.Load references/swarming-reference.md for spawn context, tend-loop rules, result templates, handoff content, and red flags.
assigned_bead_id from the orchestrator.send_input(...) check-ins..khuym/HANDOFF.json and pause safely.Swarming is complete when either:
Swarm execution complete for the final phase. Invoke khuym:reviewing.| File | When to Load |
|---|---|
| references/swarming-reference.md | Orchestration flow, worker prompt, result formats |
| .khuym/state.json | Runtime worker and phase state |
| .khuym/HANDOFF.json | Pause/resume artifact |
tools
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.
development
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.
development
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.
tools
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.