build-in-publiclisted

# Build in Public Turn a release into ready-to-edit launch copy. The skill reads the changelog since the previous release, learns the product's voice from the repo, and writes one English draft per channel — X/Twitter thread, LinkedIn post, and (for major releases) a Product Hunt launch kit — into `build-in-public/<tag>/`. It drafts, it never posts: you review the files, edit, and publish manually. ``` Resolve release → Changelog → Project context → Draft per channel → [you review the files] → Report + checklist ``` ## 1. Resolve what to announce - **Scope** — a whole **release** (a tag) or a single **feature/bug-fix branch**. Branch mode makes a focused "just shipped X / just fixed Y" post about one change (present tense, **no Product Hunt**); output goes to `build-in-public/<branch-slug>/`. Pick branch mode when the user names a branch, a feature, or a fix rather than a version. - **Tag** (release) — use the tag the user names. If none, list candidates (`git tag --sort=-v:refname | head`) and confirm the latest version tag. - **Branch** — use the branch the user names (or the current branch). Its base defaults to the repo's default branch; the post covers only the commits the branch adds. - **Major?** — a release is *major* when the tag is `vX.0.0` (semver major bump) or the user calls it a launch/major. Major releases get the Product Hunt kit; others (and all branch posts) get X + LinkedIn only. - **Series** — a repo may hold several tag series (e.g.