Skip to main content

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".

설치로 이동

소스 정보

저장소
ryanb/dotfiles
최근 소스 활동
2026년 6월 23일 17:32
감지된 SKILL.md 언어
영어
스타
2,398
포크
770

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
interview
description
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".
# Interview 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.
GitHub에서 보기