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

Ir para a instalação

Informações da origem

Repositório
ryanb/dotfiles
Última atividade na origem
23 de junho de 2026 às 17:32
Idioma detectado do SKILL.md
inglês
Estrelas
2.398
Forks
770

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
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.
Ver no GitHub