spawn-planning-agents
Use when creating implementation plans to research codebase patterns and gather context for planning.
What this skill does
# Spawn Planning Agents Use specialized agents to gather context needed for creating detailed implementation plans. ## Planning Research Needs When planning implementations, you need: 1. **Existing code patterns** - How is similar functionality implemented? 2. **Integration points** - What files will need to change? 3. **Test patterns** - How should tests be written? 4. **Documentation** - What prior decisions or research exists? ## Agent Selection for Planning **Find what exists**: - `codebase-locator` - Find files related to the feature area - `thoughts-locator` - Find existing plans, research, or tickets **Understand patterns**: - `codebase-pattern-finder` - Find similar features to model after - `codebase-analyzer` - Understand existing architecture **Extract insights**: - `thoughts-analyzer` - Extract key decisions from prior research ## Planning Workflow 1. **Context gathering (parallel)**: - Locate existing code in the feature area - Find similar implementations to model after - Check for prior research or decisions 2. **Pattern analysis (parallel, after context)**: - Analyze architecture of similar features - Understand integration points 3. **Plan creation**: - Use findings to inform phases - Reference specific files and patterns - Include concrete examples from codebase ## Example Planning task: "Add email notifications feature" **Step 1 - Context (parallel)**: ``` Task(subagent_type="codebase-locator", prompt="Find all notification-related code") Task(subagent_type="codebase-pattern-finder", prompt="Find examples of background job handlers and email sending") Task(subagent_type="thoughts-locator", prompt="Find any research about notification systems") ``` **Step 2 - Analysis (after context)**: ``` Task(subagent_type="codebase-analyzer", prompt="Analyze how the existing SMS notification system works, including job queuing and template rendering") ``` **Step 3 - Plan with specifics**: Reference the patterns found and create phases that follow existing conventions.
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.