split-decision

Generate 2-4 viable options with pros, cons, effort, risk, and reversibility.

60|2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill split-decision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-decision
Source: https://github.com/ElliotJLT/Claude-Skill-Potions/tree/main/skills/split-decision
Command: npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill split-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claude often presents a single best approach without showing viable alternatives. This skill enforces a structured analysis by generating 2-4 genuinely viable options with trade-offs before deciding.

Core Features & Use Cases

  • Viable options generation: Presents multiple well-reasoned paths (2-4) for a decision topic.
  • Structured evaluation: Each option is analyzed for pros, cons, effort, risk, and reversibility.
  • Decision lean: Provides a clear recommendation (lean) with justification and explicit trade-offs.

Quick Start

  1. State the decision topic clearly (e.g., "How should we architect the user service?").
  2. Request 2-4 options with trade-offs; the skill will return a table and a lean.
  3. Confirm which trade-offs you are willing to accept before acting.

Frequently Asked Questions about split-decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I weigh architectural trade-offs when choosing between multiple viable options?

Structured trade-off analysis presents 2-4 viable architectural options side-by-side with pros, cons, effort, risk, and reversibility for each. This method surfaces genuine alternatives before committing to a single path, letting you make informed choices based on your specific constraints and risk tolerance.

What should I evaluate when deciding between technology platforms or refactoring approaches?

Compare options across effort required, implementation risk, reversibility if things go wrong, and key trade-offs unique to each choice. A structured evaluation table clarifies which path aligns with your timeline, team capacity, and appetite for risk.

How do I get a clear recommendation when multiple options seem equally valid?

A decision lean provides a single recommendation with explicit justification and the trade-offs you accept by choosing it. This separates the analysis of all options from the reasoned choice, making trade-offs visible before you act.

Can I use trade-off analysis for workflow design decisions, not just technology choices?

Yes. Structured trade-off analysis applies to any strategic or architectural decision where multiple viable paths exist—platform selection, refactoring scope, workflow redesign, or infrastructure approaches all benefit from comparing options and their reversibility.

What's the difference between this approach and picking a single best solution?

Single-solution thinking skips viable alternatives and their trade-offs. Structured trade-off analysis enforces comparison of 2-4 genuine options with documented pros, cons, and risk, so you choose consciously rather than by default.