interviewing
Systematic questioning to clarify requirements, goals, and constraints. Use when there's ambiguity about what the user wants, hidden complexity needs uncovering, or you need to understand before proceeding. Triggers on unclear requirements, vague goals, or when other skills encounter fundamental ambiguity.
What this skill does
# Interviewing ## When to Use - Requirements or goals are ambiguous - User isn't clear about what they want - Hidden complexity might derail implementation - Another skill encounters fundamental ambiguity Skip when requirements are already clear or user wants to proceed without clarification. ## Core Methodology ### Ask Non-Obvious Questions Probe deeper than surface-level: - **Why**: What problem does this solve? Why now? - **Constraints**: What would make this unacceptable? What can't change? - **Failure modes**: What's the worst case? What happens when X fails? - **Success**: How will you know this worked? What does "done" look like? - **Tradeoffs**: What are you willing to give up? Minimum viable version? - **Assumptions**: You mentioned X, but what about Y? Is that always true? ### Avoid - Restatements of what's already said - Yes/no confirmations - Generic questions that apply to anything - Leading questions ### Follow the Thread Dig deeper when answers reveal complexity. Don't jump topics when current one has unexplored depth. ### Batch Questions Use `AskUserQuestion` with `questions` array for 2-4 related questions exploring different angles of the same area. ## Saturation Stop when: - Answers stop revealing new information - You could explain requirements to someone else - User expresses readiness to proceed ## Output Summarize what you've learned: ``` **Clarified Requirements:** - **Goal**: [specific goal] - **Constraints**: [hard limits] - **Success criteria**: [how we'll know it worked] - **Key tradeoffs**: [prioritizing vs deprioritizing] - **Open questions**: [if any] ``` ## Integration | Skill | When to use interviewing first | |-------|-------------------------------| | **Brainstorming** | User unclear about *what* they want (not just *how*) | | **Technical Planning** | Requirements too vague to plan | | **Debugging** | Problem description unclear | | **Blog Writing** | Topic or purpose unclear | For writing, also ask: What's the core message? Who's the audience? What triggered this? ## Examples See `reference/examples.md` for project and writing interview flows.
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.