interview
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Like grill-me, but asks one structured, numbered question at a time with multiple-choice options. Use when the user wants a disciplined interview to stress-test a plan or design, or mentions "interview me".
pinned to #3a6ecb2updated 2 weeks ago
Ask your AI client: “install skills/interview”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/interviewmetahub onboarded this repo on the author's behalf.
If you own github.com/ryanb/dotfiles on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
2,392
Last commit
2 weeks ago
Latest release
published
About this skill
Pulled from SKILL.md at publish time.
Interview the user relentlessly about every aspect of this plan or design until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one at a time.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.3a6ecb2· 2 weeks ago
Documentation
41Description quality
52 words · 342 chars — "Interview the user relentlessly about a plan or design until reaching shared und…"
README is present and substantial
4,149 chars · 4 sections · 9 code blocks
Tags / topics declaredwarn
No manifest tags and no GitHub repo topics
Add tags to the manifest (or GitHub topics on the repo) so the registry's search and category filters surface this artifact.
README has usage / example sections
found: Installation
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Release history
1- releasecurrent3a6ecb2warn2 weeks ago
Contents
Interview the user relentlessly about every aspect of this plan or design until you reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one at a time.
Rules for questions
- One question at a time. Never bundle multiple questions into a single turn. Ask, wait for the answer, then ask the next.
- Number questions in strict sequence. Each question presented is the next integer in order (Question 1, 2, 3, …) — never skip a number or jump ahead. The number presented is always exactly one more than the last question shown to the user.
- Always present a numbered list of multiple-choice answers. Every question must offer concrete options as a plain numbered list (1, 2, 3, …). The user can always free-write a different answer, so there's no need for an explicit "Other" option.
- Always give a recommendation. After the options, state which option you recommend and why, in one line.
- Explore before asking. If a question can be answered by exploring the codebase, do that instead of asking.
Format every question like this:
<The single question>
1. <Option one>
2. <Option two>
3. <Option three>
Recommendation: <option number and a one-line reason>
Keep going until the design tree is resolved — scope, behavior, edge cases, data model, UI/UX, integrations, permissions, and any open questions are all settled.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/interview