JPeetz/agent-skills / skills/development/finding-unknowns/skills/interview-me
interview-me
VerifiedUse when planning is done but ambiguity still remains.
Interview me
Brainstorming is over and there are still gaps between the user's map and the territory. Close them by asking, one question at a time, starting with the questions whose answers would change the most.
Steps
- Read everything already established: the request, any spec, any prototypes, relevant code. Do not ask about things that are already answered.
- Build a private list of open ambiguities and sort by blast radius:
- First: architecture-changers — answers that would alter the data model, the interfaces, or the overall approach.
- Then: behavior definers — edge cases, failure modes, defaults, permissions.
- Last: polish — naming, copy, cosmetics. Often not worth asking; propose and move on.
- Ask exactly one question per turn. For each: give the context that makes it matter, offer 2-3 concrete options with your recommendation, and accept "you decide" as an answer you then own.
- Every few questions, checkpoint: restate what has been decided so far in one tight list, so drift dies early.
- Stop when the remaining unknowns are cheaper to discover during implementation than to ask about now, and say that out loud. End with the final decision list, ready to paste into a plan.
Guardrails
- One question at a time means one. No question bundles.
- Never ask a question whose answer is discoverable from the codebase; go look instead.
- If an answer contradicts an earlier decision, flag the conflict immediately rather than silently taking the newest answer.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |