competitive-intelligencelisted

# competitive-intelligence Competitor analysis, market sizing, positioning maps, win/loss pattern synthesis, and battlecard creation for product and GTM decisions. ## When to use - Map the competitive landscape for AI code assistants (GitHub Copilot, Cursor, etc.) - Create a battlecard for our sales team competing against Datadog - Analyse our last 50 win/loss notes — what patterns do you see? - How should we position against a competitor that's 10x larger? - Estimate the TAM for developer productivity tools in enterprise - What are the defensible moats in the observability market? - Identify the positioning gaps in the MLOps tool landscape - Compare our feature set against three competitors in a matrix ## When NOT to use - Run customer interviews to validate our positioning hypothesis — Primary research — not CI synthesis - Build a three-year financial model for our go-to-market plan — Financial modelling — out of scope - Design our pricing tiers and annual contract structure — Pricing strategy — separate concern - Write a press release about our product launch — Comms/PR — not competitive intelligence ## Anti-patterns ### Symptom Invoking this skill for tasks outside its scope — e.g., infrastructure concerns when the request is about application code, or vice versa. ### Problem Scope mismatch wastes context and produces advice tuned for the wrong domain. A database schema skill answering a connection-pooling question gives schema advice when the real problem is oper