plan-interview
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
What this skill does
# Plan Interview Skill Transform rough plans into comprehensive, implementation-ready specifications through adaptive, structured interviews. ## When to Use - Converting a plan or idea into a detailed specification - Gathering requirements through structured questioning - Transforming rough documentation into implementation-ready specs - Ensuring all edge cases, risks, and stakeholders are considered before implementation ## Available Components ### Command: `/plan-interview:interview [plan-file]` Adaptive interview that calibrates depth based on plan complexity: | Complexity | Signals | Questions | |------------|---------|-----------| | **Simple** | Single feature, clear scope | 10-15 | | **Moderate** | Multi-component, some integrations | 18-23 | | **Complex** | Cross-system, many stakeholders | 22-28 | **Usage:** ```bash /plan-interview:interview docs/feature-plan.md # Output: docs/feature-plan-spec.md ``` ### Agent: `spec-reviewer` Autonomous quality analysis of specifications across 4 dimensions: - **Completeness** (25 pts) - All sections populated? - **Consistency** (25 pts) - No contradictions? - **Clarity** (25 pts) - No ambiguous language? - **Edge Cases** (25 pts) - Error handling defined? Triggers when you say "review my spec" or "check specification quality". ## Interview Phases 1. **Foundations & Scope** - Stakeholders, success criteria, constraints, MVP scope 2. **Technical Deep-Dive** - Architecture, data models, scalability, security 3. **User Experience** - Personas, flows, cognitive load, error recovery 4. **Risks & Tradeoffs** - Risk categorization, blast radius, contingency plans 5. **Operationalization** - Testing, deployment, monitoring 6. **Wrap-Up** (optional) - Only for complex plans with remaining gaps ## Interview Philosophy **Core Principle**: Depth over breadth. Better to deeply understand critical aspects than superficially cover everything. **Key Techniques**: - Non-obvious questions - Skip what the plan already answers - Edge probing - What happens in unusual cases? - Assumption surfacing - Make implicit beliefs explicit - Contradiction detection - Flag when answers don't align - Adaptive depth - Probe deeper on complex areas, move faster on clear ones ## Spec Output Structure Generated specs include: - Overview (problem, solution, success criteria, stakeholders) - Functional and non-functional requirements - Technical design (architecture, data models, APIs, security) - User experience (personas, flows, states, edge cases) - Risks and mitigations (risk register, tradeoffs, contingency plans) - Implementation notes (key decisions, dependencies, migration) - Operationalization (testing, deployment, monitoring) - Open questions and out-of-scope items - Phasing (MVP vs future) ## References Load these for deeper guidance during interviews: - `references/phase-1-clarifications.md` - Foundations questions and pitfalls - `references/phase-2-technical.md` - Architecture discussion patterns - `references/phase-3-ux.md` - Persona development, UX patterns - `references/phase-4-risks.md` - Risk assessment frameworks - `references/interview-techniques.md` - Cross-cutting interview skills - `references/example-spec.md` - Annotated high-quality spec example
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.