interview
Interview users in-depth about their plans using probing, non-obvious questions. Use when user says "/interview", "interview me", "question my plan", "probe my idea", "challenge my assumptions", or wants deep exploration of a plan before implementation.
What this skill does
# Plan Interview Skill This skill helps you thoroughly explore and stress-test plans through in-depth questioning. ## When to Use This Skill Use this skill when: - A user has outlined a plan and wants it challenged - You need to uncover hidden assumptions or risks - A plan needs to be fleshed out before implementation - The user wants to think through edge cases and tradeoffs ## Process 1. **Review Context** - Read the entire conversation to understand the plan being discussed - Identify the core goals, constraints, and proposed approach 2. **Interview In-Depth** - Use the AskUserQuestion tool to probe the plan - Ask about anything relevant: technical implementation, UI/UX, concerns, tradeoffs, edge cases, assumptions, risks, dependencies - Make questions non-obvious - probe deeper into things they might not have considered - Challenge assumptions directly - Ask about the hard parts 3. **Continue Until Complete** - Keep interviewing until the plan is fully fleshed out - Don't stop after surface-level questions - Dig into specifics and corner cases 4. **Summarize** - Once complete, re-iterate the full plan incorporating everything discussed - Highlight key decisions made and risks identified ## Question Categories Consider probing these areas: - **Technical**: Architecture, scalability, performance, security - **UX**: User flows, error states, edge cases, accessibility - **Dependencies**: External services, libraries, team coordination - **Risks**: What could go wrong? What's the fallback? - **Assumptions**: What are we taking for granted? - **Scope**: What's in/out? Where are the boundaries? - **Maintenance**: How will this evolve? Who maintains it? ## Key Principles - **Be thorough** - Don't accept surface-level answers - **Challenge assumptions** - Question things that seem "obvious" - **Explore failure modes** - What happens when things go wrong? - **Stay curious** - Follow interesting threads deeper
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.