interview-me

Clarify and confirm software requirements through targeted questioning.

Updated May 21, 2026
One-click install
npx skills add https://github.com/danieldev24/one-for-all --skill interview-me-danieldev24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/danieldev24/one-for-all/tree/main/skills/interview-me
Command: npx skills add https://github.com/danieldev24/one-for-all --skill interview-me-danieldev24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The skill helps clarify and confirm user requirements to avoid building the wrong product or solving the wrong problem.

Core Features & Use Cases

  • Clarifies Ambiguous Requests: Guides users through a structured questioning process to elicit actual needs, not just what they think they should want.
  • Enhances User Understanding: Helps identify and resolve gaps in user understanding before development begins, reducing rework and missed requirements.
  • Use Case: When a user requests a "dashboard" without specifying for whom or why, the skill helps narrow down the requirements by asking focused questions and hypothesizing potential answers.

Quick Start

To initiate an interview, type 'interview me' and provide a context for which you require clarity.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I clarify ambiguous user requirements for software development?

To clarify ambiguous user requirements, you need a structured questioning process that elicits actual needs rather than assumed wants. This skill guides interactive discovery sessions to unpack underlying intent, preventing costly misalignments during early development phases.

What is the best way to prevent building the wrong product during the discovery phase?

The best way to prevent building the wrong product is by conducting targeted user interviews to confirm requirements before development begins. This approach identifies gaps in understanding and resolves them early, significantly reducing rework and missed requirements.

How do I unpack the underlying intent of a user's software request?

You unpack underlying intent by asking focused questions and generating hypotheses about potential answers. When a user provides vague requests like needing a dashboard, this method narrows down the specific context, target audience, and purpose.

Can I use this skill to identify gaps in user understanding before starting development?

Yes, you can use this skill to identify and resolve gaps in user understanding before development. It requires a live, interactive user to participate in the questioning process, ensuring all requirements are fully defined and confirmed prior to coding.

When do I need to use targeted questioning for software requirement clarification?

You need targeted questioning for software requirement clarification during early stage discovery and definition phases. It is essential when a user requests a feature without specifying the audience or reasoning, helping to prevent building the wrong solution.

How do I start an interactive interview to confirm software requirements?

To start an interactive interview to confirm requirements, type 'interview me' and provide the specific context for which you require clarity. The skill then initiates a structured dialogue to hypothesize answers and refine your development goals.