본문으로 건너뛰기
cccskills
무료GitHub에 공개

interview-me

Interview the user one question at a time to resolve remaining ambiguity before implementation. Use when planning or brainstorming is done but unknowns remain, or when the user asks to be interviewed about a task or spec.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md1.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

  1. Read everything already established: the request, any spec, any prototypes, relevant code. Do not ask about things that are already answered.
  2. 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.
  3. 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.
  4. Every few questions, checkpoint: restate what has been decided so far in one tight list, so drift dies early.
  5. 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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design tools, scripts, and CLIs that an agent will call, so the interface teaches its own use instead of a wall of prose and examples. Use when building an MCP server or tool definition, writing an agent-facing script, or when an agent keeps misusing a tool it already has.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills3532026년 9월 28일 업데이트

Test a consequential technical assumption with a small, falsifiable experiment before committing to an approach. Use when a plan depends on uncertain runtime, integration, or data behavior that inspection alone cannot establish. Not for preference interviews or routine implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills3532026년 9월 28일 업데이트

Surface the user's unknown unknowns before work starts. Use when the user is entering an unfamiliar codebase area, an unfamiliar domain (design, video, infra), or explicitly asks for a "blindspot pass" or to find their "unknown unknowns."

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills3532026년 9월 28일 업데이트

Generate several genuinely different throwaway variations (designs, approaches, drafts) for the user to react to. Use when the user can only recognize what they want by seeing it — visual design, UX flows, naming, tone — or asks to brainstorm or prototype before building.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills3532026년 9월 28일 업데이트

After a working session, produce a report on what changed plus a quiz the user must pass before merging. Use when the user asks "what did we actually do," wants to review a large change, or invokes a quiz before merge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills3532026년 9월 28일 업데이트

Audit the instructions an agent already carries — CLAUDE.md, AGENTS.md, skills, tool descriptions — for contradictions, over-constraint, and duplication, then propose a cut list. Use when an agent ignores its own instructions, when a CLAUDE.md has grown bloated, or when the user asks to audit or rightsize their agent context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Neeeophytee/finding-unknowns-skills3532026년 9월 28일 업데이트

Neeeophytee의 스킬 모두 보기

이 스킬의 문제 신고