/debate-kickoff
Starter: frame a decision as a multi-model debate — picks sides, seats providers, and launches /octo:debate with a well-formed motion
One skill from octo.
shell
$ npx -y skills add nyldn/claude-octopus --skill debate-kickoff --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/debate-kickoff
Context preview
The summary Claude sees to decide when to auto-load this skill.
Starter: frame a decision as a multi-model debate — picks sides, seats providers, and launches /octo:debate with a well-formed motion
Stats
Stars3,869
Forks362
LanguageShell
LicenseMIT
Ships with octo
SKILL.md
debate-kickoff.SKILL.md
--- name: debate-kickoff description: "Starter: frame a decision as a multi-model debate — picks sides, seats providers, and launches /octo:debate with a well-formed motion" --- # 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.
