ワンクリックで
pm-parallel-research
Use when facing 2+ independent research, analysis, or investigation tasks that can run concurrently without shared state
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use when facing 2+ independent research, analysis, or investigation tasks that can run concurrently without shared state
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when analyzing competitors, understanding competitive landscape, conducting SWOT analysis, or positioning your product against alternatives.
Use when setting up or improving a continuous product discovery practice with weekly customer interviews.
Use when preparing design specifications for engineering handoff and quality assurance.
Use when planning a product or feature launch and preparing go-to-market execution.
Use when you have raw user feedback from multiple sources (interviews, surveys, tickets, reviews) and need to extract themes, patterns, and actionable insights
Use when defining product metrics, designing experiments, analyzing feature adoption, or setting up measurement frameworks.
| name | pm-parallel-research |
| description | Use when facing 2+ independent research, analysis, or investigation tasks that can run concurrently without shared state |
Delegate independent PM research tasks to parallel subagents. When you have multiple competitors to analyze, multiple user segments to research, or multiple discovery activities that don't depend on each other — dispatch them concurrently instead of sequentially.
Core principle: One agent per independent research domain. Let them work concurrently. Synthesize when all return.
Announce at start: "I'm using the pm-parallel-research skill to dispatch parallel research tasks."
digraph when_to_use {
"Multiple research tasks?" [shape=diamond];
"Are they independent?" [shape=diamond];
"Single agent does all" [shape=box];
"Can they run in parallel?" [shape=diamond];
"Sequential agents" [shape=box];
"Parallel dispatch" [shape=box];
"Multiple research tasks?" -> "Are they independent?" [label="yes"];
"Are they independent?" -> "Single agent does all" [label="no - related"];
"Are they independent?" -> "Can they run in parallel?" [label="yes"];
"Can they run in parallel?" -> "Parallel dispatch" [label="yes"];
"Can they run in parallel?" -> "Sequential agents" [label="no - shared state"];
}
Use when:
Don't use when:
Group research by domain:
Domain A: Competitor Analysis — Research Competitor X's pricing, features, positioning
Domain B: User Research — Synthesize 5 recent customer interviews
Domain C: Market Sizing — Estimate TAM/SAM/SOM for the new segment
Each domain is independent — pricing research doesn't affect interview synthesis.
Each agent gets:
Agent 1 → Research Competitor X's pricing and features
Agent 2 → Synthesize interviews for activation pain points
Agent 3 → Estimate market size for enterprise segment
// All three run concurrently
When agents return:
Good agent prompts are:
Analyze Competitor X's product positioning and pricing.
## Context
We're evaluating whether to enter the mid-market analytics space.
Competitor X is the #2 player. We need to understand their strategy.
## Your Task
1. Research Competitor X's public-facing product pages, pricing page, and recent blog posts
2. Identify their pricing tiers, key features per tier, and target customer segments
3. Note any recent positioning shifts (new homepage messaging, new verticals, new case studies)
## Output Format
Return a structured analysis:
### Pricing
| Tier | Price | Key Features | Target Segment |
|------|-------|-------------|----------------|
| ... | ... | ... | ... |
### Positioning
- Primary value prop (1 sentence)
- Target personas
- Key differentiators they claim
- Recent positioning changes
### Strengths & Weaknesses
- What they do better than us
- Where they're vulnerable
### Recommendations
- 3 actionable insights for our strategy
Agent 1 → Competitor A deep-dive (pricing, features, positioning)
Agent 2 → Competitor B deep-dive
Agent 3 → Competitor C deep-dive
Agent 4 → Market trends and adjacent threats
Agent 1 → Synthesize interviews #1-5 (activation problems)
Agent 2 → Synthesize interviews #6-10 (retention patterns)
Agent 3 → Extract all direct quotes about pricing/value
Agent 1 → Analyze support tickets for top pain points (last 90 days)
Agent 2 → Review competitor app store reviews for differentiation gaps
Agent 3 → Synthesize sales team feedback from last 5 deal losses
Agent 1 → Research launch benchmarks for our category
Agent 2 → Draft competitive comparison for sales battle cards
Agent 3 → Review similar product launches for lessons learned
Too broad: "Analyze the market" — agent gets lost Specific: "Analyze Competitor X's pricing tiers and target segments"
No sources: Agent fabricates or guesses Sources provided: "Research their public pricing page and G2 reviews"
No output format: Agent returns unstructured wall of text Format specified: "Return as a table with these columns..."
Vague ask: "Tell me about competitors" Specific question: "What pricing model does each competitor use and which segments do they target?"
Related tasks grouped: Output of A needed for B, but dispatched in parallel Correct: Sequential if dependent, parallel only if independent
After agents return:
From a competitive strategy session: