interview-me
FeaturedConduct an adaptive structured interview that elicits tacit knowledge, requirements, preferences, or decisions and summarizes them explicitly. Use when the needed information is in the user's head and cannot be recovered from project files. Not for adversarial oral examination; use $grill-me.
Install
Quality Score: 93/100
Skill Content
Details
- Author
- flonat
- Repository
- flonat/flonat-research
- Created
- 7 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
interview-me
Interview the user about a plan or decision through structured one-at-a-time questioning until reaching consensus. Produces a design brief artifact or hands off when the user signals readiness. Use when an idea is vague and needs shaping before planning or implementation begins. Trigger this when someone says: interview me, help me think through this, I have an idea but I don't know how to approach it, ask me questions about this, what should I be thinking about here. Do NOT use when the task is already well-scoped — use /plan instead.
interview-me
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.
interview-me
Extracts what the user actually wants instead of what they think they should want. Achieves this through one-question-at-a-time interview until ~95% confidence about the underlying intent. Use when an ask is underspecified ("build me X" without "for whom" or "why now"), when the user explicitly invokes ("interview me", "grill me", "are we sure?", "stress-test my thinking"), or when you catch yourself silently filling in ambiguous requirements before any plan, spec, or code exists.