# Competitor tracking Human Guide

## What This Is For
Systematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation. It gives the agent a clearer input/output frame for competitive research: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Competitor tracking agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for competitor tracking.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Competitor tracking guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Understand your competitive positioning
- Arm sales and marketing with accurate battlecards
- Identify market gaps and opportunities
- Learn from competitor successes and failures
- Same category, same target developer
- Would appear in the same "best X tools" lists
- Example: If you're a CI/CD tool, other CI/CD tools
- Adjacent categories that overlap with your use case
- Might be expanding into your space
- Developers might use instead of your category
- Example: GitHub Actions competing with standalone CI tools
- Open source tools developers self-host

## Decision Points And Nuance
The original skill emphasizes: Overview, Competitor Identification, Types of Competitors, Competitive Landscape Mapping, What to Track, Product and Features, Pricing and Packaging, Positioning and Messaging, Content Strategy, Community and Traction.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Don't be sleazy or pile on

## Copy-And-Paste Prompt
```text
Use the Competitor tracking human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the jonathimer/devmarketing-skills skill entry for `competitor-tracking`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Competitor Tracking

Systematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.

## Overview

Competitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding/trajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.

Effective competitor tracking helps you:
- Understand your competitive positioning
- Anticipate competitor moves
- Arm sales and marketing with accurate battlecards
- Identify market gaps and opportunities
- Learn from competitor successes and failures

## Competitor Identification

### Types of Competitors

**Direct Competitors:**
- Same category, same target developer
- Solve the same core problem
- Would appear in the same "best X tools" lists
- Example: If you're a CI/CD tool, other CI/CD tools

**Indirect Competitors:**
- Adjacent categories that overlap with your use case
- Might be expanding into your space
- Developers might use instead of your category
- Example: GitHub Actions competing with standalone CI tools

**DIY Alternatives:**
- Open source tools developers self-host
- Custom scripts and internal tooling
- "Just use bash scripts" or "build it yourself"
- Often your biggest competitor by volume

**Platform Alternatives:**
- Cloud provider native services (AWS, GCP, Azure equivalents)
- All-in-one platforms that include your functionality
- Enterprise suite solutions

### Competitive Landscape Mapping

Create a competitive landscape document with:

1. **Competitor profiles** - Company, product, target market, positioning
2. **Feature matrix** - Core features compared across competitors
3. **Pricing comparison** - Tiers, pricing model, enterprise pricing signals
4. **Strengths/weaknesses** - Honest assessment of each competitor
5. **Trajectory** - Funding, growth signals, strategic direction

## What to Track

### Product and Features

**Track weekly/monthly:**
- Changelog and release notes
- New feature announcements
- Pricing changes
- Integration announcements
- API changes
- SDK/library updates

**How to track:**
- Subscribe to competitor newsletters
- Follow their GitHub releases
- Monitor their Twitter/blog
- Set up monitoring alerts for "[competitor] launch" "[competitor] announces"

### Pricing and Packaging

**Key signals:**
- Pricing page changes (use archive.org to track history)
- New tier introductions
- Enterprise/custom pricing signals
- Free tier changes
- Usage-based vs seat-based shifts

**Competitive pricing intelligence:**