Analyze the relevance of new information (text, link, or document) to the current product/project
Analyzes new information's relevance to your product and provides structured recommendations.
/plugin marketplace add kjgarza/marketplace-claude/plugin install kjgarza-kjgarza-product-plugins-kjgarza-product@kjgarza/marketplace-claudeURL text or description of new informationAnalyze the relevance and implications of: $ARGUMENTS
This command helps product teams quickly assess whether new information—market news, competitor updates, research papers, user feedback, technology announcements, or any other signal—is relevant to their product strategy and requires action.
Systematically analyze the provided information and produce a structured relevance assessment with clear recommendations on whether and how to act as well as a few comments to share with the team.
If URL provided:
If text provided:
If reference to a document:
Score the information across multiple dimensions:
| Dimension | Score (1-5) | Criteria |
|---|---|---|
| Direct Relevance | Does this directly affect our product, users, or market? | |
| Timing Urgency | Do we need to act now, soon, or can this wait? | |
| Competitive Impact | Does this change our competitive position? | |
| Strategic Alignment | Does this affect our strategy or validate/invalidate assumptions? | |
| User Impact | Does this change what our users need or expect? |
Overall Relevance Score: Average of dimensions (1-5)
For relevant information, analyze:
Opportunities:
Threats:
Dependencies:
Based on relevance and implications, recommend:
Action Level:
Specific Actions:
## Summary
[2-3 sentence summary of the information and its source]
## Source Assessment
- **Type:** [News/Research/Competitor/Technology/User Feedback/Regulatory/Other]
- **Credibility:** [High/Medium/Low] — [Rationale]
- **Freshness:** [Publication date and timeliness]
## Relevance Assessment
| Dimension | Score | Rationale |
|-----------|-------|-----------|
| Direct Relevance | X/5 | [Brief explanation] |
| Timing Urgency | X/5 | [Brief explanation] |
| Competitive Impact | X/5 | [Brief explanation] |
| Strategic Alignment | X/5 | [Brief explanation] |
| User Impact | X/5 | [Brief explanation] |
**Overall Score:** X/5 — [Critical/High/Moderate/Low/Minimal]
## Key Implications
### Opportunities
- [Opportunity 1]
- [Opportunity 2]
### Threats
- [Threat 1]
- [Threat 2]
### Assumptions Affected
- [Assumption that may need revisiting]
## Recommendations
**Action Level:** [🔴 Act Now / 🟡 Act Soon / 🟢 Monitor / ⚪ Archive]
**Recommended Actions:**
1. [Specific action with owner if known]
2. [Specific action]
**Discussion Points:**
- [Question to raise with team]
**Related To:**
- [Current initiative or workstream this relates to]
When analyzing competitor news:
When analyzing technology changes:
When analyzing user signals:
When analyzing market changes:
When analyzing research papers:
User: /analyze-intel https://techcrunch.com/competitor-launches-ai-writing-assistant
[Command analyzes]:
- Fetches article content
- Identifies competitor and feature set
- Compares to current product roadmap
- Assesses overlap and differentiation
- Recommends team discussion points
User: /analyze-intel "Three users this week mentioned they want real-time collaboration in the editor"
[Command analyzes]:
- Parses the feedback
- Checks against current user research
- Assesses alignment with roadmap
- Evaluates effort vs. impact
- Recommends whether to investigate further
User: /analyze-intel OpenAI just released a new model with 2x context window
[Command analyzes]:
- Identifies technical implications
- Assesses impact on current architecture
- Evaluates migration effort
- Recommends adoption timeline
User: /analyze-intel https://arxiv.org/abs/2024.12345 - new approach to claim detection
[Command analyzes]:
- Fetches and parses paper abstract/content
- Assesses applicability to product
- Compares to current approach
- Evaluates implementation feasibility
- Recommends whether to investigate or adopt
Is the information directly about our product/users/market?
├── Yes → High baseline relevance, proceed with full analysis
└── No → Is it about adjacent space or enabling technology?
├── Yes → Moderate baseline, assess indirect implications
└── No → Low baseline, quick scan for any connection
├── Connection found → Elevate to moderate, analyze
└── No connection → Archive with minimal analysis
After analysis, consider:
Before finalizing analysis:
Overreacting to noise
Underreacting to weak signals
Competitor obsession
Analysis paralysis
Ignoring timing