How does the interview process work?

The skill reads your plan file and asks one targeted question at a time to probe for technical details, UX considerations, and potential edge cases based on your initial draft.

What triggers the Plan Interviewer skill?

You can activate the skill by using natural language triggers like 'interview me about', 'refine this plan', or 'question this spec' followed by the file path.

What happens after the interview is finished?

Once the questioning is complete and the plan is deemed solid, the skill automatically writes the refined specification back to your original file, incorporating all gathered insights.

Can I use this for existing codebases?

Yes, it is highly effective for refining the scope of refactoring tasks or new feature additions within existing projects to ensure all dependencies are considered.

Plan Interviewer

Name: Plan Interviewer
Author: aviflombaum

byaviflombaum

•

Productivity & Workflow

Refines project plans and technical specifications through guided Socratic questioning and assumption testing.

About

Plan Interviewer is a specialized Claude Code skill designed to transform rough project outlines into comprehensive, production-ready specifications. By engaging the user in a deep, one-on-one interview process, the skill probes for technical edge cases, UI/UX nuances, and architectural trade-offs that might otherwise be overlooked. It actively challenges assumptions using 'what if' scenarios to ensure the final plan is robust, logically sound, and ready for implementation before the coding phase begins.

Key Features

30 GitHub stars
MVP scope refinement to identify and prevent feature creep
Proactive identification of UI/UX edge cases and user flow bottlenecks
Deep Socratic questioning to uncover hidden technical requirements
Systematic validation of technical stacks and architectural tradeoffs
Automatic file updates that incorporate interview insights directly into specifications

Use Cases

Validating a high-level project idea before starting the development phase
Refining a vague feature request into a detailed, actionable implementation guide
Stress-testing a technical specification for potential failure points or edge cases

About

Key Features

30 GitHub stars
MVP scope refinement to identify and prevent feature creep
Proactive identification of UI/UX edge cases and user flow bottlenecks
Deep Socratic questioning to uncover hidden technical requirements
Systematic validation of technical stacks and architectural tradeoffs
Automatic file updates that incorporate interview insights directly into specifications

Use Cases

Validating a high-level project idea before starting the development phase
Refining a vague feature request into a detailed, actionable implementation guide
Stress-testing a technical specification for potential failure points or edge cases