skills.rest
j-cogburn
j-cogburnCOMMUNITY
Explore all skills by this author →
GitHub

interview-me

Interviews users one question at a time to extract implicit requirements and confirm intent before planning or development begins.

Updated Jun 1, 2026
Search Tags:#scope-definition#user-interview#requirement-gathering#intent-extraction#pre-planning#requirement-clarification#ambiguity-resolution
One-click install
npx skills add https://github.com/j-cogburn/d3 --skill interview-me-j-cogburn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interview-me
Source: https://github.com/j-cogburn/d3/tree/main/tests/project-t01/.d3/skills/interview-me
Command: npx skills add https://github.com/j-cogburn/d3 --skill interview-me-j-cogburn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of building misaligned solutions caused by unstated user assumptions, ambiguous requirements, and the gap between what users ask for and what they actually need. Catching these misalignments before planning or coding starts avoids costly rework and wasted effort.

Core Features & Use Cases

  • Structured Intent Interview: Guides you through a one-question-at-a-time interview process with attached hypotheses to surface hidden requirements and user priorities.
  • Confidence Tracking: Forces explicit confidence scoring on your understanding of the user's needs, with clear stop conditions to avoid premature planning.
  • Explicit Intent Confirmation: Produces a structured restatement of the user's goals, constraints, and out-of-scope items for explicit sign-off before any downstream work begins.
  • Use Case: If a user requests "a dashboard for our metrics" without context, this skill walks through targeted questions to discover if they actually need a personal experiment tracker, a team standup summary tool, or an executive reporting dashboard, ensuring you build the right thing first.

Quick Start

Use the interview-me skill to clarify the full requirements for the project you just described before moving to any planning, specification, or development work.

Frequently Asked Questions about interview-me

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

FAQPage Schema
How do I resolve ambiguous project requirements before development starts?▼

To resolve ambiguous project requirements, you need a structured user interview process that extracts unstated intent. A one-question-at-a-time workflow with confidence scoring surfaces hidden priorities and establishes shared understanding before planning or coding begins.

What is the best way to uncover true user intent during requirement gathering?▼

Uncovering true user intent requires targeted intent extraction during pre-planning. By attaching hypotheses to specific questions and tracking confidence levels, you can identify when user-stated needs diverge from actual desired outcomes and prevent building misaligned solutions.

How do I clarify underspecified build requests like 'a dashboard for our metrics'?▼

To clarify underspecified build requests, apply a structured interview workflow that asks targeted questions to discover specific use cases. This determines whether the user actually needs a personal tracker, a team summary tool, or an executive reporting dashboard before downstream work begins.

Can I use a structured interview to get explicit sign-off on project scope?▼

Yes, a structured interview can produce explicit intent confirmation. By generating a structured restatement of user goals, constraints, and out-of-scope items, you create a formal sign-off checkpoint that prevents premature planning and costly rework.

When do I need ambiguity resolution for software pre-planning?▼

Ambiguity resolution is needed when users submit underspecified build requests or when stated needs diverge from actual desired outcomes. If you face unstated assumptions and ambiguous requirements, resolving them before planning avoids wasted development effort.

What are the limitations of relying on user-stated needs for scope definition?▼

Relying solely on user-stated needs risks building misaligned solutions due to unstated assumptions and ambiguous requirements. Without explicit confidence scoring and intent confirmation, premature planning can occur, leading to costly rework and wasted effort.

Related Skills

Explore More Product & Management Skills→
JaCha00JaCha00

deep-interview

Clarify user intent through Socratic questioning to define execution-ready specifications.

Community
Advanced
julianromlijulianromli
182

prd

Generate comprehensive Product Requirements Documents with structured sections for architecture, APIs, and testing.

Community
Advanced
qa-amanqa-aman
19

uat-plan

Generates a UAT plan with test scenarios, traceability, and sign-off criteria from business requirements.

Community
Advanced
martinffxmartinffx
39

atelier-spec-product

Conduct discovery interviews to define feature scope and requirements.

Community
Intermediate