dispatching-parallel-agents
Use when there are multiple independent subtasks that can progress in parallel without overlapping ownership or blocking the next local step
What this skill does
# Dispatching Parallel Agents ## Overview Use Codex subagents to accelerate sidecar work, not to outsource thinking on the critical path. **Core principle:** Keep the next blocking step local. Delegate bounded work that can run in parallel without shared write ownership. ## When to Use Use this skill when: - There are 2 or more independent questions or implementation slices - One subtask does not need the result of another - You can assign clear file or responsibility boundaries Do not use this skill when: - The next action is blocked on the delegated result - Multiple agents would need to edit the same files - The problem is still too unclear to split safely ## Agent Types - `explorer`: focused codebase questions, read-only analysis, fast context gathering - `worker`: implementation or fixes with explicit file ownership ## Workflow 1. Decide the immediate local step first. 2. Identify sidecar tasks that are concrete, independent, and useful. 3. Give each agent one clear responsibility. 4. State file ownership for code changes. 5. Continue local work immediately instead of waiting by reflex. 6. Integrate results only after reviewing what changed. ## Good Delegation Units - "Inspect how config is loaded in `bin/bin/claude-bootstrap` and report the relevant call chain" - "Add tests for `scripts/sync-codex.sh`; worker owns new test fixture files only" - "Draft Codex-native replacement text for one skill directory" ## Bad Delegation Units - "Figure out the whole feature" - "Fix everything failing" - Two workers editing the same module tree - Delegating a task and then idling until it returns ## Prompt Ingredients Every spawned agent should get: - The exact goal - The reason this subtask matters - Ownership boundaries - Constraints - The output you need back For workers, explicitly say: - which files or module they own - that they are not alone in the codebase - that they must not revert unrelated changes ## Integration Rules - Prefer a few high-quality agents over many vague ones. - Do not duplicate delegated work locally. - Use `wait` only when the result is needed now. - Close finished agents you no longer need. - Re-run verification after integrating worker output. ## Red Flags - Delegating the very next blocker and then stalling - Overlapping write scopes - Repeatedly spawning agents to compensate for a vague prompt - Trusting agent success claims without local verification - Parallelizing work that is actually one coupled change
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce 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).
relationship-science-coach
IncludedUse 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.
building-sf-integrations
IncludedSalesforce 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).
venue-templates
IncludedAccess 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.
let-fate-decide
IncludedDraws 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.
net-ops
IncludedCross-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.