- name
SKILL.md
スキルファイルは公開元のリポジトリに置かれたままです。
コピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add boshu2/agentops --skill interview -a cursor -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add boshu2/agentops --skill interview -a claude-code -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add boshu2/agentops --skill interview -a codex -yコピーしたコマンドをターミナルに貼り付けてください。この SKILL.md がそのエージェントにインストールされます。
npx skills add boshu2/agentops --skill interview -a grok -yコピーしたメッセージを Grok Bot のチャットで送信してください。Bot がこの SKILL.md を GitHub から取得し、すべての Bot が共有するスキルに追加します。
Install this skill: https://github.com/boshu2/agentops/tree/HEAD/plugin/skills/interview公開元より
Shape a big outcome with the caller, one question per turn, before agents run alone: you look up facts; the caller makes choices and supplies what only they know. Interview creates nothing new (no goal, bead or file), changes no status, claim or closure, and only appends notes to an existing intent source (Show the state). To test a plan, design or decision the caller already holds, see a held plan.
Settled: <what the last answer decided, or nothing yet>. Open: <count>.
Q<n>: <the decision>. <the question, with 2 to 4 options when they exist>
My recommendation: <answer>, because <source or reason>.
Tradeoff: <the one cost that matters>
Because "your call" turns the recommendation into scope, recommend only what the outcome needs. Add a criterion, safeguard, authority or budget the caller did not name only when the outcome fails without it or harm would land before anyone notices. Offer anything else costly to add later (stored data, a published interface, money, security) as an option, not as the recommendation. Never narrow what the caller asked for. Draw budget and authority options from a source (prior goals, the tracker, the caller's words); with none, ask openly.
The caller answers by default. On request ("let a council answer my interview"), a council answers through Council's interview-panel mode; the caller accepts or amends its answers in one pass before anything is recorded, and authority, budgets and acceptance changes stay the caller's. Fact questions stay with the caller in this mode; the council answers only choices. If only another person can answer, keep the choice Open and offer a questionnaire for that person. The caller sends it; Interview contacts no one.
Drive each criterion to a Given/When/Then with an observable result and its proving evidence. Draft the example yourself as the recommendation; the caller accepts or edits it. "Works reliably" is not acceptance; ask what would be seen.
Given a Job has already completed
When the worker receives that Job again
Then it returns the completed result without a second side effect
# Proof: a redelivery test asserts one side effect and the completed result
When a word is vague, overloaded or has synonyms, ask which term the domain uses. Record one term with a one-line definition and use only it in examples, notes, code and tests. Domain owns deeper modeling.
Show these lists on request, after a revision and at stop:
Number each choice Q when first listed. As an item changes, Open and Deferred included, append its line to the intent source (root epic, issue or conversation) if the request or existing authorization covers editing it (the conversation always does); otherwise show it for the caller to append. The last line per Q or term is current. Before treating acceptance as frozen by a running goal, confirm its current state from the native goal runtime or the caller. A saved Navigate checkpoint or open child build beads alone do not establish a running goal. If that state is unknown and matters to the proposed update, ask. While a goal runs, append no changed criterion or term; list it under Open in the conversation as an acceptance change for the caller to hold and re-craft. In BD:
bd context --json # confirm the destination before any write
bd show <epic-id> # on resume: the last line per Q<n> or term; start from Open
bd update <epic-id> --append-notes "decided Q<n>: <choice> | example: <Given/When/Then> | proof: <evidence>"
# or: "fact Q<n>: <report>" "term: <word> = <definition>" "open Q<n>: <choice>" "deferred Q<n>: <choice> | revive when <condition>"
Stop when the caller stops, the next question would only restate a settled answer, the work proves to be one slice (not when testing a held plan), or everything Craft Goal admission needs is settled:
While the caller is still here, test the settled answers once. Then hand over the lists; the caller starts the next step: Craft Goal for several related experiments, RPI or Plan for one outcome with items 1 to 3 and real bounds. Open items stay open; never fill one to finish.
Interview you one question at a time, each choice with a recommendation, to settle a big outcome before agents work alone. Use when: asked to interview you about a goal or plan.
---name: interviewdescription: Interview you one question at a time, each choice with a recommendation, to settle a big outcome before agents…---# plugin/skills/interview/SKILL.mdよくある質問
公開元から plugin/skills/interview/SKILL.md をダウンロードするか、パスをコピーしてリポジトリを開いてください。PlugMCP はスキルを掲載するだけで、ファイルはホストしていません。
公開元は https://github.com/boshu2/agentops で管理しています。
Claude、Cursor、Codex、Grok Build は、公開元のリポジトリから追加した SKILL.md を読み込めます。Grok Bot は、チャットでスキルの GitHub フォルダーのリンクを送るとインストールします。