Extract underlying user intent through iterative, hypothesis-driven questioning.
npx skills add https://github.com/mymx2/foreman --skill interview-me-mymx2
Please help me install this Agent Skill. Skill: interview-me Source: https://github.com/mymx2/foreman/tree/main/.agents/skills/interview-me Command: npx skills add https://github.com/mymx2/foreman --skill interview-me-mymx2
This skill prevents the costly mistake of building features based on ambiguous or conventional requests by uncovering the user's actual underlying needs before any planning or coding begins.
Invoke the interview-me skill to help clarify the requirements for the new project before we start drafting any specifications.
High-intent search queries and answers about installing and using this skill.
You clarify project requirements by conducting an iterative, hypothesis-driven interview that asks one question at a time to surface hidden assumptions and validate the user's true intent before development begins.
Prevent building the wrong features by forcing the AI to state its hypotheses and confidence levels, making hidden assumptions visible and testable before you finalize a scoped statement of intent.
You need a discovery interview during the initial software definition phase when a user's stated request lacks sufficient context or specificity, requiring multi-turn interaction to validate assumptions and confirm a scoped intent.
Assumption surfacing works by requiring the AI to explicitly state its hypotheses and confidence levels during the interview, making hidden assumptions visible and testable to resolve ambiguity in project requirements.
No dependencies are required to run iterative intent discovery interviews; the skill operates independently to extract underlying user intent through multi-turn, hypothesis-driven questioning during the initial project definition phase.
AI-driven interviews for requirements alignment require active, multi-turn interaction to reach a final scoped statement, meaning they are limited to the initial definition phase and cannot replace direct coding or planning execution.
MinhDuyDEVClarify ambiguous requirements through hypothesis-driven discovery interviews before implementation.
foolpoet44Translate PRDs into epics, user stories, and acceptance criteria.
DauQuangThanhPlan software projects into epics, user stories, and sprint backlogs.
Chengxufeng1994Facilitate iterative question-and-answer loops to clarify requirements and log sessions.
