bug-fix
Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with…
Adversarial deliberation process for making decisions. Spawns advocate agents for each option who argue their cases before a judge (you) who renders a verdict.
$ npx -y skills add chrisallenlane/claude-swe-workflows --skill think-deliberate --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/think-deliberateContext preview
The summary Claude sees to decide when to auto-load this skill.
Adversarial deliberation process for making decisions. Spawns advocate agents for each option who argue their cases before a judge (you) who renders a verdict.
name: think-deliberate description: Adversarial deliberation process for making decisions. Spawns advocate agents for each option who argue their cases before a judge (you) who renders a verdict. model: opus
Uses adversarial representation to ensure all options are robustly explored before making a decision. Inspired by the legal adversarial system where truth emerges from the collision of well-argued positions.
**Judge (You):** The Claude instance running this skill. You:
**Advocates:** Subagents spawned for each option. They:
**Identify from user's request:**
**If options are unclear:**
**Output:** Clear list of N options to deliberate.
**Before spawning advocates, ensure you have sufficient context.**
**Probe for:**
**Ask clarifying questions proactively** - don't assume the initial framing contains everything relevant. Users often omit context they consider obvious.
**Conclude fact-finding when:**
**Keep it focused** - you're gathering context, not conducting an interview. 3-5 clarifying questions is typical; more than 10 suggests the decision isn't ready for deliberation.
**For each option, spawn an advocate agent:**
**Advocate prompt template:**
You represent: [OPTION] Decision context: [WHAT IS BEING DECIDED] Relevant criteria: [WHAT MATTERS FOR THIS DECISION] Background: [ANY CONTEXT THE USER PROVIDED] Present your initial argument for why [OPTION] is the best choice.
**Collect initial arguments from all advocates.**
**Share all arguments with all advocates:**
**Rebuttal prompt template:**
You represent: [OPTION] Here are the arguments made by all advocates: [ADVOCATE 1 - OPTION A]: [argument] [ADVOCATE 2 - OPTION B]: [argument] ... Present your rebuttal. Address the strongest points made against your option and counter the arguments made for competing options.
**As judge, you may ask questions to:**
**Question prompt:**
You represent: [OPTION] The judge asks: [QUESTION] Respond directly and honestly.
**You may question one advocate, multiple advocates, or all of them.**
**Before rendering judgment, explain your current thinking:**
**Give advocates a final opportunity to respond:**
You represent: [OPTION] The judge is leaning toward [OTHER OPTION] for the following reasons: [REASONING] This is your final opportunity to make your case. Respond to the judge's reasoning.
**Collect final arguments in parallel.**
**After final arguments, either:**
**A) Return to Step 5** if:
**B) Proceed to judgment** if:
**Iteration limit: 10 rounds maximum** (a "round" is one cycle through steps 4-6)
**Present your decision to the user:**
1. **The verdict**: Which option you recommend 2. **Primary reasoning**: The 2-3 most important factors 3. **Acknowledgment of trade-offs**: What you're giving up 4. **Confidence level**: How confident you are in this decision 5. **Key evidence**: What most influenced your decision
**Format:**
## Judgment **Recommendation:** [OPTION] **Reasoning:** [Why this option wins] **Trade-offs:** [What you're sacrificing by not choosing alternatives] **Confidence:** [High/Medium/Low] - [Brief explanation] **Key factors:** - [Factor 1] - [Factor 2] - [Factor 3]
**If you truly cannot decide:**
**Present to user:**
## Unable to Render Judgment I cannot make a definitive recommendation because: [REASON] **The deliberation reveal
A system of composable software engineering workflows for Claude Code. Plan projects, implement tickets, and run quality passes — from a single ticket to a multi-batch project, using the same layered architecture.
Repo: chrisallenlane/claude-swe-workflows
Bug-fixing workflow that coordinates diagnosis, test-driven reproduction, root-cause analysis, and targeted fixes. Use when the user wants to fix a bug with…
Proactive bug-hunting workflow. Assesses codebase risk through complexity, coverage, and structural analysis, then spawns focused investigators that write…
Multi-ticket batch workflow. Takes a batch of tickets, plans execution order, implements each via /implement in autonomous mode, runs cross-cutting quality…
Full-lifecycle project workflow. Takes batched tickets, implements via /implement-batch, runs smoke tests, then executes a comprehensive quality pipeline…
Iterative development workflow that coordinates implementation, refactoring, QA, and documentation agents to complete features systematically. Use when the…
Autonomous bug-elimination loop. Iteratively invokes /bug-hunt and /implement-batch until findings converge below an operator-specified severity floor. At…