Skip to content
Back to skills

Analyze Competition

ASecurity

Map the competitive landscape and positioning gaps for a candidate problem space. Part of the PDLC Discover phase.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 6, 2026
research

Security analysis

A100/100

Scanned October 6, 2026

npx -y skills add tomzx/agents --skill analyze-competition --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analyze Competition?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Analyze Competition
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tomzx-analyze-competition/badge)](https://www.skillsdirectory.com/skills/tomzx-analyze-competition)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: analyze-competition
description: Map the competitive landscape and positioning gaps for a candidate problem space. Part of the PDLC Discover phase.
argument-hint: "[initiative-id or topic]"
---

# Analyze Competition

Maps who else addresses the problem, how they position, and where the gaps are. The output is positioning opportunities, not feature checklists. Pairs with `research-market` and feeds `frame-opportunities`.

## Prerequisites

- Apply the shared PDLC conventions in `skills/pdlc/references/shared.md`.
- `problems.md` from `discover-problems`, or an explicit topic.

## Steps

1. Enumerate alternatives the target customer could use, including the current default and workarounds (the most common "competitor" is doing nothing).
2. For each, capture positioning: who they target, the job they claim to do, their price/range, and their strongest and weakest points.
3. Build a positioning map across two axes that matter to the customer (e.g., ease vs. power, price vs. completeness). Identify empty quadrants.
4. Identify differentiation opportunities: where the problem is underserved, mis-served, or served for the wrong segment.
5. Note moats and switching costs that affect viability, not just desirability.
6. Write `competitors.md` to the initiative directory.

## Output Format

Use the template at `skills/pdlc/templates/initiatives/competitors.md`. Carry the standard initiative frontmatter with `phase: discover`.

## Outcome

If `$OUTCOME_YAML` is set, emit `verdict: drafted`.

## Completion Checklist

- [ ] Current default / do-nothing included as an alternative
- [ ] Positioning map with two customer-meaningful axes
- [ ] At least one differentiation opportunity identified and tied to a problem
- [ ] Switching costs / moats noted

## Next Step

Load `frame-opportunities` once discovery inputs are ready.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…