Skip to content
Back to skills

Product Intelligence

ASecurity

Automated competitor feature tracking, user feedback clustering, and feature validation for the Product department. Monitors competitor launches, aggregates user feedback signals, clusters by theme, and feeds the product self-improvement loop. Use when tracking competitor features, analyzing user feedback, validating feature hypotheses, or running the product UAOP pipeline.

  • 6 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 8, 2026
ai-agents

Security analysis

A100/100

Scanned September 8, 2026

npx -y skills add kmshihab7878/claude-code-setup --skill product-intelligence --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Product Intelligence?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Product Intelligence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/kmshihab7878-product-intelligence/badge)](https://www.skillsdirectory.com/skills/kmshihab7878-product-intelligence)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "product-intelligence"
description: "Automated competitor feature tracking, user feedback clustering, and feature validation for the Product department. Monitors competitor launches, aggregates user feedback signals, clusters by theme, and feeds the product self-improvement loop. Use when tracking competitor features, analyzing user feedback, validating feature hypotheses, or running the product UAOP pipeline."
risk: low
tags: [product, research, competitive-intel, feedback]
created: 2026-03-23
updated: 2026-03-23
---

# Product Intelligence — Product Department Intelligence Engine

Automated competitor feature tracking and user feedback synthesis. UAOP Stage 1 + Stage 5 for Product.

## When to use

- Tracking competitor product launches and feature changes
- Synthesizing user feedback from multiple channels
- Validating feature hypotheses before building
- Quarterly product roadmap planning
- Sprint prioritization — "what should we build next?"

## Pipeline

### Step 1: Competitor Feature Scan
- Monitor competitor changelogs, release notes, Product Hunt launches
- Track feature additions/removals across LangChain, CrewAI, AutoGen
- Identify feature gaps (they have it, we don't) and advantages (we have it, they don't)

### Step 2: User Feedback Aggregation
- Collect signals: support tickets, app reviews, community posts, NPS comments, sales call notes
- Cluster by theme using frequency + sentiment analysis
- Rank by impact: revenue-tied requests > nice-to-haves

### Step 3: Feature Validation
- For each proposed feature: hypothesis, success metric, estimated effort (RICE score)
- Cross-reference against competitor data — are we filling a gap or innovating?
- Check ICP alignment — does the target user actually want this?

### Step 4: Product Intel Report
- Top feature requests (by cluster frequency)
- Competitor moves (new features, pricing changes, positioning shifts)
- Recommended priorities (RICE-ranked)
- Experiment proposals (hypothesis + metric + sample size)

### Step 5: Self-Improvement Loop
- Track feature adoption rates post-launch
- Measure experiment win rates
- Reinforce: features with high adoption → invest more; low adoption → investigate why
- Feed outcomes into next cycle's prioritization

## Cadence
```
WEEKLY:   Competitor changelog scan + feedback triage
MONTHLY:  Full product intel report + RICE re-ranking
QUARTERLY: Roadmap review informed by cumulative intelligence
```

## Agents
| Agent | Role |
|-------|------|
| pm-agent (L0) | Owns product strategy, approves priorities |
| feedback-synthesizer (L4) | Clusters and themes user feedback |
| trend-researcher (L4) | Tracks competitor movements |
| experiment-tracker (L4) | Monitors experiment results |
| requirements-analyst (L4) | Validates feature specs |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…