interview-me

Clarify ambiguous project requirements through a structured iterative interview process.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/dmarins/sdd --skill interview-me-dmarins
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/dmarins/sdd/tree/main/skills/interview-me
Command: npx skills add https://github.com/dmarins/sdd --skill interview-me-dmarins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the costly mistake of building features based on ambiguous or misaligned user requests by forcing a structured, one-question-at-a-time interview process to uncover the underlying intent.

Core Features & Use Cases

  • Intent Clarification: Uses a confidence-scoring mechanism to ensure the AI truly understands the user's goal before starting any work.
  • Assumption Exposure: Forces the AI to state its hypotheses and reasoning, allowing the user to correct misconceptions early.
  • Use Case: When a user asks to build a dashboard, this skill helps determine if they actually need a simple list or a specific data visualization, saving hours of development on the wrong solution.

Quick Start

Activate the interview-me skill to help me refine my project requirements before we start coding.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I clarify project requirements before starting software development?

You clarify project requirements by conducting a structured, one-question-at-a-time interview process to uncover underlying intent and mandate explicit confirmation of goals, constraints, and scope before implementation begins.

What is the best way to eliminate ambiguity in under-specified feature requests?

Eliminating ambiguity in feature requests requires an iterative interview process that exposes hidden assumptions and uses confidence-scoring to ensure high-confidence alignment on success criteria before any coding starts.

When do I need to use a structured discovery process for software requirements?

You need a structured discovery process during the initial definition phase when user requests lack clear success criteria, ensuring you extract true intent and avoid building the wrong solution like a complex dashboard instead of a simple list.

How does an AI confidence-scoring mechanism work for intent clarification?

A confidence-scoring mechanism for intent clarification works by forcing the system to state its hypotheses and reasoning iteratively, allowing the user to correct misconceptions early until high-confidence alignment is reached.

Can I use this iterative interview approach for any scale of project alignment?

Yes, you can use this iterative interview approach for any scale of project alignment, as it focuses on exposing assumptions and mandating explicit confirmation of scope and constraints before proceeding to implementation.

What are the limitations of using a one-question-at-a-time interview for requirements discovery?

A limitation of one-question-at-a-time requirements discovery is that it requires user patience during the initial definition phase, as the process mandates explicit confirmation of goals and constraints before any implementation can proceed.