interview

Interview users to refine implementation plans into consolidated specifications.

6|2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/dandaka/skills --skill interview-dandaka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/dandaka/skills/tree/main/interview
Command: npx skills add https://github.com/dandaka/skills --skill interview-dandaka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementation plans and design proposals often contain gaps, ambiguous assumptions, or unexamined tradeoffs that lead to costly rework; this Skill uncovers those issues by conducting a structured, targeted interview to surface missing requirements and risks.

Core Features & Use Cases

  • Structured Questioning: Systematically explore technical implementation, UI/UX, tradeoffs, and risks with 2–3 focused questions per area.
  • Adaptive Coverage: Skip topics already answered, probe vague responses, and dive deeper on edge cases, scalability, integrations, and security concerns.
  • Output a Refined Spec: After ~8–12 questions produce a consolidated specification summarizing the plan, refined requirements, decisions, and remaining open questions.
  • Use Case: Hand over a design doc or describe a plan in chat and get a prioritized list of gaps, follow-up questions, and a ready-to-save refined specification.

Quick Start

Ask the interview skill to review the implementation plan at /path/to/plan.md and conduct a structured interview to produce a refined specification.

Frequently Asked Questions about interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an implementation plan for technical and UX gaps?

To validate an implementation plan, you can use a structured interview process that applies adaptive questioning across technical implementation, UI/UX, tradeoffs, and risks to surface missing requirements and produce a refined specification.

What is the best way to clarify project requirements before development starts?

The best way to clarify project requirements is conducting a targeted interview that probes vague assumptions and explores tradeoffs, systematically transforming ambiguous plans into a consolidated specification with documented decisions and open questions.

How many questions does it take to refine a design specification through an interview?

Refining a design specification through an interview typically takes roughly eight to twelve focused questions, systematically covering technical implementation, UI/UX, and risk assessment while skipping topics already addressed in the supplied plan.

Can I review a plan file to uncover technical risks and scalability issues?

Yes, you can review a plan file to uncover technical risks by applying iterative questioning that specifically probes edge cases, scalability limits, integrations, and security concerns to validate the implementation plan.

How do I assess tradeoffs in a software design proposal?

To assess tradeoffs in a software design proposal, conduct a structured interview that explores technical implementation and UI/UX decisions, probing vague responses to document the reasoning and surface unexamined risks in a refined specification.

What do I need to provide for a plan validation interview?

For a plan validation interview, you need to provide an implementation plan either as a file path or described directly in the conversation, allowing the adaptive questioning process to skip answered topics and focus on missing requirements.