split-decision
When facing architectural decisions, technology choices, or strategic trade-offs, present options as a structured comparison and require explicit trade-off acknowledgment before proceeding. Triggers on words like "should we", "which approach", "what's the best way", or when Claude is about to recommend one approach over alternatives. Never present a single recommendation without showing viable alternatives first.
npx skills add majiayu000/claude-skill-registry --skill split-decision --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Split Decision <purpose> Claude has a tendency to present "the best approach" as if there's only one right answer. In reality, most significant decisions involve trade-offs. This skill forces multi-option analysis before committing to any architectural, technology, or strategic choice. No more single-option recommendations dressed up as obvious conclusions. </purpose> ## When To Activate Trigger when you see: - User asks "should we X or Y" - User asks "what's the best approach for..." - User asks "which is better..." - Claude is about to recommend an architectural choice - Claude is about to recommend a technology/library/tool - Any decision with meaningful trade-offs (not trivial choices) - Refactoring approaches with multiple valid paths - Database, framework, or infrastructure decisions Do NOT trigger for: - Trivial decisions ("should I use let or const here") - Bug fixes with clear solutions - Syntax questions - When user has already made the decision and just needs implementation ## Instructions ### Step 1: Identify Viable Options Generate 2-4 genuinely viable options. These must be: - Actually reasonable choices (not strawmen to make one look better) - Different enough to h
- When To Activate
- Instructions
- Step 1: Identify Viable Options
- Step 2: Assess Each Option
- Step 3: Present Comparison Table
- Step 4: State Your Lean
- Step 5: Request Explicit Confirmation
- Trade-off Categories
- NEVER
- ALWAYS
- Examples
- Example 1: Database Choice
- Example 2: Refactoring Approach
- Example 3: Quick Decision (Skill Not Needed)
What does the split-decision skill do?
When facing architectural decisions, technology choices, or strategic trade-offs, present options as a structured comparison and require explicit trade-off acknowledgment before proceeding. Triggers on words like "should we", "which approach", "what's the best way", or when Claude is about to recommend one approach over alternatives. Never present a single recommendation without showing viable alternatives first.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill split-decision --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.