Skip to main content
command CX Codex

competitive — Claude Code command: what it does, how to install

competitive researches competitors for any feature or product, maps market gaps, and saves a markdown report to your project.

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 competitive does

The competitive command breaks down the competitive space for a specific product or active task context. It starts with an intake check using AskUserQuestion. The agent clarifies competitor lists, target dimensions such as pricing or UX, and research depth before gathering information.

Once confirmed, the command analyzes three to five direct and indirect competitors. It reviews target audiences, strengths, drawbacks, and monetization models. The output produces a comparison matrix, highlights common industry baselines, and outlines technical pointers inside a <claude_context> block.

Finished research does not vanish in chat logs. The agent automatically creates artifacts/research/ and writes a timestamped Markdown document named after your topic.

What it helps with

  • Analyze competitor strengths and weaknesses
  • Build feature comparison tables across rivals
  • Spot market gaps and differentiation angles
  • Extract technical patterns common in the niche

Example prompts for the agent

  • /competitive b2b billing platforms
  • /competitive
  • /competitive habit tracking apps

How to install competitive

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/competitive.md

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

Questions about competitive

How do I install competitive in Claude Code?

In Claude Code, run both commands in order: /plugin marketplace add glittercowboy/taches-cc-resources and then /plugin install taches-cc-resources@taches-cc-resources.

What does the competitive command do?

It reviews competing products in your problem space to uncover differentiation opportunities, business models, and technical standards.

Where is the research report stored?

The command creates an artifacts/research/ directory and writes a file named YYYY-MM-DD-[topic]-competitive.md.

Source text

competitive.md · MIT
---
description: Research competitors - who else does this, how, strengths/weaknesses
argument-hint: [product/feature or leave blank for current context]
---

<objective>
Research competitive landscape for $ARGUMENTS (or the current topic if no arguments provided).

Understand who else solves this problem, how they do it, and where the opportunities are.
</objective>

<intake_gate>

<context_analysis>
First, analyze $ARGUMENTS to extract what's already provided:
- The product/feature space
- Known competitors
- Dimensions that matter (features, pricing, UX)
- What you're trying to learn

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 competitors unclear:**
- "Any specific competitors to include?" with options: I have a list, Find the main ones, Direct competitors only, Include indirect competitors, Other

**If dimensions unclear:**
- "What dimensions matter?" with options: Features/capabilities, Pricing/business model, UX/design, Technical approach, All of the above, Other

**If goal unclear:**
- "What are you trying to learn?" with options: How to differentiate, Market positioning, Feature gaps, Technical approaches, Other

**If depth unclear:**
- "How many competitors?" with options: Top 3, Top 5, Comprehensive (7+), Other

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

<decision_gate>
After receiving answers, use AskUserQuestion:

Question: "Ready to research competitors, or would you like me to ask more questions?"

Options:
1. **Start research** - 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 research" → proceed to research
</decision_gate>

</intake_gate>

<process>
After intake complete:

1. Define what problem/space we're competing in
2. Identify 3-5 key competitors (direct and indirect)
3. For each competitor, analyze:
   - How they solve the problem
   - Target audience
   - Strengths and weaknesses
   - Pricing/business model
4. Identify patterns across competitors
5. Find gaps and opportunities
</process>

<output_format>
## Competitive Research: [Space/Problem]

### Strategic Summary
[2-3 sentences: the competitive landscape, key insight, main opportunity]

### Problem Being Solved
[What job are all these products doing for users]

### Competitors

**[Competitor 1]**
- **Solution:** [How they solve it]
- **Target:** [Who they serve]
- **Strengths:** [What they do well]
- **Weaknesses:** [Where they fall short]
- **Pricing:** [Model and range]

**[Competitor 2]**
[Same structure...]

**[Competitor 3]**
[Same structure...]

### Comparison Matrix
| Aspect | Comp 1 | Comp 2 | Comp 3 |
|--------|--------|--------|--------|
| [Key feature] | Y/N | Y/N | Y/N |
| [Key feature] | Y/N | Y/N | Y/N |
| [Key feature] | Y/N | Y/N | Y/N |

### Patterns
[What most/all competitors do - table stakes]

### Gaps & Opportunities
- [Gap]: [Why it's underserved, opportunity]
- [Gap]: [Why it's underserved, opportunity]

### Differentiation Options
1. [Way to differentiate]: [tradeoff]
2. [Way to differentiate]: [tradeoff]

### Implementation Context
<claude_context>
<insights>
- table_stakes: [features we must have to compete]
- differentiators: [features that would set us apart]
- avoid: [approaches that don't work in this space]
</insights>
<technical>
- common_patterns: [technical approaches competitors use]
- opportunities: [technical approaches no one uses yet]
- integrations: [common integrations in this space]
</technical>
<positioning>
- underserved: [user segments not well served]
- overserved: [segments with too many options]
</positioning>
</claude_context>

**Next Action:** Deep dive on specific competitor, validate gaps with user research, or run /plan/brief to define our approach

### 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]-competitive.md`
   - Example: `2025-01-15-midi-sequencers-competitive.md`

3. Write the complete research to the file

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

<success_criteria>
- Competitors are genuinely relevant (not just big names)
- Analysis is honest (not dismissive of competition)
- Gaps are real opportunities (not just missing features)
- Differentiation options are actionable
- Implementation context identifies technical patterns to adopt or avoid
- Informs strategic decisions
- Output saved to artifacts/research/ directory
</success_criteria>

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

Similar slash commands

All slash commands for Marketing and content →

From the same set48

The whole set →
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 options 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. 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 feasibility feasibility is a command that assesses whether a project can meet its constraints and recommends whether to proceed, revise terms, or stop. CX Codex +1 ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open