xiaohongshu
xiaohongshu
Write clear, impactful company announcements for any audience
Full skill instructions
The Announcement Drafter skill helps you create clear, well-structured announcements for any organizational change, update, or news. Whether you're announcing a new hire, policy change, product launch, organizational restructuring, or company milestone, this skill ensures your message is clear, appropriately toned, and drives the right response.
This skill understands that announcements are high-stakes communication. They set tone, manage expectations, and can significantly impact morale, adoption, or perception. The skill helps you balance transparency with tact, excitement with realism, and information with brevity.
Great announcements inform, engage, and motivate. They answer key questions before they're asked, acknowledge impact, and provide clear next steps. This skill makes creating them efficient while maintaining the quality and care they deserve.
| Action | Command/Trigger |
|---|---|
| New hire | "Draft announcement for new hire [name/role]" |
| Product launch | "Write product launch announcement for [product]" |
| Policy change | "Create announcement for new [policy] policy" |
| Org change | "Draft org restructuring announcement" |
| Milestone | "Write celebration announcement for [achievement]" |
| Incident | "Create incident announcement about [issue]" |
| Partnership | "Draft partnership announcement with [company]" |
| Event | "Write event announcement for [event name]" |
Subject: Please welcome [Name] to [Team/Company]!
Team,
I'm excited to announce that [Full Name] is joining [Company] as [Title] on [Team], starting [Date].
**About [First Name]:**
[2-3 sentences about background, experience, and what makes them awesome]
**In this role, [First Name] will:**
• [Responsibility 1]
• [Responsibility 2]
• [Responsibility 3]
[Personal touch: hobby, fun fact, or quote from them]
Please join me in welcoming [First Name] to the team!
[First Name], we're thrilled to have you aboard.
[Your name]
---
📧 [Email]
💬 [Slack: @username]
📍 [Location/Time zone]
Subject: 🚀 Introducing [Product Name]
Hi everyone,
Today we're launching [Product Name] - [one-sentence description of what it is and who it's for].
**The Problem:**
[2-3 sentences on the problem this solves]
**Our Solution:**
[Product Name] helps [target audience] [achieve specific outcome] by [unique approach].
**Key Features:**
• [Feature 1] - [Benefit]
• [Feature 2] - [Benefit]
• [Feature 3] - [Benefit]
**Availability:**
[Product Name] is available [now/starting Date] for [pricing/who can access].
→ [Primary CTA button/link]
**What This Means for You:**
[Specific relevance to internal audience]
**Next Steps:**
• [Date]: [Milestone]
• [Date]: [Milestone]
Huge thanks to [Teams/people] who made this happen!
Questions? [Contact/channel]
[Your name]
Subject: Update to [Policy Name] - Effective [Date]
Team,
We're making a change to our [policy area] policy, effective [Date].
**What's Changing:**
[Clear, concise explanation of the change]
**Why We're Making This Change:**
[Rationale - context and reasoning]
**What This Means for You:**
**If you [scenario A]:** [Impact and what to do]
**If you [scenario B]:** [Impact and what to do]
**How This Works:**
1. [Step or detail 1]
2. [Step or detail 2]
3. [Step or detail 3]
**Resources:**
• [Policy doc] → Link
• [FAQ] → Link
• [Support/contact info]
**Key Dates:**
• [Date]: [Milestone]
• [Date]: [Effective date]
**Questions?**
[Contact person/channel/office hours]
We believe this change will [positive outcome]. Thanks for your understanding as we make this transition.
[Your name]
Subject: Important Update: Changes to [Team/Department]
Team,
I want to share some important changes to [team/department] structure, effective [Date].
**What's Changing:**
[Clear explanation of the reorganization]
[Optional: Visual org chart]
**Why Now:**
[Context for timing and reasoning]
• Reason 1
• Reason 2
• Expected outcome
**What This Means:**
**For [Group A]:**
[Specific impact and changes]
Your new reporting structure: [Details]
**For [Group B]:**
[Specific impact and changes]
**Timeline:**
• [Date]: [Transition milestone]
• [Date]: [Completion]
• [Date]: [Review point]
**What Stays the Same:**
[Reassuring continuity points]
**Support During Transition:**
• [Resource 1]
• [Resource 2]
• [Office hours/Q&A session details]
I know change can be unsettling. [Acknowledge concerns]. We're committed to [supporting employees/making this smooth].
Questions? Please reach out to [contact] or join us for [Q&A session details].
[Your name]
Subject: 🎉 We Did It: [Milestone Achievement]
Team,
I'm thrilled to share that we just [achieved milestone]!
[Brief celebratory opening that captures the significance]
**By the Numbers:**
• [Metric 1]: [Impressive number]
• [Metric 2]: [Impressive number]
• [Metric 3]: [Impressive number]
**What This Means:**
[Impact and significance of the achievement]
**How We Got Here:**
[Brief story of the journey or key factors]
**Shoutouts:**
This wouldn't have been possible without:
• [Team/Person] for [specific contribution]
• [Team/Person] for [specific contribution]
• Everyone who [general contribution]
**Looking Ahead:**
[What's next or how this sets up future success]
Take a moment to celebrate this - you earned it! 🎉
[Optional: Details on celebration event/recognition]
[Your name]
Subject: [Status]: [Service] Issue - [Date/Time]
Hi everyone,
We're currently experiencing [brief description of issue] affecting [who/what].
**Status:** [Investigating / Identified / Monitoring / Resolved]
**Impact:**
• [What's affected]
• [What's not affected]
• [Estimated users impacted]
**What We Know:**
[Clear, factual description of the issue]
**What We're Doing:**
[Actions being taken to resolve]
**Timeline:**
• [Time]: Issue began
• [Time]: Team notified
• [Time]: [Key milestone]
• **ETA for resolution:** [Estimate or "working on it"]
**Workaround:**
[If available: temporary solution or alternative]
**Updates:**
We'll provide updates every [timeframe] or when status changes.
Follow along: [Status page link]
**For Customers:**
[Guidance on customer communication if relevant]
We know this is frustrating. Our team is working hard to resolve this as quickly as possible.
Questions? [Emergency contact]
[Your name]
---
**[Update cadence as situation evolves]**
Subject: Exciting News: [Company] Partners with [Partner]
Team,
I'm excited to announce that [Company] is partnering with [Partner Company]!
**About [Partner]:**
[2-3 sentences on who they are and what they do]
**The Partnership:**
Together, we'll [description of what partnership enables].
**What This Means:**
• [Benefit 1]
• [Benefit 2]
• [Benefit 3]
**Timeline:**
• [Date]: [Milestone]
• [Date]: [Launch/integration]
**For Our Customers:**
[How this benefits end users]
**Internally:**
[How this affects team/processes]
**Next Steps:**
[What happens now]
This partnership positions us to [strategic benefit]. Thanks to [teams/people] who made this happen.
[External announcement coming [date/time]]
[Your name]
| Announcement Type | Tone | Example Opening |
|---|---|---|
| Positive News | Excited, Celebratory | "I'm thrilled to share that..." |
| Policy Change | Clear, Supportive | "We're making a change to improve..." |
| Difficult News | Honest, Empathetic | "I want to share some difficult news..." |
| Incident | Transparent, Factual | "We're currently experiencing..." |
| Milestone | Proud, Grateful | "We did it! Thanks to all of you..." |
| New Hire | Welcoming, Warm | "Please join me in welcoming..." |
When the same news needs different announcements:
Executives/Leadership:
Employees/Internal:
Customers:
Public/Press:
For announcements about significant changes:
Before Announcing:
In the Announcement:
After Announcing:
Before sending any announcement:
Content
Tone
Completeness
Distribution
xiaohongshu
technical spec
product ux expert
database patterns
Conduct multi-agent task orchestration and workflow coordination.
Initialize project with Conductor artifacts (product definition,
Expert in web animations, transitions, and motion design using Framer Motion and CSS
Creates Mermaid and ASCII diagrams for flowcharts, architecture, ERDs, state machines, mindmaps, and more. Use when user mentions diagram, flowchart, mermaid, ASCII diagram, text diagram, terminal diagram, visualize, C4, mindmap, architecture diagram, sequence diagram, ERD, or needs visual docume...
PostgreSQL bindings for H3 hexagonal grid system. Use when working with H3 cells in Postgres, including spatial indexing, geometry/geography integration, and raster analysis.
Context-Driven Development skill for projects using Conductor. Use this skill when you detect a `conductor/` directory in the project, when working on tasks defined in a `plan.md` file, or when the user asks about tracks, specs, or plans. Automatically applies TDD workflow, tracks task completion...
Display project status, active tracks, and next actions
Official Stakpak application containerization standard operating procedure, a step-by-step guidline to properly dockerize applications. This is a rule book curated by the Stakpak Team.
Generate, edit, and beat-sync AI video with leading models in one workspace.
The world's fastest calendar for remote work
Transform Your Design with AI Designer by ImgCreator.ai
Revolutionizing Video Production with AI-Powered Creativity
Extend an image past the frame and let AI fill the new aspect ratio.
Discover your celebrity doppelgänger with StarByFace!
ChainClarity explains 700+ crypto whitepapers in plain English, with layered summaries, comparisons, research tools, alerts, and a $4.99 Pro plan.
Opus.ai: Revolutionize Your Web Experience