swarming

Included with Lifetime

$97 forever

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.

General

What this skill does

# Swarming

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`.

## Coordination Substrate

Same-session swarming uses:

- beads and `bv` for work selection and graph state
- Codex subagents for bounded parallel execution
- `.khuym/reservations.json` for local file ownership
- the parent Codex thread for `[DONE]`, `[BLOCKED]`, `[HANDOFF]`, and `[NOOP]` results

No external mail server is required for the default path.

## When to Use

Invoke after `khuym:validating` says: `Validation complete. Current phase passes. Invoke khuym:swarming skill.`

Prerequisites:

- current-phase beads are approved and open
- `EPIC_ID` is known
- `node .codex/khuym_status.mjs --json` has been run when available
- `history/learnings/critical-patterns.md` has been read when present

## Operating Contract

1. Confirm readiness with `bv --robot-triage --graph-root <EPIC_ID>`.
2. Sweep expired reservations.
3. Choose each ready bead parent-side, then spawn bounded worker subagents with `references/swarming-reference.md`.
4. Record `agent_id`, `agent_nickname`, bead, and status in `.khuym/state.json`.
5. Tend the live graph, reservations, and worker results until the phase is clean.
6. Write `.khuym/HANDOFF.json` before pausing near context limits.
7. Run final graph, reservation, and quality checks before handing off.

Load `references/swarming-reference.md` for spawn context, tend-loop rules, result templates, handoff content, and red flags.

## Hard Rules

- Never spawn workers before validation approves execution.
- Never let workers pick beads themselves; pass one explicit `assigned_bead_id` from the orchestrator.
- Never let workers edit without local reservations.
- Do not resolve file conflicts by asking workers to be careful; adjust reservations or bead scope.
- Silence alone is not failure. Do not send routine mid-flight `send_input(...)` check-ins.
- Reserve interrupts for explicit user aborts or confirmed deadlocks where the user wants preemption.
- If context usage passes roughly 65%, write `.khuym/HANDOFF.json` and pause safely.

## Completion Signal

Swarming is complete when either:

- the current phase is executed and the workflow returns to planning for the next phase, or
- the final phase is executed and the user can be told: `Swarm execution complete for the final phase. Invoke khuym:reviewing.`

## Reference Files

| 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 |

Files: 2

Size: 6.9 KB

Complexity: 25/100

Category: General

Source: https://github.com/hoangnb24/skills/tree/main/plugins/khuym/skills/swarming

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts