Exploring Alternatives

Try 2-3 different approaches before implementing - don't settle for first design you think of

43 stars 26 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add obra/clank --skill Exploring Alternatives
Manual install
git clone --depth 1 https://github.com/obra/clank.git /tmp/clank
mkdir -p ~/.claude/skills
cp -r /tmp/clank/skills/coding/exploring-alternatives ~/.claude/skills/Exploring-Alternatives

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Exploring Alternatives

## Overview

Don't settle for the first design you think of. Try multiple approaches, compare trade-offs, pick the best, THEN implement.

**Core principle:** Design is cheap to iterate. Code is expensive. Once you write code, emotional attachment makes it hard to throw away. Explore alternatives while iteration is still cheap.

**Violating the letter of this rule is violating the spirit of good design.**

## When to Use

**Always use before implementing:**
- Non-trivial features
- Complex algorithms
- System design decisions
- Refactoring approaches
- Architecture choices
- Data structure selection

**Especially when:**
- First idea feels complex
- Multiple viable approaches exist
- Stakes are high (production code, public APIs)
- Design will be hard to change later

**Warning signs you need this:**
- Jumping to implementation with first idea
- "This is the obvious way" (without considering alternatives)
- Solution feels forced or awkward
- Fighting the implementation
- Design keeps changing during coding

## The Exploration Process

### Step 1: Understand the Problem

**Before exploring solutions, clarify the problem:**

- What exactly are we solving?
- What are the constraints?
- What are the requirements?
- What are success criteria?

**If problem is unclear, exploring solutions is premature.**

### Step 2: Generate 2-3 Alternatives

**Don't stop at first idea. Generate at least 2 more.**

**Techniques for generating alternatives:**
Read the full skill on GitHub

Details

Skill name
Exploring Alternatives
Repository
obra/clank
Path
skills/coding/exploring-alternatives/SKILL.md
Repo updated
9 October 2025

FAQ

What does the Exploring Alternatives skill do?

Try 2-3 different approaches before implementing - don't settle for first design you think of

How do I install the Exploring Alternatives skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add obra/clank --skill Exploring Alternatives. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Exploring Alternatives popular?

It lives in obra/clank, which has 43 GitHub stars and 26 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.