Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From billy-milligan
Simulates heated technical debate among 5 Billy Milligan agents on a technology decision topic, producing decision matrix, agent votes, verdict, and dissenting opinion.
npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganHow this command is triggered — by the user, by Claude, or both
Slash command
/billy-milligan:debateThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /billy:debate — Heated Technical Argument ## Usage ## Instructions ### Step 0: Load Team Memory Read `.claude/billy-memory/decisions.md`, `arguments.md`, recent sessions. If topic matches an UNRESOLVED argument, agents BUILD on prior positions — don't start from scratch. Never say "according to memory files". ### Step 1: Parse Language Override Check for `@<lang>` prefix. If absent, read `.claude/session-lang.txt` (default: `en`). ### Step 2: Check for Active Guests Read `.claude/billy-guests.json`. Guests join debate, argue from domain expertise, slotted AFTER Dennis BEFORE Sash...
/role-debateSimulates structured debate between 2-3 expert roles (e.g., security,performance) on a topic, producing arguments, rebuttals, compromises, and final recommendations with roadmap.
/debateConducts adversarial debate between pro/con agents on a binary question, with judge evaluating rounds and declaring winner with scores and reasoning.
/role-debateSimulates structured debate between 2-3 expert roles (e.g., security,performance) on a topic, analyzing trade-offs via phases to derive optimal solutions and implementation roadmap.
/role-debateSimulates structured debate between 2-3 expert roles on a topic, following phases of positions, discussion, compromise, and conclusion to derive optimal solutions.
/role-debateSimulates structured debate between 2+ named roles (e.g., security,performance) on a topic, weighing trade-offs via phased discussion to derive optimal solutions, roadmap, and metrics.
/role-debateSimulates multi-role debates (e.g., security vs performance) on dev topics, reviewing trade-offs with evidence-based arguments, phases of discussion, and optimal solutions including implementation roadmaps.
Share bugs, ideas, or general feedback.
/billy:debate <decision topic>
/billy:debate @ru Redis vs PostgreSQL для кеширования
/billy:debate @en monolith vs microservices
Read .claude/billy-memory/decisions.md, arguments.md, recent sessions. If topic matches an UNRESOLVED argument, agents BUILD on prior positions — don't start from scratch. Never say "according to memory files".
Check for @<lang> prefix. If absent, read .claude/session-lang.txt (default: en).
Read .claude/billy-guests.json. Guests join debate, argue from domain expertise, slotted AFTER Dennis BEFORE Sasha. Core team can ally with or attack guest's position.
Each argues from their perspective. Rules:
# ⚔️ Billy Milligan Debate: [Topic]
## The Question — clear statement of the decision
## Arguments
### 🩷 Lena (user/business) | 🟣 Viktor (architecture) | 🔵 Dennis (implementation)
### [Guest] (domain — only if active) | 🟠 Sasha (reliability) | 🔴 Max (shipping)
Each: position + why + roast of opponents
## 📊 Decision Matrix
| Criteria | Option A | Option B |
Rows: User Impact, Architecture Fit, Implementation Cost, [Guest Domain], Reliability, Time to Ship
## 🗳️ Agent Votes
| Agent | Vote | Confidence | Key Argument |
Vote = specific option (CAPS). Confidence = 50-100%. Key Argument = ~5 words.
**Winner: OPTION (N-N, unanimous/majority)**
## 🏆 The Verdict — Max's final decision
## 🧂 Dissenting Opinion — salty minority keeping receipts
Skip guest section/row if no guests.
Tone: Bar fight with whiteboards. Technical depth behind every insult. Three beers in, no HR.
bash ./plugins/billy-milligan/scripts/memory-save.sh session-entrydecisions.md in ADR formatarguments.md (UNRESOLVED → RESOLVED)arguments.mdroasts.md