plugins/market-research/skills/researching-market/SKILL.md
Integrate Phase 0 and Phase 1A outputs into TAM/SAM/SOM sizing, buyer personas, and market entry signals. Run after `analyzing-source-project` and `researching-industry-landscape` (Phase 1B).
npx skillsauth add qte77/claude-code-utils-plugin researching-marketInstall 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.
Target: $ARGUMENTS
Phase 1B of the GTM pipeline. Depends on Phase 0 and Phase 1A. Integrates technical capability and competitive intelligence into strategic market sizing and buyer analysis.
Read config/mode.md before starting:
concise — Top-down TAM estimate, one primary persona, bullet entry signalsdetailed — Bottom-up + top-down sizing, 2-3 personas with full profiles, trend projectionsconservative — Use published analyst figures, conservative growth ratesambitious — Build bottom-up case for expansive TAM, highlight adjacenciesresults/phase-0/capability-profile.md — Source project capabilitiesresults/phase-1a/competitor-map.md — Competitive landscapeconfig/targets.md — Target market segmentsconfig/comments_research.md — Research scope constraintsconfig/mode.md — Style and approach settingsconfig/validation_criteria.md Phase 1B gatesWrite to results/phase-1b/:
market-analysis.md# Market Analysis
## Market Sizing
### TAM (Total Addressable Market)
- Estimate: $[X]B
- Methodology: [top-down / bottom-up]
- Source: [URL, year]
### SAM (Serviceable Addressable Market)
- Estimate: $[X]B
- Scope: [geography, segment, use case]
### SOM (Serviceable Obtainable Market — Year 1-3)
- Estimate: $[X]M
- Assumptions: [list]
## Growth Rate
- [X]% CAGR through [year] — Source: [URL]
## Buyer Personas
### Persona: [Name/Role]
- Title: [job title]
- Pain: [primary pain point]
- Budget authority: [Yes/No/Influence]
- Buying trigger: [what prompts purchase decision]
## Market Entry Signals
- [Signal] — Strength: [High/Medium/Low]
## Risks
- [Risk] — Likelihood: [H/M/L] — Mitigation: [approach]
config/targets.mddevelopment
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
development
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
development
Audits website accessibility for WCAG 2.1 AA compliance, generating findings and code fixes. Use when reviewing accessibility, keyboard navigation, screen reader compatibility, or inclusive design.
development
Writes tests following TDD (using vitest and @testing-library/react) best practices. Use when writing unit tests, integration tests, or component tests in TypeScript.