interview
Conducts in-depth technical interviews about implementation plans. Use when the user wants to be interviewed about a plan, spec, or feature before implementation, or when they say "interview me" or "let's discuss the plan".
What this skill does
# Plan Interview Skill Conduct a thorough technical interview to refine and validate an implementation plan before coding begins. ## Instructions 1. **Read the plan file** first to understand what's being proposed 2. **Use the AskUserQuestion tool** for all interview questions 3. **Ask about these areas** (in no particular order, adapt to context): - Technical implementation details - UI/UX decisions and user flows - Concerns and potential risks - Tradeoffs and alternatives considered ## Interview Guidelines ### Question Quality - Avoid obvious questions that have clear answers in the plan - Dig into edge cases, failure modes, and implicit assumptions - Challenge decisions constructively to surface hidden complexity - Ask "what if" scenarios to stress-test the design - Probe for dependencies, performance implications, and security considerations ### Question Types to Use - "What happens when..." (edge cases) - "How would this handle..." (failure modes) - "Why did you choose X over Y?" (tradeoffs) - "What's the migration path if..." (future-proofing) - "How will users discover/understand..." (UX depth) - "What's the worst case scenario for..." (risk assessment) ### Interview Flow 1. Start with clarifying questions about the overall goal 2. Deep-dive into the most complex or risky parts first 3. Explore integrations with existing systems 4. Cover operational concerns (monitoring, debugging, rollback) 5. End with questions about success metrics and validation ### When to Stop Continue interviewing until: - All major technical decisions are validated - Edge cases and failure modes are addressed - The user feels confident about the approach - No more non-obvious questions remain ## After the Interview Once the interview is complete, write a detailed specification that incorporates: - Original plan content - Decisions made during the interview - Edge cases and how they'll be handled - Any open questions or future considerations - Implementation notes and gotchas discovered Save the spec to an appropriate location (ask the user where if unclear).
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.