startup-competitive-analysis
Startup Competitive Analysis
Use this skill to produce decision-oriented competitive intelligence: define the competitive set, collect evidence, synthesize match / ignore / bet decisions, and ship practical artifacts teams can use (briefs, landscapes, battlecards, win/loss).
Operating Principles (2026)
- Prefer decisions over inventories: make explicit
match / ignore / betcalls with rationale and owner. - Treat competitor claims as hypotheses: validate with buyer reality and current evidence.
- Date-stamp key claims and keep an evidence trail (link + capture month).
- Triangulate important facts across sources (at least two).
- Stay ethical: respect ToS; don’t scrape behind auth/paywalls; don’t misrepresent identity.
Intake Checklist (Ask First)
- Objective: sales enablement, positioning, strategy, fundraising, churn reduction
- Market: category, geography, segment (ICP), and time horizon (now vs 6–12 months)
- Known competitors and “do nothing” alternative (status quo / DIY / services)
- Constraints: available sources, web access, internal docs, legal/compliance requirements
More from vasilyu1983/ai-agents-public
product-management
Founder-PM toolkit for discovery, roadmaps, prioritization, and PMF measurement. Use when planning product strategy, metrics, or roadmaps.
684software-architecture-design
Designs system structure across monolith/microservices/serverless. Use when structuring systems, scaling, decomposing monoliths, or choosing patterns.
519software-ui-ux-design
Designs and audits UI/UX with WCAG 2.2 accessibility. Use when designing flows, running heuristic reviews, or defining design systems.
383qa-testing-playwright
E2E web testing with Playwright. Use when writing tests, debugging flakes, or setting up CI with selectors, sharding, and network mocking.
372document-pdf
Extract text/tables from PDFs, create formatted PDFs, merge/split/rotate, and handle forms. Use for any PDF generation or parsing task.
327qa-testing-strategy
Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, or establishing release criteria.
317