What problem does it solve? Writing launch posts and project announcements often leads to overclaiming, invented metrics, or vague marketing language that erodes reader trust. This Skill produces factual drafts that clearly separate shipped work from plans and keep every claim grounded in evidence. ## Core Features & Use Cases - Audience and platform targeting: Establishes the audience, platform, and state of the work (release, merged change, open PR, or plan) before drafting. - Evidence-based claims: Requires verification of revisions, demos, and project links before stating availability, and rejects fabricated testimonials, adoption numbers, or performance claims. - Length and CTA discipline: Measures drafts against platform character limits and prefers one relevant invitation over competing calls to action. - Use Case: After merging a --dry-run feature tested only on Linux, generate a launch post that announces the preview mode, notes the untested Windows support, and invites users to report issues. ## Quick Start Draft a launch post for my project's new dry-run feature, noting it is tested on Linux but not Windows.