solo-community-outreach

查找相关的 Reddit、HN 和 ProductHunt 主题，并通过启动清单起草价值优先的社区回复。当用户说“查找社区”、​​​​“草稿推广”、“Reddit 促销”、“ProductHunt 发布”或“社区营销”时使用。请勿用于社交媒体帖子（使用 /content-gen）或视频脚本（使用 /video-promo）。

# /community-outreach

Find relevant community threads (Reddit, Hacker News, ProductHunt) and draft contextual, value-first responses. NOT spam — genuine helpful answers that naturally mention the product.

## MCP Tools (use if available)

- `web_search(query, engines, include_raw_content)` — search Reddit, HN, web
- `kb_search(query)` — find related methodology
- `project_info(name)` — get project details

If MCP tools are not available, use WebSearch/WebFetch as fallback.

## Steps

1. **Parse project** from `$ARGUMENTS`.
   - Read PRD/README to understand: problem, solution, ICP, key features.
   - If empty: ask via AskUserQuestion.

2. **Extract search keywords:**
   - Problem keywords (what users complain about)
   - Solution keywords (what users search for)
   - Category keywords (the market/niche)
   - Competitor names (for "vs" and "alternative" threads)

3. **Search communities** (run searches in parallel):

   ### 3a. Reddit
   For each keyword group, search via MCP `web_search(query)` or WebSearch:
   - `"{problem} reddit"` — pain point threads
   - `"{solution category} recommendations reddit"` — recommendation requests
   - `"{competitor} alternative reddit"` — competitor frustration
   - `"{competitor} vs reddit"` — comparison threads

   For each result, extract: subreddit, title, URL, post date, comment count.
   Filter: prefer threads < 6 months old, > 5 comments (active).

   ### 3b. Hacker News
   Search via `site:news.ycombinator.com`:
   - `"Show HN: {similar product category}"` — similar launches
   - `"Ask HN: {problem domain}"` — questions in the space
   - `"{competitor name} site:news.ycombinator.com"` — competitor mentions

   Extract: title, URL, points, comment count.

   ### 3c. ProductHunt
   Search via `site:producthunt.com`:
   - `"{product category} site:producthunt.com"` — similar launches
   - `"{competitor} site:producthunt.com"` — competitor pages

   Extract: product names, launch dates, upvote counts, taglines.

   ### 3d. Other Communities (optional)
   - `site:indiehackers.com "{problem}"` — Indie Hackers
   - `site:dev.to "{solution category}"` — Dev.to (if technical product)

4. **Forced reasoning — outreach strategy:**
   Before drafting, write out:
   - **Best 5 threads** to engage with (highest relevance + activity)
   - **Tone per community:** Reddit (casual, self-deprecating), HN (technical, data-driven), PH (enthusiastic, builder)
   - **Value-first angle:** What genuine help can we offer BEFORE mentioning the product?
   - **Red lines:** No astroturfing, no fake accounts, always disclose you're the builder

5. **Draft responses** for top 5 threads:

   For each thread:
   ```markdown
   ### Thread: {title}
   **URL:** {url}
   **Subreddit/Community:** {community}
   **Why relevant:** {1 sentence}

   **Draft response:**
   {2-4 paragraph response that:
   - Directly addresses the question/problem
   - Provides genuine value (tips, experience, data)
   - Mentions the product naturally (last paragraph)
   - Includes "disclaimer: I'm the developer" for transparency
   }
   ```

6. **Generate ProductHunt launch checklist:**

   ```markdown
   ## ProductHunt Launch Checklist

   ### Pre-Launch (1 week before)
   - [ ] Hunter identified (or self-hunting)
   - [ ] Tagline ready (< 60 chars): "{tagline}"
   - [ ] Description ready (< 260 chars)
   - [ ] 5+ screenshots/GIF prepared
   - [ ] Maker comment drafted (story + problem + solution)
   - [ ] Launch day scheduled (Tuesday-Thursday, 00:01 PST)

   ### Launch Day
   - [ ] Post live and verified
   - [ ] Maker comment posted immediately
   - [ ] Share in relevant communities (not vote-begging)
   - [ ] Respond to all comments within 1 hour
   - [ ] Share progress on Twitter/LinkedIn

   ### Post-Launch
   - [ ] Thank supporters
   - [ ] Collect feedback from comments
   - [ ] Update product based on feedback
   ```

7. **Write outreach plan** to `docs/outreach-plan.md`:

   ```markdown
   # Community Outreach Plan: {Project Name}

   **Generated:** {YYYY-MM-DD}
   **Product:** {one-line description}
   **ICP:** {target persona}

   ## Target Communities

   | Community | Relevant Threads Found | Priority |
   |-----------|----------------------|----------|
   | r/{subreddit} | N | high/medium/low |
   | Hacker News | N | high/medium/low |
   | ProductHunt | N | high/medium/low |

   ## Top Threads to Engage

   {5 thread drafts from step 5}

   ## ProductHunt Launch Checklist

   {checklist from step 6}

   ## Search Keywords Used
   - {keyword1}: N results
   - {keyword2}: N results

   ---
   *Generated by /community-outreach. Review all drafts before posting.*
   ```

8. **Output summary** — communities found, top 3 threads to engage, PH readiness.

## Critical Rules

1. **Value first, product second** — every response must genuinely help the person
2. **Always disclose** — "I'm the developer" or "disclaimer: I built this"
3. **No vote manipulation** — never ask for upvotes
4. **No astroturfing** — never pretend to be a user
5. **Respect community rules** — check subreddit rules before posting
6. **Quality over quantity** — 5 great responses > 50 generic ones

## Common Issues

### Web search not available
**Cause:** MCP web_search tool not configured or WebSearch not accessible.
**Fix:** Use WebSearch/WebFetch as primary. For better results with engine routing (Reddit, HN), set up [SearXNG](https://github.com/fortunto2/searxng-docker-tavily-adapter) (private, self-hosted, free) and configure solograph MCP.

### No relevant threads found
**Cause:** Niche too small or wrong keywords.
**Fix:** Broaden search terms. Try competitor names, problem descriptions, or adjacent categories.

### Responses sound promotional
**Cause:** Product mention too prominent or lacks genuine value.
**Fix:** Rewrite with value-first approach: 80% helpful answer, 20% product mention. Always include builder disclosure.

---

## 中文说明

# /community-outreach

查找相关的社区主题（Reddit、Hacker News、ProductHunt），并起草贴合上下文、价值优先的回复。这不是垃圾信息——而是真正有帮助、自然提及产品的回答。

## MCP 工具（可用时使用）

- `web_search(query, engines, include_raw_content)` — 搜索 Reddit、HN、网络
- `kb_search(query)` — 查找相关方法论
- `project_info(name)` — 获取项目详情

如果 MCP 工具不可用，使用 WebSearch/WebFetch 作为后备。

## 步骤

1. **解析项目**，来源为 `$ARGUMENTS`。
   - 阅读 PRD/README 以理解：问题、解决方案、ICP、关键功能。
   - 如果为空：通过 AskUserQuestion 询问。

2. **提取搜索关键词：**
   - 问题关键词（用户抱怨什么）
   - 解决方案关键词（用户搜索什么）
   - 类别关键词（市场/细分领域）
   - 竞品名称（用于“vs”和“alternative”主题）

3. **搜索社区**（并行运行搜索）：

   ### 3a. Reddit
   对每个关键词组，通过 MCP `web_search(query)` 或 WebSearch 搜索：
   - `"{problem} reddit"` — 痛点主题
   - `"{solution category} recommendations reddit"` — 推荐请求
   - `"{competitor} alternative reddit"` — 竞品不满
   - `"{competitor} vs reddit"` — 比较主题

   对每个结果，提取：subreddit、标题、URL、发帖日期、评论数。
   过滤：优先选择 6 个月内、评论数 > 5（活跃）的主题。

   ### 3b. Hacker News
   通过 `site:news.ycombinator.com` 搜索：
   - `"Show HN: {similar product category}"` — 类似发布
   - `"Ask HN: {problem domain}"` — 该领域的问题
   - `"{competitor name} site:news.ycombinator.com"` — 竞品提及

   提取：标题、URL、点数、评论数。

   ### 3c. ProductHunt
   通过 `site:producthunt.com` 搜索：
   - `"{product category} site:producthunt.com"` — 类似发布
   - `"{competitor} site:producthunt.com"` — 竞品页面

   提取：产品名称、发布日期、点赞数、标语。

   ### 3d. 其他社区（可选）
   - `site:indiehackers.com "{problem}"` — Indie Hackers
   - `site:dev.to "{solution category}"` — Dev.to（如果是技术产品）

4. **强制推理——推广策略：**
   起草之前，写出：
   - **最佳 5 个主题**进行互动（最高相关性 + 活跃度）
   - **各社区的语气：** Reddit（随意、自嘲），HN（技术性、数据驱动），PH（热情、创造者）
   - **价值优先的切入点：** 在提及产品之前，我们能提供哪些真正的帮助？
   - **红线：** 不刷水军、不用假账号、始终表明你是创造者

5. **起草回复**，针对前 5 个主题：

   对每个主题：
   ```markdown
   ### Thread: {title}
   **URL:** {url}
   **Subreddit/Community:** {community}
   **Why relevant:** {1 sentence}

   **Draft response:**
   {2-4 paragraph response that:
   - Directly addresses the question/problem
   - Provides genuine value (tips, experience, data)
   - Mentions the product naturally (last paragraph)
   - Includes "disclaimer: I'm the developer" for transparency
   }
   ```