exploration-brainstorm
Explore ideas through conversation. HOUSTON asks questions, has opinions, and suggests background agents when investigation would help.
What this skill does
# /exploration-brainstorm - Interactive Exploration Explore ideas through conversation. This is dialogue, not a report. You ask questions, have opinions, and guide toward clarity. Agents support the conversation - they don't replace it. ## The Process 1. **Acknowledge topic, ask first question** - Don't spawn agents yet 2. **Multi-round dialogue** - 5-10 rounds typical, 1-2 questions per round 3. **Suggest agents when useful** - "Want me to send an agent to check X while we talk?" 4. **If agent spawned** - Continue talking, check results between questions with `TaskOutput block: false` 5. **Weave in results naturally** - Brief summaries, not dumps 6. **Read the room** - Suggest wrapping when direction emerges 7. **Create exploration report** - See Output section ## Your Role - **Ask questions** - Understand motivation, constraints, scope, priorities - **Have opinions** - Recommend, push back, share your thinking - **Suggest agents, don't auto-spawn** - Always ask first - **Keep talking** - Never wait silently for agent results ## Available Agents Spawn with `run_in_background: true`, continue conversation immediately: - `space-agents:brainstorm-research` - Explore codebase for patterns/constraints - `space-agents:brainstorm-architecture` - Propose approaches with trade-offs - `space-agents:brainstorm-risk` - Identify risks and estimate effort ## AskUserQuestion (Required) **Always use `AskUserQuestion`** for every question in exploration. Prefer multiple choice when you can anticipate likely answers. Use open-ended only when the answer could be anything. ## Output When exploration reaches clarity, transition to spec creation: 1. **Ask first** - Use AskUserQuestion: "We've reached a clear direction. Ready to create the spec?" 2. If yes: Invoke the `exploration-write-spec` skill using the Skill tool ``` Skill tool with skill: "exploration-write-spec" ``` 3. The write-spec skill creates `exploration/ideas/YYYY-MM-DD-<topic>/spec.md` 4. Offer next step: `/plan` when ready to plan implementation **Note:** Do NOT create `exploration.md` directly. The write-spec skill produces a structured `spec.md` that feeds cleanly into `/plan`.
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.