What happens if I don't finish the interview in one go?

The skill automatically saves your progress to a timestamped .interview-progress file every 3-4 questions, ensuring you don't lose your work if the session is interrupted.

What areas does the technical interview cover?

It covers critical development domains including Architecture, API design, Security, and Testing, specifically focusing on digging deeper into vague or high-risk answers.

How does Plan Interview determine the number of questions to ask?

The skill assesses the complexity of your initial input. Simple features trigger 3-4 questions, medium projects trigger 5-7, and complex system-wide changes can lead to up to 10 questions.

Can I use this on existing files or just text ideas?

Both. You can provide a file path to an existing markdown or text plan, or simply describe your concept in text for the skill to begin the interview.

Plan Interview

Name: Plan Interview
Author: GzuPark

byGzuPark

•

Collaboration Tools

Conducts deep technical interviews to uncover hidden project assumptions and generate comprehensive implementation specifications.

About

Plan Interview is a strategic Claude Code skill designed to bridge the gap between initial concepts and production-ready code. By acting as a technical interviewer, it interrogates project plans or specifications through a structured, complexity-aware workflow to identify potential edge cases, security risks, and architectural gaps. This skill simulates a rigorous peer review process, asking targeted questions one at a time to refine your ideas before implementation begins, ultimately outputting a standardized technical specification based on the interview outcomes.

Key Features

One-at-a-time technical interviewing to ensure deep focus on specific areas
1 GitHub stars
Real-time progress tracking of covered and remaining interview domains
Dynamic complexity assessment adjusting question volume to project scope
Template-based specification generation tailored to your project goals
Automatic intermediate state saving to prevent context loss during long sessions

Use Cases

Refining a vague project idea into a detailed, actionable technical specification
Identifying hidden technical debt or architectural risks before writing code
Standardizing the project planning process across a development team

About

Key Features

One-at-a-time technical interviewing to ensure deep focus on specific areas
1 GitHub stars
Real-time progress tracking of covered and remaining interview domains
Dynamic complexity assessment adjusting question volume to project scope
Template-based specification generation tailored to your project goals
Automatic intermediate state saving to prevent context loss during long sessions

Use Cases

Refining a vague project idea into a detailed, actionable technical specification
Identifying hidden technical debt or architectural risks before writing code
Standardizing the project planning process across a development team