From vfm-agent-company
Competitive Analysis using Google's Intelligence Framework. Use when analyzing competitor websites, extracting features from reference products, mapping user journeys, detecting tech stacks, or when the user says "build like X.com". Covers site analysis, feature extraction with MoSCoW prioritization, user journey mapping, and tech stack detection. Triggers on competitor analysis, "giống như", "like X", feature comparison, market research, or reverse-engineering existing products.
npx claudepluginhub duylinhdang1998/claude-template-agent --plugin vfm-agent-companyThis skill uses the workspace's default tool permissions.
**Purpose**: Analyze competitor websites to extract features, user flows, and actionable insights for product development
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
Purpose: Analyze competitor websites to extract features, user flows, and actionable insights for product development
Agent: Google Competitive Analyst Use When: Client requests "build like X.com" or references existing website
This skill provides systematic approaches to analyze competitor websites and extract knowledge that directly informs product requirements, design, and development.
Core Philosophy:
File: references/site-analysis.md
Covers:
When to Use: First step of any competitive analysis
Key Questions:
File: references/feature-extraction.md
Covers:
When to Use: After site reconnaissance
MoSCoW Prioritization:
Example - E-commerce Site:
Must Have:
- Product catalog with search
- Shopping cart
- Checkout flow
- User accounts
- Order management
Should Have:
- Product reviews
- Wishlist
- Order tracking
- Multiple payment methods
Could Have:
- Live chat support
- Product recommendations
- Loyalty program
- Social sharing
Won't Have (defer to v2):
- Live streaming shopping
- AR product preview
- Seller marketplace
File: references/user-journey-mapping.md
Covers:
When to Use: Understanding user flows for requirements
Key Journeys to Map:
Journey Template:
## Journey: [Name]
**Goal**: [What user wants to achieve]
**Entry Point**: [Where journey starts]
**Success Metric**: [How to measure success]
### Steps:
1. [Action] → [Result]
Screenshot: [filename]
Notes: [observations]
2. [Action] → [Result]
Screenshot: [filename]
Notes: [observations]
[Continue for all steps]
### Friction Points:
- [Issue 1]: [Impact]
- [Issue 2]: [Impact]
### Improvements Opportunity:
- [Improvement 1]
- [Improvement 2]
File: references/tech-detection.md
Covers:
When to Use: Informing CTO's tech stack decision
Detection Methods:
Example Analysis:
Frontend:
- Framework: React 18 (detected: __REACT_DEVTOOLS_GLOBAL_HOOK__)
- Rendering: Server-Side Rendering (HTML in source)
- Styling: Tailwind CSS (utility classes)
- State: Likely Redux (predictable state container)
Backend (inferred):
- API: REST (endpoints like /api/products)
- Real-time: WebSocket (ws:// connections seen)
- CDN: CloudFlare (CF-Ray headers)
Performance:
- FCP: 1.2s (good)
- LCP: 2.3s (needs improvement)
- TTI: 3.1s (average)
# Step 1: Initial Analysis
Read: references/site-analysis.md
Visit: Target website
Map: Site structure
Screenshot: Key pages (homepage, main sections)
# Step 2: Feature Discovery
Read: references/feature-extraction.md
List: ALL features observed
Categorize: Must/Should/Could/Won't
Prioritize: Based on business value
# Step 3: User Journey Mapping
Read: references/user-journey-mapping.md
Identify: 3-5 key journeys
Map: Each journey step-by-step
Screenshot: Each step
Note: Friction points
# Step 4: Tech Analysis
Read: references/tech-detection.md
Inspect: Page source, network, performance
Detect: Framework, rendering, API patterns
Document: Tech stack observations
# Step 5: Generate Report
Synthesize: All findings
Create: Competitive analysis report
Save: To .project/requirements/competitive-analysis.md
Present: To CEO for decision-making
CEO: Review analysis report, decide on project scope CTO: Use tech recommendations for stack decision PM: Use feature list for timeline estimation BA: Convert features to user stories and requirements
E-commerce marketplace (C2C + B2C)
Product Catalog
Shopping Cart
Checkout Flow
User Account
Seller Dashboard
1. Land on homepage
→ See featured products, categories, search bar
2. Search for product
→ Enter "laptop" in search
→ See results with filters
3. Browse results
→ Filter by price, rating
→ Click on product
4. View product details
→ See images, specs, reviews
→ Choose variant (color, size)
→ Click "Add to Cart"
5. Review cart
→ See items, total price
→ Apply voucher (optional)
→ Proceed to checkout
6. Checkout
→ Select shipping address
→ Choose payment method
→ Confirm order
7. Order confirmation
→ See order number
→ Receive email confirmation
→ Can track order
Friction Points:
- Too many steps (7 steps to checkout)
- Voucher application not obvious
- Payment methods scattered
Opportunities:
- Guest checkout (no signup required)
- Saved payment methods
- One-click purchase for returning users
Frontend: React SPA with SSR Mobile: Native apps (iOS/Android) Backend: Microservices (product, cart, order, payment, user) Database: PostgreSQL + Redis (caching) CDN: Global content delivery Real-time: WebSocket (chat, notifications)
Phase 1 (Week 1-4):
Phase 2 (Week 5-6):
Phase 3 (Week 7-8):
Defer to v2:
| Feature | Shopee | Lazada | Tokopedia | Priority | Notes |
|---------|--------|--------|-----------|----------|-------|
| Product Search | ✓ | ✓ | ✓ | Must | Basic requirement |
| Shopping Cart | ✓ | ✓ | ✓ | Must | Core e-commerce |
| Live Chat | ✓ | ✗ | ✓ | Should | Customer support |
| Flash Sales | ✓ | ✓ | ✗ | Could | Competitive edge |
## Market Position
**Shopee**:
- Strength: Gamification, free shipping, social features
- Weakness: Product quality inconsistent
- Target: Mass market, price-conscious
**Our Opportunity**:
- Focus on quality verification
- Premium experience
- Better seller vetting
When CEO receives: /work làm e-commerce giống shopee.com
CEO Action:
BA receives competitive analysis report:
Feature: "Shopping Cart"
↓
User Story:
"As a shopper, I want to add products to cart
so that I can review before checkout"
↓
Acceptance Criteria:
- Can add items to cart
- Can adjust quantity
- Can remove items
- Can see total price
- Can apply vouchers
CTO receives tech stack recommendations:
Analysis Quality:
Time Efficiency:
Impact:
🔍 Analyze comprehensively - Don't miss hidden features
📊 Prioritize ruthlessly - Not all features are equal
🎯 Focus on user value - Understand WHY features exist
💡 Find opportunities - What can we do better?
📝 Document everything - Screenshots, flows, insights
For detailed procedures, read the reference guides in references/ folder
Created: 2026-02-04 Maintained By: Google Competitive Analyst Review Cycle: After each competitive analysis