# X soft-mention (T-7 to T-3, pre-launch)

> Three single-tweet soft mentions to seed @bcherny, @alexalbert__, and @ClaudeDevs. Don't tag all three in one tweet; spread across 2–3 days. The goal is to put doc-wiki in their feed quietly before the launch, not to ask for amplification.

## Tweet 1 — to @bcherny (T-5 or T-4)

```
@bcherny been quietly building a Claude Code plugin called doc-wiki —
maintained wiki over code + Jira / Confluence / DB schemas (ER
diagrams from the real ORM models, auto cross-service map). Going
public next week, benchmark null published in full. Curious if the
slash-command surface feels right.

github.com/narailabs/doc-wiki
```

Boris regularly RTs plugins he likes; the ask here is for him to *see* the repo before launch.

## Tweet 2 — to @alexalbert__ (T-3 or T-2)

```
@alexalbert__ open-sourced doc-wiki this week — Apache 2.0 Claude Code
plugin that does ecosystem-aware context (code + Jira + Confluence +
DB schemas as one wiki). The Karpathy LLM Wiki pattern pointed at
complex enterprise code (works on small repos too). Benchmarked it
ourselves — null published in full in the repo.

github.com/narailabs/doc-wiki
```

Tagged on a different day than @bcherny tweet so they don't read as a coordinated push.

## Tweet 3 — to @ClaudeDevs (T-1)

```
@ClaudeDevs new plugin pre-launch: doc-wiki — keeps a structured wiki
over code + the entire ecosystem (Jira / Confluence / GitHub / GitLab
/ Notion / Linear / AWS/GCP / DB schemas). 8 slash commands, Apache
2.0 forever. We benchmarked it ourselves and published the null in
the repo.

Show HN going up Tuesday: github.com/narailabs/doc-wiki
```

## Notes

- **Order matters:** Boris → Alex → ClaudeDevs (descending personal-account size). Each is a slightly broader audience.
- **Spread the tweets 1–2 days apart.** Same-day soft-mentions look spammy.
- **Don't DM them about it.** They prefer public, optional engagement.
- **Don't follow up if no response.** The goal is awareness, not RT.
- **If any of them DOES quote-tweet or RT pre-launch:** thank them with one short reply, *don't* reschedule the launch around it. Stay on the Tuesday slot.
- **If they reply with a question or critique:** respond crisply, link to docs, offer a 30-min walk-through if useful.