.archive/pmm-team/skills/market-analysis/SKILL.md
Systematic market analysis skill for understanding market size, segmentation, trends, and opportunities. Produces quantified market intelligence.
npx skillsauth add lerianstudio/ring market-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Systematic market analysis to understand size, segmentation, trends, and opportunities.
Market analysis provides the foundation for ALL subsequent PMM activities:
HARD GATE: Do NOT proceed to positioning or messaging without market analysis.
Define the market boundaries:
## Market Definition
**Product/Feature:** [What you're analyzing]
**Market Category:** [Existing category or new category creation]
**Geographic Scope:** [Global, regional, specific countries]
**Time Horizon:** [Current, 1-3 years, 5+ years]
### Market Boundaries
- **Included:** [What's in scope]
- **Excluded:** [What's explicitly out of scope]
- **Adjacent Markets:** [Related but distinct markets]
Quantify the market opportunity:
## Market Sizing
### Total Addressable Market (TAM)
**Definition:** Total market demand if 100% market share
**Size:** $X billion
**Calculation Method:** [Top-down/Bottom-up/Value theory]
**Sources:** [List data sources]
### Serviceable Addressable Market (SAM)
**Definition:** Portion of TAM you can actually serve
**Size:** $X million
**Limiting Factors:**
- Geographic: [Regions you can serve]
- Technical: [Segments your product can address]
- Go-to-market: [Segments you can reach]
### Serviceable Obtainable Market (SOM)
**Definition:** Realistic market share in 1-3 years
**Size:** $X million
**Assumptions:**
- Market share: X%
- Growth rate: X%
- Competitive dynamics: [Key assumptions]
Identify distinct market segments:
## Market Segmentation
### Segment 1: [Name]
**Size:** $X million (X% of SAM)
**Characteristics:**
- Company size: [Range]
- Industry: [Verticals]
- Pain points: [Top 3 pain points]
- Buying behavior: [How they buy]
**Attractiveness:** HIGH/MEDIUM/LOW
**Fit Score:** X/10
**Priority:** PRIMARY/SECONDARY/TERTIARY
### Segment 2: [Name]
[Repeat structure]
Analyze market dynamics:
## Market Trends
### Growth Drivers
| Driver | Impact | Timeline | Confidence |
|--------|--------|----------|------------|
| [Trend 1] | HIGH/MEDIUM/LOW | Near/Mid/Long | HIGH/MEDIUM/LOW |
| [Trend 2] | ... | ... | ... |
### Headwinds
| Challenge | Impact | Mitigation |
|-----------|--------|------------|
| [Challenge 1] | HIGH/MEDIUM/LOW | [How to address] |
| [Challenge 2] | ... | ... |
### Technology Trends
- [Emerging tech affecting market]
- [Adoption curves]
- [Disruption potential]
### Regulatory Trends
- [Current regulations]
- [Expected changes]
- [Compliance requirements]
Understand the target customer:
## Customer Analysis
### Ideal Customer Profile (ICP)
**Company Characteristics:**
- Size: [Employee count, revenue]
- Industry: [Verticals]
- Geography: [Regions]
- Tech stack: [Required technologies]
- Maturity: [Growth stage]
**Behavioral Indicators:**
- [Signal that indicates fit]
- [Signal that indicates readiness to buy]
### Buyer Personas
**Primary Buyer: [Title]**
- Role: [Responsibilities]
- Goals: [What they want to achieve]
- Pain points: [What keeps them up at night]
- Success metrics: [How they're measured]
- Objections: [Common concerns]
**Economic Buyer: [Title]**
[Repeat structure]
**Technical Evaluator: [Title]**
[Repeat structure]
# Market Analysis: [Product/Feature]
## Executive Summary
- **Market Size:** $X SAM, $X SOM
- **Growth Rate:** X% CAGR
- **Key Segments:** [Top 3 segments]
- **Primary Opportunity:** [One sentence]
- **Key Risk:** [One sentence]
## Market Definition
[Phase 1 output]
## Market Sizing
[Phase 2 output]
## Segmentation
[Phase 3 output]
## Trends
[Phase 4 output]
## Customer Analysis
[Phase 5 output]
## Recommendations
1. **Target Segment:** [Primary segment to pursue]
2. **Positioning Implications:** [What this means for positioning]
3. **GTM Implications:** [What this means for go-to-market]
4. **Risks to Monitor:** [Key uncertainties]
## Sources
- [Source 1]
- [Source 2]
| Blocker | Action | |---------|--------| | No TAM data available | STOP. Define methodology and assumptions. Request validation. | | Market definition unclear | STOP. Clarify boundaries before sizing. | | Conflicting market data | STOP. Document sources. Recommend reconciliation approach. | | No ICP definition | STOP. Cannot proceed without target customer clarity. |
See shared-patterns/anti-rationalization.md for universal anti-rationalizations.
| Rationalization | Why It's WRONG | Required Action | |-----------------|----------------|-----------------| | "TAM is just a big number game" | TAM informs investment decisions and positioning scope | Calculate with methodology and sources | | "Segmentation is obvious" | Obvious segments miss nuanced opportunities | Analyze systematically | | "User knows their market" | User knowledge + analysis > either alone | Augment with structured research | | "Market data is stale" | Stale data + analysis > no data | Document recency, proceed with caveats |
See shared-patterns/pressure-resistance.md for universal pressure scenarios.
| Pressure Type | Request | Agent Response | |---------------|---------|----------------| | "Skip to positioning" | "We know the market, just position" | "Positioning without market analysis is guessing. Completing market analysis." | | "Use competitor's TAM" | "Just use what [competitor] published" | "Competitor TAM serves their narrative. Calculating independent estimate." | | "Rough estimate is fine" | "Just ballpark it" | "Ballpark estimates cause bad decisions. Providing methodology-backed estimate." |
Base metrics per shared-patterns/execution-report.md:
| Metric | Value | |--------|-------| | Duration | Xm Ys | | Iterations | N | | Result | PASS/FAIL/PARTIAL |
development
Analyzes a Go service using lib-commons v2/v3 and generates a visual migration report showing every change needed to upgrade to lib-commons v4. Produces an interactive HTML page (via ring:visualize) and optionally generates refactoring tasks for ring:dev-cycle.
documentation
Patterns and structure for writing functional documentation including guides, conceptual explanations, tutorials, and best practices documentation.
development
Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation.
documentation
Voice and tone guidelines for technical documentation. Ensures consistent, clear, and human writing across all documentation.