interview

Identify ambiguities in product plans through structured one-question-at-a-time interviews.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/dazuck/claude-code-skills --skill interview-dazuck
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview
Source: https://github.com/dazuck/claude-code-skills/tree/main/skills/interview
Command: npx skills add https://github.com/dazuck/claude-code-skills --skill interview-dazuck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies and surfaces ambiguities in product plans and PRDs by guiding a structured, one-question-at-a-time interview.

Core Features & Use Cases

  • Systematic ambiguity discovery during PRD drafting and planning sessions.
  • Guided questioning across categories: technical implementation, UI/UX decisions, dependencies and constraints, edge cases.
  • Structured summary generation that records decisions, clarifications, and remaining questions.

Quick Start

Run: /interview plans/prd.md

Frequently Asked Questions about interview

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

FAQPage Schema
How do I identify ambiguities in a product plan or PRD?

To identify ambiguities in a PRD, use a structured interview process that asks targeted questions one at a time across technical implementation, UI/UX, dependencies, and edge cases. This systematically surfaces unresolved planning issues.

What is the best way to conduct a requirements gathering interview for feature planning?

The best way to conduct a requirements interview for feature planning is to follow a disciplined protocol: ask a single targeted question at a time, dive deeper on the answers, track resolved items, and produce a structured summary of decisions.

Can I use a structured interview to review edge cases in software project planning?

Yes, you can use a structured interview to review edge cases in software project planning. It guides questioning across specific categories including technical implementation, UI/UX decisions, dependencies, and constraints to ensure edge cases are examined.

How do I track resolved decisions and remaining questions during a stakeholder review?

You can track resolved decisions and remaining questions during a stakeholder review by using a guided interview protocol that monitors answers and produces a structured summary recording all clarifications and outstanding items.

Does this structured interview approach work for UX design planning?

Yes, this structured interview approach works for UX design planning. It is explicitly applicable to PRD drafting, feature planning, and requirements gathering across UX designs, helping to surface ambiguities in UI/UX decisions.