mcpField
C
core-interview

core-interview

github.com/pwgulerAgent workflows10121 installsUpdated 2w ago
Repository

About core-interview

core-interview is an agent skill for reaching agreement on a topic by resolving its decision tree one choice at a time. It is intended for agents eliciting requirements, with rules for when to ask, inspect the codebase, or adopt and record an assumption.

Key features

  1. 01Decision-tree-based requirement discovery
  2. 02One substantive decision per question
  3. 03Codebase inspection before asking
  4. 04Low-risk assumptions recorded
  5. 05Final summary lists adopted assumptions

Use cases

  1. 01Clarifying requirements before implementation
  2. 02Resolving dependent design choices in order
  3. 03Checking existing code instead of asking the user

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pwguler/skills --skill core-interview

After installing, type/core-interviewin Claude Code to confirm it loaded.

Details

From the project README

Question the user until the two of you agree on every part of the topic. Treat the topic as a decision tree. Settle each decision before the decisions that depend on it. Leave no branch open. Not every branch needs a question to the user. The code can settle it, or an assumption that the rules below allow.

Rules:

  • Ask only questions whose answer would change what gets built. When your recommendation is strong and a wrong choice costs little, do not ask. Adopt the recommendation, record it as an assumption, and continue.
  • Put one real decision at a time to the user. Use the question tool of your agent when it has one. Wait for the answer before you ask the next question. The options are your candidate answers, with the recommended answer first. Put low-risk clarifications together in one question.
  • The user can always type an answer that the options do not have. So the tool never limits the choices of a decision.
  • If the codebase can answer a question, look in the codebase. Do not ask the user. You find the facts, not the user. Look up a fact in this session before you ask the question that depends on it.
  • When the user cannot describe the target behavior in words, ask for a reference implementation. That is source code whose behavior you reproduce, also in another language or library. Source code is better than a description or a screenshot.
  • The final summary lists every assumption that you adopted. The user can then reject any of them in one reply. A rejected assumption opens only its own branch again.

Comments

Markdown supported