community-demand-prospecting

# Community Demand Prospecting

## Overview

Turn vague growth ideas into a repeatable workflow: find relevant community conversations, estimate intent, avoid bad-fit threads, and draft replies that help first and promote only when appropriate.

Default to human-in-the-loop. This skill is for demand capture and community prospecting, not mass posting or deceptive automation.

It is especially useful for repo audit, launch readiness, market research, competitor research, positioning, finding users for a product, and planning Reddit or X outreach.

## Quick Start

Collect a compact product brief before doing outreach research. Ask for only what is missing:

- Product name and one-line description
- Target user or buyer
- Main pain points solved
- Best differentiators
- Allowed claims and forbidden claims
- Desired tone
- Destination link, demo, or CTA

If the user has not provided a brief, use the template in `assets/product-brief-template.md`.

If the user only provides a repository, landing page, or README, start with a launch-readiness audit and market scan before doing community prospecting. Use:

- `references/repo-launch-readiness.md`
- `references/market-research.md`
- `references/positioning-heuristics.md`
- `assets/repo-audit-template.md`
- `assets/market-scan-template.md`
- `assets/positioning-brief-template.md`

## Operating Sequence

Run the skill in this order unless the user explicitly asks for a narrower deliverable:

1. Extract or complete the product brief.
2. Audit launch readiness if the input is a repo, README, or rough landing page.
3. Research users, competitors, substitutes, and category shape.
4. Choose one primary positioning angle.
5. Translate the product into user pain-language.
6. Generate search queries and locate candidate threads.
7. Score each thread for intent and risk.
8. Choose the engagement ladder.
9. Draft outreach in platform-native style.
10. Return a decision-oriented report.

## Concrete Example

Example request:

```text
I b...