mcpField
D
debate-kickoff

debate-kickoff

github.com/nyldnその他4.3k40 回インストール今日更新
リポジトリ

debate-kickoff について

debate-kickoffは、技術的な選択肢を複数のモデルファミリーによる構造化された議論に変えるスキルです。利用可能なプロバイダーを確認して立場を割り当て、議論を実行し、合意点と相違点をまとめて提案します。

主な機能

  1. 01質問を議題として整理
  2. 02利用可能なプロバイダーの確認
  3. 03議論の立場の割り当て
  4. 04議論の実行と各ラウンドの統合
  5. 05想定コストの提示

活用シーン

  1. 01RedisとMemcachedの比較
  2. 02モノレポとポリレポの評価
  3. 03技術選択への複数モデルの見解収集

インストール

コマンドをコピーしてターミナルで実行します。

$npx skills add https://github.com/nyldn/claude-octopus --skill debate-kickoff

インストール後、Claude Code で/debate-kickoffを入力して読み込まれたか確認します。

同梱ファイルagents/openai.yaml

README(原文)English

プロジェクトの README より

この README の日本語訳はまだありません。以下は英語の原文です。日本語の紹介はページ上部をご覧ください。

Debate Kickoff (Starter Pack)

Turn a loosely stated decision ("Redis or Memcached?", "monorepo vs polyrepo") into a well-formed multi-model debate.

When to use

The user has a two-or-more-sided technical decision and wants adversarial perspectives from different model families rather than one model's opinion.

Steps

  1. Extract the motion. Restate the user's question as a single debatable proposition (for example: "This project should use Redis over Memcached for session storage"). Confirm silently from context; do not interrogate the user.
  2. Check seats. Run ${CLAUDE_PLUGIN_ROOT}/scripts/helpers/check-providers.sh and note which providers are available. A debate needs at least two seatable non-Claude providers for cross-lab disagreement; if only Claude is available, say so and offer a single-model pro/con instead.
  3. Assign sides. Give each available provider an explicit stance (affirmative, negative, or skeptic). Prefer cross-lab pairings (for example Codex affirmative, Antigravity negative) so disagreement is structural, not stylistic.
  4. Launch. Invoke /octo:debate with the motion and the side assignments. Display the standard Octopus banner with provider indicators before dispatch.
  5. Synthesize. After rounds complete, summarize where the models converged, where they genuinely disagreed, and give one recommendation with the strongest surviving argument.

Guardrails

  • External seats cost money; state the expected cost band from the CLAUDE.md cost table before dispatch.
  • Never fabricate a provider's position. If a seat fails, report the failure and continue with the remaining seats.

コメント