market-research
Market Research
Research existing products/competitors to inform product decisions.
When to Use
- Starting a new project and want to understand the landscape
- Cloning or improving upon an existing product
- Identifying gaps or differentiation opportunities
- Validating product direction against alternatives
Process
- Identify targets: List 3-5 existing products in the space
- Feature analysis: Document core features of each product
- Gap analysis: Identify what's missing or underserved
- Differentiation: Suggest unique value propositions
- Summarize findings for product decision-making
Research Areas
For each competitor/reference product:
- Core features: What does it do well?
- Target audience: Who uses it?
- Pricing model: Free/paid/freemium?
- Technical approach: Open source? What stack?
- UX patterns: What's the user experience like?
- Limitations: What are users complaining about?
Output Format
[MARKET RESEARCH COMPLETE]
Product space: [description]
Competitors analyzed:
1. [Product A]
- Core features: ...
- Strengths: ...
- Weaknesses: ...
2. [Product B]
- Core features: ...
- Strengths: ...
- Weaknesses: ...
Gap analysis:
- [Gap 1]: Description
- [Gap 2]: Description
Differentiation opportunities:
- [Opportunity 1]: How to stand out
- [Opportunity 2]: Underserved niche
Recommended baseline: [Product X] because [rationale]
Guidelines
- Use web search when available to gather current information
- Focus on products users would actually compare against
- Be honest about strong competitors
- Identify realistic differentiation (not just "do everything better")
More from b1tank/skills
diff-check
Author's cleanup checklist before committing or submitting a PR. Use before any commit or PR to ensure code is clean, focused, and ready for review. Checks for debug code, secrets, redundant changes, and scope creep.
13spec-template
9-section product specification template for defining software projects. Use when drafting a new spec.md, converting an idea into a structured specification, or reviewing spec completeness. Ensures consistent, comprehensive project definitions.
9decompose-task
Break large tasks (>100 lines) into atomic, verifiable sub-tasks. Use when a task scope is unclear, touches multiple files/modules, or exceeds comfortable single-commit size. Returns structured breakdown without implementing code.
8skill-name
Clear description of what this skill does and when to use it. Include specific triggers and contexts for when Claude should invoke this skill.
5clone-with-hash
Clone a local or remote git repo into a new folder with a short random hash suffix (e.g., -a1b2c3) and immediately create a new branch from a base branch. Use when a user wants a separate workspace to avoid conflicts, especially for parallel feature work or multiple local clones.
2