interview-me

Extract user intent through iterative one-question-at-a-time interviews.

7|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/carl10086/ys-powers --skill interview-me-carl10086
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/carl10086/ys-powers/tree/main/skills/interview-me
Command: npx skills add https://github.com/carl10086/ys-powers --skill interview-me-carl10086

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of misaligned requirements by forcing a deep, iterative discovery process before any planning or coding begins, preventing the high cost of building the wrong solution.

Core Features & Use Cases

  • Intent Extraction: Uses a one-question-at-a-time interview method to uncover the underlying 'why' behind a user's request.
  • Hypothesis Testing: Requires the agent to state a confidence level and a guess, ensuring transparency and surfacing hidden assumptions.
  • 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 time on unnecessary development.

Quick Start

Invoke the interview-me skill to stress-test your current project requirements and ensure we are building the right thing.

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 project requirements before starting software development?

To clarify ambiguous project requirements, you can use an iterative interview process that extracts underlying intent through one-question-at-a-time sessions. This ensures high-confidence requirement alignment by stress-testing ideas before the pre-design phase begins.

What is the best way to discover the underlying intent of a feature request?

The best way to discover underlying intent is through hypothesis testing during an interactive interview. The agent states a confidence level and a guess to surface hidden assumptions, forcing a deep discovery process to uncover the specific 'why' behind a user's request.

How do I conduct a requirements discovery interview to validate project scope?

To conduct a requirements discovery interview, initiate an interactive skill that asks one question at a time, requiring active user participation to validate hypotheses. This iterative process continues until final project scope is confirmed for high-confidence alignment before implementation.

When do I need to use an iterative interview process for requirements alignment?

You need to use an iterative interview process for requirements alignment during the pre-design phase of software development when project goals are underspecified or ambiguous. It prevents the high cost of building the wrong solution by forcing deep discovery before coding begins.

Does this requirements discovery method work for validating simple dashboard requests?

Yes, this requirements discovery method works for validating simple dashboard requests by determining if you actually need a simple list or a specific data visualization. It stress-tests current project requirements interactively to ensure you are building the right thing, saving development time.