plan-interview

Included with Lifetime

$97 forever

Conduct technical interviews about project plans to uncover hidden assumptions and identify potential issues before implementation. Use when the user wants to be interviewed about a plan, spec, or project idea.

General

What this skill does


# Plan Interview

Conduct in-depth technical interviews about project plans to deeply
understand implementation details, uncover hidden assumptions,
and identify potential issues before implementation begins.

**Language:** Match the user's input language.
Use explicitly requested language if specified.

## Workflow

### Step 1: Understand Input

Input: `$ARGUMENTS`

- **File path** (contains `/` or ends with `.md`, `.txt`)
  -> Read the file, use Glob for related files
- **Text description** -> Use directly as project concept

### Step 2: Assess Complexity

| Complexity | Indicators                           | Questions |
| ---------- | ------------------------------------ | --------- |
| Simple     | Single feature, clear scope          | 3-4       |
| Medium     | Multiple features, some integrations | 5-7       |
| Complex    | System-wide, many integrations       | 8-10      |

### Step 3: Conduct Interview

Use AskUserQuestion tool. Ask ONE question at a time.

For question areas,
see [references/interview-areas.md](references/interview-areas.md).

**Progress Tracking:** Display after each question:

```text
[Progress: 2/6 | Covered: Architecture, API | Remaining: Security, Testing]
```

**Guidelines:**

- Ask meaningful follow-up questions
- Dig deeper on vague answers
- Challenge assumptions respectfully
- Skip non-applicable areas

**Intermediate Save:** Every 3-4 questions,
save to `.interview-progress-<timestamp>.md`:

- Questions asked and responses
- Areas covered and remaining

**Completion:** Interview ends when:

1. All relevant areas covered, OR
2. Maximum questions (10) reached, OR
3. User requests to end

Before ending:
"I've covered [areas]. Anything else before writing the specification?"

### Step 4: Write Specification

Use template from [references/spec-template.md](references/spec-template.md).

**Output location:**

- File input -> Same directory with `-spec` suffix
- Text input -> Ask user, default `./specs/<project-name>-spec.md`

**Cleanup:** Delete `.interview-progress-*.md` after successful spec generation.

## Triggers

This skill activates when users want to:

- Be interviewed about a project plan or specification
- Uncover hidden assumptions in their implementation plan
- Get structured feedback on a project idea before coding
- Generate a detailed specification from a concept

## Anti-Patterns

- **Asking obvious questions**: Don't ask what's already in the plan
- **Rushing through areas**: Ensure clarity before moving on
- **Ignoring context**: Adapt questions to project type
- **Skipping confirmation**: Always confirm before ending

## Extension Points

1. **Custom interview areas**: Add domain-specific areas
   in references/interview-areas.md
2. **Template customization**: Modify spec template for organization standards

## Design Rationale

**Why dynamic question count?** Fixed counts don't fit all projects.
Simple features need fewer questions;
complex systems need thorough exploration.

**Why intermediate saves?** Long interviews risk context loss.
Periodic saves preserve progress and enable session recovery.

**Why separate references?** Keeps SKILL.md lean.
Question lists and templates are loaded only when needed.

Files: 3

Size: 6.9 KB

Complexity: 26/100

Category: General

Source: https://github.com/gzupark/claude-plugin-pack/tree/main/plugins/hello-world/skills/plan-interview

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts