Interview users one question at a time to clarify true intent before planning.
npx skills add https://github.com/zxyycom/docnav --skill interview-me-zxyycom
Please help me install this Agent Skill. Skill: interview-me Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/interview-me Command: npx skills add https://github.com/zxyycom/docnav --skill interview-me-zxyycom
This skill extracts the user's true intent before planning, specification, or coding by conducting a one-question-at-a-time interview until the underlying goals are clear, surfacing missing who/why/success/constraint, and identifying when the user explicitly asks for an interview.
State your underspecified ask to begin the interview; the agent will publish a hypothesis and pose the first clarifying question.
High-intent search queries and answers about installing and using this skill.
To clarify project requirements before development, you conduct a one-question-at-a-time interview to surface missing who, why, and constraints. The process anchors questions to a running hypothesis, attaching a guess to each query to correct assumptions until underlying goals are clear.
Discovering true user intent for product planning involves distinguishing what users want versus what they should want. By hypothesizing and reporting confidence before questions, you close visible gaps and require explicit restatement to obtain a concrete, confirmed intent statement.
An intent discovery interview works by anchoring each clarifying question to a running hypothesis and attaching a guess to surface and correct assumptions. It requires explicit confirmation to produce a final, signed intent statement before any downstream plan or specification is created.
No, you cannot generate specifications directly without confirming the intent statement. The process requires explicit confirmation and restatement to produce a final, signed intent statement before any downstream plan or specification is created.
You need to conduct a requirements clarification interview when you have an underspecified ask before planning, specification, or coding. It identifies missing who, why, success criteria, and constraints to ensure the underlying goals are completely clear before downstream work.
zig-whatwgClarify ambiguous requests by asking one focused question at a time.
jonesrussellAnalyze project artifacts for inconsistencies, duplications, and gaps.
jlawsDiagnose projects and surface PRDs, roadmaps, and launch plans.
discountedcookieGuide iterative questioning to clarify design requirements and produce OpenSpec proposal summaries.
