oss-launchlisted

# OSS Launch Take **one topic** (a release, a new project, a milestone) and produce **different, platform-native content for each target**, then publish through the gated `social-post` wrapper. One idea in, many tailored posts out — never the same blob copy-pasted everywhere. ## Voice (non-negotiable) - English, written for **developers**, in the project author's own voice. - **No hype, no marketing-speak.** State concrete technical value plainly. - Never invent metrics, stars, benchmarks, users, or endorsements. - At most 2 hashtags, and only where they're idiomatic (X). ## Workflow 1. **Gather the brief.** Read what's available: `README.md`, `CHANGELOG.md`, the GitHub release body, and the repo URL. Ask the user for the one-line angle if it isn't obvious (what's new / why it matters). Keep it small — do not scan the whole repo. 2. **Pick targets.** Confirm which platforms to publish to (default offer: X, Bluesky, Reddit; add dev.to when relevant). 3. **Draft per platform.** Write one file per target under `tmp/launch/<platform>.md` following the rules below. Each draft is genuinely rewritten for its platform — not a truncation of the X post. 4. **Review gate.** Show every draft to the user together. Let them edit. Do not proceed until they explicitly approve. 5. **Publish — only through this skill's `scripts/social-post`.** For each approved draft run the dry-run first, show it, then re-run with `--yes` after confirmation. Never call `crosspo