Clarify project requirements with AI
Use a short interview to find out who a request serves, what outcome matters and which constraint changes the answer. Finish with an intent you can check.
Clarify project requirements with AI when a familiar label is hiding an unfamiliar need. “We need a dashboard” could mean a sales lead wants a morning exception list or a warehouse manager needs a weekly count. Those requests do not necessarily need the same product.
The interview-me skill starts by stating its current understanding and naming the missing information. It asks questions that distinguish plausible interpretations, then revises its reading as you answer. The exercise suits a live conversation where a wrong assumption would cost the team time.
What it does
- Separate the intended outcome from a suggested solution
- Identify the person who will use the result
- Expose a constraint that changes the design
- Compare two interpretations with a focused question
- Summarise the remaining uncertainty before planning
Install and use
- Install the skill in a compatible conversational agent. Bring an initial request and a person who can answer questions about the work. No account or external research tool is needed for the interview.
- Ask, “We think we need a dashboard. Interview me about the decision it should support before suggesting screens or metrics.”
- Read the final interpretation aloud. Correct anything that sounds plausible but does not reflect what the intended user actually does.
FAQ
Source
Made by Addy Osmani. Original skill: interview-me, published on GitHub under the MIT licence.
View on GitHub