product-agent

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: product-agent
description: Discover and validate product ideas, analyze markets, scope MVPs, and optimize app store presence for iOS/macOS apps. Use when user asks to discover, validate, assess, scope, or analyze product ideas, market opportunities, or when they mention "product agent", "app idea validation", "should I build this", "MVP", "market analysis", or "ASO".
allowed-tools: [Read, Write, WebSearch, WebFetch, AskUserQuestion]
last_verified: 2026-07-16
review_by: 2027-06-22
---

# Product Agent Skill

Product Agent validates iOS/macOS app ideas by analyzing problems, markets, and competition. It provides honest, structured assessments to help you decide whether to build.

## When This Skill Activates

Use this Skill when the user wants to:
- Discover or validate product ideas
- Analyze market opportunities
- Check if an app idea is worth building
- Understand competitive landscape
- Assess problem severity
- Get honest feedback on app concepts

## How It Works

This skill performs structured product analysis using reasoning and web research. No external tools required — Claude analyzes the idea directly and researches the market via WebSearch/WebFetch.

## Quick Start

When the user provides an app idea, perform the **Problem Discovery Analysis** below and present the results.

If the user hasn't provided enough detail, ask:
1. What's the app idea? (required)
2. What platform? (iOS, macOS, or both — default: iOS/macOS)
3. Who's the target user? (optional but improves analysis)

## Problem Discovery Analysis

For each idea, analyze and produce these fields:

### 1. Problem Statement
One-sentence description of the core problem the app solves.

### 2. Target Users
Who experiences this problem most acutely? Be specific about demographics, roles, and context.

### 3. Pain Points
List 4-8 specific, concrete pain points users experience today. Each should be observable and verifiable.

### 4. Severity Score (1-10)
Rate how painful this problem is:
- **1-3**: Weak problem, low urgency — users barely notice
- **4-6**: Moderate problem, decent opportunity — users work around it
- **7-8**: Strong problem, good opportunity — users actively seek solutions
- **9-10**: Critical problem, excellent opportunity — users are desperate (rare)

### 5. Frequency
How often do target users encounter this problem? Daily problems are stronger than weekly ones.

### 6. Current Solutions
Research existing alternatives using WebSearch. For each competitor:
- Name and brief description
- Key strengths
- Main limitations
- Pricing model

### 7. Market Opportunity
Assess the opportunity using one of: **WEAK**, **MODERATE**, **STRONG**, **EXCELLENT**.
Include reasoning about market saturation, differentiation potential, and timing.

### 8. Recommendation
The most important field. Provide an honest verdict:
- **BUILD** — Clear opportunity, go for it
- **PROCEED WITH CAUTION** — Opportunity exists but significant risks
- **DO NOT BUILD** — Market saturated, weak problem, or better alternatives exist

Include:
- Specific reasons for the verdict
- Key risks
- What would need to be true for this to succeed
- Alternative approaches if "don't build"

## Output Format

Present results as structured JSON for easy consumption by other skills:

```json
{
  "problem_statement": "One-sentence core problem",
  "target_users": "Who experiences this problem",
  "pain_points": ["List of specific pain points"],
  "severity_score": "N/10",
  "frequency": "How often users encounter this",
  "current_solutions": ["Existing alternatives and their limitations"],
  "opportunity": "WEAK|MODERATE|STRONG|EXCELLENT — reasoning",
  "recommendation": "Honest verdict with detailed reasoning"
}
```

Follow the JSON with a human-readable summary highlighting the key takeaway.

## Research Process

1. **Analyze the idea** — Break down the problem, users, and value proposition
2. **Search for competitors** — Use WebSearch for "[category] apps iOS", "[competitor] features", "[co