Skip to main content
command CX Codex

options — Claude Code command: compare and decide

A command to evaluate multiple options side-by-side: tools, approaches, architectures. It asks clarifying questions, builds a comparison matrix, and recommends the best choice with reasoning.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What options does

The options command automates decision-making when you have multiple candidates to evaluate. You specify what to compare, and the command asks about your criteria and constraints, then constructs a table with ratings for each option, weights the criteria, and delivers a recommendation plus a fallback choice.

The command runs three stages: first, it scans what context you've already provided and identifies gaps; next, it asks targeted questions via AskUserQuestion; finally, it builds the comparison matrix and scores each option. Results save to artifacts/research/ with a timestamped filename.

It handles any comparison: database selection, framework choice, hosting platform, auth method, even business decisions. Give it what you're choosing between, mention known options or constraints, and the command fills in the rest through questions.

What it helps with

  • evaluate multiple tools or approaches using consistent criteria
  • organize a decision when too many variables are in play
  • justify a choice to stakeholders with structured analysis
  • maintain a record of key decisions for the project

Example prompts for the agent

  • Compare caching options for us: Redis versus Memcached versus SQLite
  • Should we pick Vue or React for a small frontend project, and why?
  • options: where to host a Rust backend — DigitalOcean, AWS, or Fly.io

How to install options

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

2Manually: put the files in place

.claude/commands/options.md

Call it with /options. For all projects use ~/.claude/commands/

Questions about options

How do I install the options command in Claude Code?

Run /plugin marketplace add glittercowboy/taches-cc-resources, then /plugin install taches-cc-resources@taches-cc-resources. The command will be ready as /options.

What does the options command do?

The command asks clarifying questions about what you're comparing, which criteria matter, and any constraints. It then builds a scoring matrix for each option and provides a recommendation backed by reasoning.

Where does the command save the comparison?

Results are saved to artifacts/research/ with a filename like 2025-01-15-database-options.md, so you can refer back to the analysis later.

Source text

options.md · MIT
---
description: Compare multiple options side-by-side with recommendation
argument-hint: [what to compare or leave blank for current context]
---

<objective>
Compare options for $ARGUMENTS (or the current topic if no arguments provided).

Structured side-by-side comparison to make an informed decision. Works for tools, approaches, vendors, architectures.
</objective>

<intake_gate>

<context_analysis>
First, analyze $ARGUMENTS to extract what's already provided:
- What decision is being made
- Known options to compare
- Decision criteria
- Must-haves vs nice-to-haves

Only ask about genuine gaps - don't re-ask what's already stated.
</context_analysis>

<initial_questions>
Use AskUserQuestion to ask 2-4 questions based on actual gaps:

**If criteria unclear:**
- "What matters most?" with options: Simplicity, Performance, Flexibility, Maintenance burden, Let me specify, Other

**If options unclear:**
- "Which options to compare?" with options: I have a list, Find the main contenders, Compare everything, Other

**If weighting unclear:**
- "Any deal-breakers?" with options: Must have specific feature, Must be simple, Must be performant, No deal-breakers, Other

**If constraints unclear:**
- "Any constraints?" with options: Must integrate with existing system, Budget limits, Specific tech requirements, None significant, Other

Skip questions where $ARGUMENTS already provides the answer.
</initial_questions>

<decision_gate>
After receiving answers, use AskUserQuestion:

Question: "Ready to compare options, or would you like me to ask more questions?"

Options:
1. **Start comparison** - I have enough context
2. **Ask more questions** - There are details to clarify
3. **Let me add context** - I want to provide additional information

If "Ask more questions" → generate 2-3 contextual follow-ups, then present decision gate again
If "Let me add context" → receive input, then present decision gate again
If "Start comparison" → proceed to research
</decision_gate>

</intake_gate>

<process>
After intake complete:

1. Define decision criteria (what matters for this choice)
2. List all viable options
3. Evaluate each option against each criterion
4. Weight criteria by importance
5. Make recommendation with reasoning
</process>

<output_format>
## Options Comparison: [Decision]

### Strategic Summary
[2-3 sentences: the options, recommendation, key tradeoff]

### Context
[Brief description of what we're deciding and why it matters]

### Decision Criteria
1. [Criterion] - [why it matters] - Weight: High/Med/Low
2. [Criterion] - [why it matters] - Weight: High/Med/Low
3. [Criterion] - [why it matters] - Weight: High/Med/Low

### Options

**Option A: [Name]**
- [Criterion 1]: [Rating + brief note]
- [Criterion 2]: [Rating + brief note]
- [Criterion 3]: [Rating + brief note]
- **Score: X/10**

**Option B: [Name]**
- [Criterion 1]: [Rating + brief note]
- [Criterion 2]: [Rating + brief note]
- [Criterion 3]: [Rating + brief note]
- **Score: X/10**

**Option C: [Name]**
[Same structure...]

### Comparison Matrix
| Criterion | Option A | Option B | Option C |
|-----------|----------|----------|----------|
| [Criterion 1] | Good/OK/Poor | | |
| [Criterion 2] | Good/OK/Poor | | |
| [Criterion 3] | Good/OK/Poor | | |

### Recommendation
[Option X] because [reasoning tied to weighted criteria]

### Runner-up
[Option Y] - choose this if [specific condition]

### Implementation Context
<claude_context>
<chosen>
- option: [chosen option name]
- install: [how to install/set up]
- config: [configuration needed]
- patterns: [usage patterns]
- docs: [documentation reference]
</chosen>
<runner_up>
- option: [runner-up name]
- when: [conditions where this becomes better choice]
- switch_cost: [effort to switch later if needed]
</runner_up>
<integration>
- existing_code: [how it fits with current codebase]
- gotchas: [common issues with this option]
- testing: [how to verify it works]
</integration>
</claude_context>

**Next Action:** Implement chosen option, prototype to validate, or gather more info on specific option

### Sources
- [Source name]: [URL] - [date accessed]
- [Source name]: [URL] - [date accessed]
</output_format>

<artifact_output>
Save the research to a file:

1. Create directory structure if it doesn't exist:
   - `[current-working-directory]/artifacts/research/`

2. Generate filename from topic:
   - Get current date in YYYY-MM-DD format
   - Slugify the topic (lowercase, hyphens for spaces)
   - Format: `YYYY-MM-DD-[topic]-options.md`
   - Example: `2025-01-15-auth-providers-options.md`

3. Write the complete research to the file

4. Report to user: "Saved to `artifacts/research/[filename]`"
</artifact_output>

<success_criteria>
- Criteria reflect what actually matters for this decision
- Options are genuinely comparable (apples to apples)
- Ratings are justified, not arbitrary
- Recommendation follows from analysis
- Runner-up provides contingency
- Implementation context gives Claude everything needed to proceed
- Output saved to artifacts/research/ directory
</success_criteria>

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar slash commands

All slash commands for Agent setup: memory, context, orchestration →

From the same set48

The whole set →
the-pirate-bay Search The Pirate Bay through its JSON API and retrieve magnet links. Use it to find torrents, browse popular uploads, or check seed counts. CX Codex +1 ★ 1,988repo stars setup-ralph setup-ralph lays out Geoffrey Huntley's Ralph Wiggum loop in a directory: file structure, planning and build prompts, and gates that reject bad work. CX Codex +1 ★ 1,988repo stars run-plan run-plan executes a PLAN.md file directly without loading planner skill overhead. It routes tasks to subagents and keeps most of the context window free. CX Codex +1 ★ 1,988repo stars build-macos-apps build-macos-apps is a Claude Code skill for building native macOS apps with SwiftUI and AppKit. It routes work on new apps, bugs, tests, performance, and releases to a matching workflow. CX Codex +1 ★ 1,988repo stars competitive competitive researches competitors for any feature or product, maps market gaps, and saves a markdown report to your project. CX Codex +1 ★ 1,988repo stars deep-dive deep-dive — a slash command that investigates a topic from several angles and writes a structured report into artifacts/research/ inside your project. CX Codex +1 ★ 1,988repo stars history history — a command to research historical attempts at solving a task: what was tried before, what worked, what mistakes to avoid. Helps prevent repeating errors and apply lessons from experience. CX Codex +1 ★ 1,988repo stars technical Researches technical implementation options, evaluates libraries and tradeoffs, and saves a ready architecture brief into Markdown. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open