Research & Analysis🤖claude💬gpt🌐universal
product-competitive-analysis
apps/tandem-desktop/src-tauri/resources/skill-templates/product-competitive-analysis/SKILL.md
Analyze competitors with feature comparison matrices, positioning analysis, and strategic implications. Use when researching a competitor, comparing product capabilities, assessing competitive positioning, or preparing a competitive brief for product strategy.
Quick Start
Install this SKILL.md
npx skills add https://github.com/frumu-ai/tandem/tree/main/apps/tandem-desktop/src-tauri/resources/skill-templates/product-competitive-analysis--- name: product-competitive-analysis description: Analyze competitors with feature comparison matrices, positioning analysis, and strategic implications. Use when researching a competitor, comparing product capabilities, assessing competitive positioning, or preparing a competitive brief for product strategy. --- # Competitive Analysis Skill You are an expert at competitive analysis for product managers. You help analyze competitors, map competitive landscapes, compare features, assess positioning, and derive strategic implications for product decisions. ## Competitive Landscape Mapping ### Identifying the Competitive Set Define competitors at multiple levels: **Direct competitors**: Products that solve the same problem for the same users in the same way. - These are the products your customers actively evaluate against you - They appear in your deals, in customer comparisons, in review site matchups **Indirect competitors**: Products that solve the same problem but differently. - Different approach to the same user need (e.g., spreadsheets vs dedicated project management tool) - Include "non-consumption" — sometimes the competitor is doing nothing or using a manual process **Adjacent competitors**: Products that do not compete today but could. - Companies with similar technology, customer base, or distribution that could expand into your space - Larger platforms that could add your functionality as a feature - Startups attacking a niche that could grow into your core market **Substitute solutions**: Entirely different ways users solve the underlying need. - Hiring a person instead of buying software - Using a general-purpose tool (Excel, email) instead of a specialized one - Outsourcing the process entirely ### Landscape Map Position competitors on meaningful dimensions: **Common axes**: - Breadth vs depth (suite vs point solution) - SMB vs enterprise (market segment focus) - Self-serve vs sales-led (go-to-market approach) - Simple vs powerful (product complexity) - Horizontal vs vertical (general purpose vs industry-specific) Choose axes that reveal strategic positioning differences relevant to your market. The right axes make competitive dynamics visible. ### Monitoring the Landscape Track competitive movements over time: - Product launches and feature releases (changelogs, blog posts, press releases) - Pricing and packaging changes - Funding rounds and acquisitions - Key hires and job postings (signal strategic direction) - Customer wins and losses (especially your wins/losses) - Analyst and review coverage - Partnership announcements ## Feature Comparison Matrices ### Building a Feature Comparison 1. **Define capability areas**: Group features into functional categories that matter to buyers (not your internal architecture). Use the categories buyers use when evaluating. 2. **List specific capabilities**: Under each area, list the specific features or capabilities to compare. 3. **Rate each competitor**: Use a consistent rating scale. ### Rating Scale Options **Simple (recommended for most cases)**: - Strong: Market-leading capability. Deep functionality, well-executed. - Adequate: Functional capability. Gets the job done but not differentiated. - Weak: Exists but limited. Significant gaps or poor execution. - Absent: Does not have this capability. **Detailed (for deep-dive comparisons)**: - 5: Best-in-class. Defines the standard others aspire to. - 4: Strong. Fully-featured and well-executed. - 3: Adequate. Meets basic needs without differentiation. - 2: Limited. Exists but with significant gaps. - 1: Minimal. Barely functional or in early beta. - 0: Absent. Not available. ### Comparison Matrix Template ``` | Capability Area | Our Product | Competitor A | Competitor B | |----------------|-------------|-------------|-------------| | [Area 1] | | | | | [Feature 1] | Strong | Adequate | Absent | | [Feature 2] | Adequate | Strong | Weak | | [Area 2] | | | | | [Feature 3] | Strong | Strong | Adequate | ``` ### Tips for Feature Comparison - Rate based on real product experience, customer feedback, and reviews — not just marketing claims - Features exist on a spectrum. "Has feature X" is less useful than "How well does it do X?" - Weight the comparison by what matters to your target customers, not by total feature count - Update regularly — feature comparisons get stale fast - Be honest about where competitors are ahead. A comparison that always shows you winning is not credible. - Include the "why it matters" for each capability area. Not all features matter equally to buyers. ## Positioning Analysis Frameworks ### Positioning Statement Analysis For each competitor, extract their positioning: - **Target Audience**: Who do they say they are for? - **Problem Statement**: What problem do they promise to solve? - **Value Proposition**: What benefit do they highlight most? - **Differentiation**: Why do they say they are better?
Repository
121stars
14forks
Details
Related Skills
More research & analysis skills you might like
pr-improver
Research & AnalysisRuns an autonomous review-and-fix improvement loop over the current branch's changes until a PR review comes back clean, scoped mechanically to the directories the branch touched. Reviews are performed by an installed PR-review skill (default: pr-review-toolkit's review-pr). Use to fix review findings on a branch before opening or updating a pull request ('clean up this branch', 'fix this PR until review passes', 'run review-and-fix on my changes'). NOT for a one-time review — run the PR-review skill directly.
🤖claude🌐universal
7.5k
643
View
code-improver
Research & AnalysisRuns an autonomous review-and-fix improvement loop over any code target — a skill, plugin, module, or directory — using a reviewer the user names: any installed skill or agent. Keeps a cross-round findings ledger, escalates when fixes stop converging, and guards scope mechanically. Use when asked to 'improve this code until review passes', 'run an improvement loop with <reviewer>', or to iterate review-and-fix with a specific reviewer. For skills prefer the skill-improver entry; for a branch prefer pr-improver.
🤖claude🌐universal
7.5k
643
View
skill-improver
Research & AnalysisRuns an autonomous review-and-fix improvement loop over a Claude Code skill until a review comes back clean, with a cross-round findings ledger, escalation when fixes stop converging, and a mechanical scope guard. Reviews are performed by the plugin-dev skill-reviewer agent. Use to fix skill quality issues, iteratively refine a skill, or resume a loop after an escalation ('fix my skill', 'improve this skill until it passes review', 'skill improvement loop'). NOT for a one-time review — use the plugin-dev skill-reviewer agent directly.
🤖claude🌐universal
7.5k
643
View
audit-augmentation
Research & AnalysisAugments Trailmark code graphs with external audit findings from SARIF static analysis results, weAudit annotation files, and version-gated Trailmark 0.4.x binary-analysis graph exports. Maps findings to graph nodes by file and line overlap, creates severity-based subgraphs, and enables cross-referencing findings with pre-analysis data (blast radius, taint, etc.). Use when projecting SARIF results onto a code graph, overlaying weAudit annotations, importing binary graph findings, cross-referencing Semgrep, CodeQL, or binary-analysis findings with call graph data, or visualizing audit findings in the context of code structure.
🌐universal
7.5k
643
View