launchnotes-draft-from-work
Use when the user wants to turn shipped or in-progress work into a LaunchNotes announcement — e.g. "draft an announcement for what we shipped this week", "write up the 2.4 release from Jira", "turn these merged GitHub PRs into a release note". Pulls the work from whatever sources are connected (trackers like Jira, Linear, GitHub, ClickUp, and flag tools like LaunchDarkly or PostHog), drafts a publish-ready announcement in the user's voice, categorizes it, links it to its roadmap item, and attaches the source issues — always leaving it as a draft for review. Start here when the subject is issues, PRs, or flags; if it's an existing roadmap item, use launchnotes-ship-the-roadmap. Not for backfilling a changelog (use launchnotes-import-existing-changelog) or reporting on how an announcement performed (use launchnotes-release-recap). Load launchnotes-use first.
Install
With your agent
Install OMGSkills skill "launchnotes/mcp-server-guide:skills/launchnotes-draft-from-work" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/launchnotes/mcp-server-guide /tmp/mcp-server-guide && ln -s /tmp/mcp-server-guide/skills/launchnotes-draft-from-work ~/.claude/skills/launchnotes-draft-from-workFrom README
Draft a LaunchNotes announcement from tracker work Turn completed (or about-to-ship) work into a ready-to-review announcement. You do the gathering, judgment, and drafting; the user publishes. Requires: the launchnotes-use skill loaded, a tracker MCP connected (Jira, Linear, GitHub, or ClickUp), and a target LaunchNotes project. If a feature-flag tool is connected (LaunchDarkly, PostHog, etc.), check it: shipped work isn't necessarily visible to customers until its flag is on. If no tracker is connected, ask the user to paste the work items rather than guessing. Steps Gather the work the user pointed at — by milestone, label, date range, or explicit IDs. Don't assume "shipped"; they may want to announce in-progress work. If a flag tool is connected, or the work mentions a flag, look for the flag behind this work and check its production rollout (ask the user if no tool is connected). If there is one, tell the user so they can decide how to frame it; if not, carry on.
More from this repo
launchnotes-feedback-to-roadmap
Used when the user wants to turn reader feedback into roadmap items — e.g.
launchnotes-import-existing-changelog
Used when the user wants to bring an existing changelog or blog into LaunchNotes — e.g.
launchnotes-post-roadmap-update
Used when the user wants to post a progress update to a roadmap item's timeline and notify the people following it —...