关于 Internal Memo Creator
Internal Memo Creator 是帮助员工和管理者撰写正式内部沟通文件的技能。它指导备忘录结构、语气、政策细节、行动请求和后续跟进。
主要功能
- 01标准备忘录结构
- 02政策文档编写
- 03行动请求规划
- 04语气与清晰度检查
- 05格式和分发建议
适用场景
- 01发布工作场所政策变更
- 02记录决策及其理由
- 03明确负责人和期限以请求行动
- 04总结会议决策与任务
安装
复制下面的命令,在终端中运行。
$
npx skills add https:/ / github.com/ eddiebe147/ claude-settings --skill internal-memo-creator安装后在 Claude Code 中输入/internal-memo-creator确认已加载。
详细介绍
内部备忘录撰写工具
内部备忘录撰写工具可帮助你撰写清晰、专业的公司内部沟通备忘录。无论你是要记录政策变更、分享重要信息、请求采取行动,还是传达决策,这项工具都能确保备忘录结构合理、语气得当,并达成沟通目标。
这项工具深知,备忘录是正式的内部文件。它们需要清晰、专业,能够留存记录,同时易于理解且便于执行。这项工具可帮助你在正式性与可读性之间取得平衡,确保信息得到接收和落实。
优秀的备忘录能够传达信息、留存记录并推动行动。它们提供必要背景,明确预期,并可作为参考文件。这项工具让备忘录撰写更高效,同时保持内部沟通所需的专业水准。
核心工作流
工作流 1:撰写标准备忘录
- 明确目的:了解需要传达什么
- 确定受众:明确哪些人需要收到备忘录
- 收集信息:整理需要传达的事实、决策或政策
- 构建备忘录结构:遵循标准备忘录格式
- 清晰撰写:使用专业且易于理解的语言
- 审核:检查内容是否清晰、完整,语气是否得当
工作流 2:记录政策
- 概述政策:明确将要变更或实施的内容
- 说明理由:解释制定该政策的原因
- 详细说明要求:具体说明预期要求
- 列出时间安排:明确生效日期
- 说明执行方式:解释违规后果或问责机制
- 提供资源:提供支持渠道或答疑联系人
工作流 3:撰写行动请求备忘录
- 明确请求:清晰说明需要对方做什么
- 提供背景:解释其重要性
- 设定截止日期:给出具体时间安排
- 明确责任归属:清楚说明各项职责
- 助力行动:提供资源或后续步骤
- 跟进落实情况:纳入问责措施
快速参考
| 操作 | 命令/触发语 |
|---|---|
| 政策备忘录 | “撰写一份关于新 [policy] 的备忘录” |
| 决策备忘录 | “创建一份记录 [decision] 的备忘录” |
| 行动请求 | “起草一份请求 [action] 的备忘录” |
| 信息备忘录 | “撰写一份关于 [topic] 的信息备忘录” |
| 公告 | “创建一份宣布 [news] 的备忘录” |
| 指令 | “为 [initiative] 撰写一份指令备忘录” |
| 状态更新 | “起草一份关于 [project] 的状态备忘录” |
| 会议摘要 | “创建一份总结 [meeting] 的备忘录” |
标准备忘录格式
MEMORANDUM
TO: [Recipient(s) - Name and Title]
FROM: [Sender - Name and Title]
DATE: [Full Date]
RE: [Subject - Clear, Specific Topic]
[Opening paragraph: State purpose clearly in first 1-2 sentences. Lead with the main point or action needed.]
[Body paragraphs: Provide necessary context, background, details, or rationale. Use headers and bullets for readability.]
[Closing paragraph: Summarize key points, restate action items if any, provide next steps or contact information.]
[Optional: Attachments or appendices listed]
备忘录类型与模板
模板 1:政策备忘录
MEMORANDUM
TO: All Employees
FROM: Sarah Chen, Chief People Officer
DATE: January 6, 2026
RE: Updated Remote Work Policy - Effective February 1, 2026
We are updating our remote work policy to provide more flexibility while maintaining team collaboration and productivity. This memo outlines the changes and what you need to know.
WHAT'S CHANGING
Effective February 1, 2026, all employees will have the option to work remotely up to three days per week, with a minimum of two days in the office for team collaboration.
Key changes:
• Employees may choose which days to work remotely (subject to team coordination)
• Core collaboration hours of 10 AM - 3 PM remain required for all
• In-office days should be coordinated with immediate team
• Monthly all-hands meetings require in-person attendance
WHY WE'RE MAKING THIS CHANGE
Our employee survey indicated that flexibility is a top priority, while our collaboration data shows that some in-person time is critical for team dynamics. This policy balances both needs.
WHAT YOU NEED TO DO
1. Review the full policy document (attached)
2. Coordinate with your manager on in-office days by January 20
3. Update your calendar to reflect your regular schedule
4. Ensure your home office setup meets our security requirements (IT checklist attached)
RESOURCES
• Full policy document: [Link]
• IT home office guide: [Link]
• FAQ: [Link]
• Questions: [email protected]
This policy will be reviewed quarterly and adjusted based on feedback and business needs.
Attachments:
1. Remote Work Policy (Full Document)
2. IT Security Requirements for Remote Work
3. Frequently Asked Questions
模板 2:决策备忘录
MEMORANDUM
TO: Product and Engineering Leadership
FROM: Michael Park, VP of Product
DATE: January 6, 2026
RE: Decision to Delay Q1 Feature Release
This memo documents the decision to delay the Q1 major feature release from February 15 to March 15, 2026, and outlines the rationale and next steps.
DECISION
We will delay the launch of the new analytics dashboard by four weeks, moving the release date from February 15 to March 15, 2026.
RATIONALE
This decision was made based on three factors:
1. Quality Concerns: QA testing revealed critical performance issues with large datasets that require additional engineering time to resolve properly.
2. Customer Feedback: Beta customer feedback indicated the need for additional customization options that would significantly improve adoption.
3. Resource Constraints: Two key engineers are out on planned leave in February, reducing our capacity to address issues during what would normally be a critical launch period.
IMPACT
• Sales team has been notified and customer commitments have been updated
• Marketing launch campaign will shift to align with new date
• Q2 roadmap will be adjusted to accommodate the timeline shift
• No impact to other Q1 deliverables
NEXT STEPS
1. Engineering to prioritize performance fixes and additional customization features
2. Product to update roadmap and communicate to stakeholders
3. Marketing to adjust launch campaign timeline
4. Sales enablement session rescheduled to week of March 10
ACTION ITEMS
| Action | Owner | Due Date |
|--------|-------|----------|
| Fix critical performance issues | @Eng Team | Feb 28 |
| Implement customization features | @Product Team | Feb 28 |
| Update customer communications | @Sales Leadership | Jan 10 |
| Revise launch campaign | @Marketing | Jan 15 |
| Update roadmap documentation | @Product Ops | Jan 8 |
QUESTIONS
For questions about this decision, please contact me directly or raise concerns in the #product-leadership channel.
模板 3:行动请求备忘录
MEMORANDUM
TO: All Department Heads
FROM: Alex Rodriguez, Chief Financial Officer
DATE: January 6, 2026
RE: Q1 Budget Review - Action Required by January 20
We are conducting our Q1 budget review and require updated forecasts from all departments. This memo outlines what we need and when.
ACTION REQUIRED
Each department head must submit:
1. Updated Q1 spend forecast
2. Variance explanation for any changes >10% from original budget
3. Q2-Q4 revised projections
4. Any new budget requests
DEADLINE: Friday, January 20, 2026, 5:00 PM
WHY THIS MATTERS
Our Q1 actual spend is tracking 15% below budget across several departments, while others are slightly over. We need accurate forecasts to:
• Reallocate resources to higher-priority initiatives
• Identify potential year-end budget shortfalls early
• Make informed decisions on new investment opportunities
HOW TO SUBMIT
Use the budget review template (linked below) and submit via the finance portal.
Template: [Link to template]
Portal: [Link to portal]
Guide: [Link to step-by-step guide]
WHAT TO INCLUDE
Your submission should cover:
1. Updated Q1 Forecast
- Revised spend by category
- Explanation of variances >10%
- Expected headcount changes
2. Q2-Q4 Projections
- Quarterly breakdown by category
- Major initiatives or projects
- Assumptions and dependencies
3. New Budget Requests
- Justification and business case
- Amount and timing
- Expected ROI or impact
SUPPORT AVAILABLE
Finance team office hours for questions:
• Tuesday, Jan 9: 2-4 PM (Conference Room A)
• Thursday, Jan 11: 10 AM-12 PM (Conference Room B)
• Or schedule 1:1: [email protected]
Late submissions may result in budget freezes for your department pending review.
Thank you for your prompt attention to this critical process.
模板 4:信息备忘录
MEMORANDUM
TO: All Staff
FROM: Jordan Lee, VP of Operations
DATE: January 6, 2026
RE: Office Renovation Schedule - January-March 2026
This memo provides information about upcoming office renovations, including timeline, impact, and accommodations.
OVERVIEW
We will be renovating the 3rd floor offices and common areas over the next three months to create more collaboration space, update technology infrastructure, and refresh the overall work environment.
TIMELINE
Phase 1: January 15-31
• Conference rooms 3A-3C closed
• 3rd floor kitchen closed
• Alternative spaces: 2nd and 4th floor conference rooms and kitchens
Phase 2: February 1-28
• East wing of 3rd floor closed
• Affected teams temporarily relocated to 5th floor
• Limited access to 3rd floor from 8 AM-6 PM
Phase 3: March 1-15
• West wing of 3rd floor closed
• Final installation and finishing
• Full floor reopens March 18
WHAT TO EXPECT
During renovation:
• Increased noise levels on 3rd floor
• Temporary relocation for some teams (direct notice sent separately)
• Limited parking on south side due to material deliveries
• Daily progress updates via Slack #office-renovations channel
ACCOMMODATIONS
• Remote work encouraged during noisiest periods (will be communicated 48 hours in advance)
• Temporary workspaces available on 5th floor
• Meeting room reservation system updated to reflect closures
• Additional coffee/snacks provided in 2nd and 4th floor kitchens
WHAT'S BEING UPDATED
The renovation includes:
• New collaborative workspaces with flexible seating
• Upgraded AV systems in all conference rooms
• Modernized kitchen with additional seating
• Fresh paint, flooring, and lighting
• Phone booths for private calls/focus work
QUESTIONS OR CONCERNS
• Facilities team: [email protected]
• Daily updates: #office-renovations on Slack
• Project lead: Taylor Martinez (ext. 1234)
We appreciate your patience during this improvement project. The end result will significantly enhance our work environment.
模板 5:会议摘要备忘录
MEMORANDUM
TO: Executive Leadership Team
FROM: Pat Davis, Chief of Staff
DATE: January 6, 2026
RE: Summary - Q1 Strategy Meeting (January 5, 2026)
This memo summarizes key decisions, action items, and next steps from yesterday's Q1 strategy meeting.
ATTENDEES
Present: CEO, CFO, CTO, CPO, CMO, VP Sales, VP People
Absent: COO (out on leave)
KEY DECISIONS
1. Q1 Company Goal: Prioritize enterprise customer expansion
- Target: 20 new enterprise customers (>$100K ARR each)
- All departments to align resources to support this goal
2. Hiring Freeze Exception: Approved 5 new enterprise sales roles
- Roles to be filled by end of January
- Budget reallocation from marketing approved
3. Product Roadmap Shift: Move enterprise features to top priority
- SSO/SAML integration moved up to February release
- Advanced reporting postponed to Q2
DISCUSSION HIGHLIGHTS
Enterprise Focus
Team aligned that enterprise expansion is critical for long-term growth. Current enterprise customers have 3x higher retention and 5x higher LTV than mid-market.
Resource Allocation
General agreement that short-term investment in enterprise sales will require some reallocation from other initiatives. Marketing and product teams committed to supporting the shift.
Competitive Position
Market window is favorable now, but we expect 2-3 competitors to launch similar enterprise features in Q2. Speed is essential.
ACTION ITEMS
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
| Finalize enterprise sales hiring plan | VP Sales | Jan 10 | In Progress |
| Reallocate $500K budget to sales | CFO | Jan 12 | Not Started |
| Reprioritize Q1 product roadmap | CPO | Jan 8 | In Progress |
| Create enterprise customer playbook | VP Sales | Jan 20 | Not Started |
| Communicate strategy shift to company | CEO | Jan 9 | Scheduled |
| Update OKRs to reflect new priority | All Leads | Jan 15 | Not Started |
NEXT STEPS
1. CEO to present strategy to full company at All-Hands (Jan 9)
2. Department leads to update team OKRs by Jan 15
3. Weekly check-ins on enterprise customer progress starting Jan 12
4. Full leadership team to reconvene Feb 2 to review progress
OPEN QUESTIONS
1. Should we adjust Q2 hiring plan now or wait for Q1 results?
- Decision deferred to February leadership meeting
2. What's our competitive response if [Competitor] launches first?
- Product and marketing to develop contingency plan by Jan 20
NEXT MEETING
February 2, 2026, 9:00 AM - 12:00 PM
Location: Conference Room A
Agenda: Q1 progress review, Q2 planning
For questions or clarifications on any items in this memo, please contact me directly.
模板 6:指令备忘录
MEMORANDUM
TO: All Managers and Team Leads
FROM: Jamie Thompson, CEO
DATE: January 6, 2026
RE: Implementation of Monthly Team Check-Ins - Required Starting February
Effective February 1, 2026, all managers and team leads are required to conduct monthly one-on-one check-ins with each of their direct reports.
REQUIREMENT
Each manager must:
• Schedule recurring 30-minute monthly check-ins with every direct report
• Use the provided check-in template to structure conversations
• Document key discussion points and action items
• Submit completion confirmation by 5th of following month
This is a mandatory management practice and will be included in manager performance reviews.
PURPOSE
These regular check-ins serve multiple critical functions:
• Provide consistent communication touchpoints
• Surface issues or concerns early
• Support career development and growth
• Build stronger manager-report relationships
• Ensure alignment on priorities and expectations
IMPLEMENTATION
Timeline:
• Jan 10: Manager training session (required attendance)
• Jan 15: Schedule check-ins for February
• Feb 1: First check-ins begin
• Mar 5: First completion report due
Resources Provided:
• Check-in conversation guide and template
• Manager training recording for those unable to attend live
• Sample questions and best practices
• Documentation system tutorial
EXPECTATIONS
What these check-ins should cover:
• Recent wins and challenges
• Progress on goals and projects
• Support needed from manager
• Career development and growth
• Feedback (both directions)
• Alignment on priorities
What makes a good check-in:
• Scheduled consistently (don't reschedule unless critical)
• Held in private, uninterrupted setting
• Employee-led agenda (their priorities first)
• Action items documented and followed up
• Confidential unless employee approves sharing
ACCOUNTABILITY
Compliance will be tracked:
• People Ops will monitor completion rates
• Missed check-ins must be documented with reason
• Managers with <80% completion rate will receive coaching
• Persistent non-compliance may result in leadership review
SUPPORT
• Manager training: Jan 10, 2-4 PM (Conference Room A + Zoom)
• Template and guide: [Link]
• Questions: [email protected]
• Coaching for difficult conversations available: [Link to schedule]
This practice is a core part of our management culture and leadership expectations. Thank you for prioritizing this important work.
写作最佳实践
开篇段落
- 立即说明目的
- 开门见山,不要先介绍背景
- 清楚说明这份备忘录的内容,以及读者为何需要阅读
- 最多写 2-3 句话
正文内容
- 使用标题组织信息
- 用项目符号和列表拆分文本
- 段落保持简短(3-4 句话)
- 先写关键信息,再补充细节
- 明确写出日期、数字和预期要求
结尾段落
- 总结关键行动事项
- 适用时重申截止日期
- 提供答疑联系人
- 适当时向读者致谢
语气指南
| 备忘录类型 | 语气 | 开篇示例 |
|---|---|---|
| 政策 | 专业、清晰 | “我们正在实施一项关于……的新政策。” |
| 决策 | 客观、直接 | “本备忘录记录了……的决策。” |
| 行动请求 | 清晰、紧迫 | “我们需要您就……提供意见。” |
| 信息通知 | 乐于助人、直截了当 | “本备忘录提供有关……的信息。” |
| 指令 | 权威、专业 | “自 [日期] 起,所有员工都必须……” |
格式设置最佳实践
标题的使用
将内容拆分为易于阅读的章节:
- 主要章节使用全大写
- 子章节使用标题式大小写
- 帮助读者快速浏览
列表和项目符号
适用于:
- 多个相关事项
- 行动事项
- 要求或步骤
- 关键要点或结论
表格
适用于展示:
- 包含负责人和日期的行动事项
- 比较内容
- 时间线或日程安排
- 多项数据
留白
- 避免文字密密麻麻
- 在章节之间换行
- 留出页边距以提高可读性
- 让版面更易于阅读
应避免的常见问题
- 重点埋得太深:先讲重点,不要拖到第 3 段才说
- 背景信息过多:简明扼要地提供相关背景
- 措辞含糊:明确说明期望、日期和行动
- 没有明确负责人:始终指定责任人
- 缺少截止日期:提供具体日期,不要写“尽快”或“越快越好”
- 过于随意:备忘录是正式文件
- 过于正式:不要写得像法律合同
- 没有后续信息:始终提供联系人或下一步安排
- 默认读者了解背景:解释背景,不要假设所有人都知道
- 遗漏附件:提及并附上所有相关文件
分发最佳实践
发送给谁
- 仅发送给需要了解的人
- 抄送应当知情的人
- 面向广泛受众时使用分发列表
- 可考虑为不同受众准备不同版本
如何发送
- 大多数内部备忘录使用电子邮件发送
- 非常正式或需要留档的文件使用打印件
- 将文件发布到共享云盘/内联网,供人查阅
- 在相关渠道(Slack、Teams)发布通知
何时发送
- 为提高可见度,最好在周二至周四的上午中段发送
- 避免在周一(事务繁忙)和周五(临近周末)发送
- 在截止日期前留出充足时间
- 避免在重大活动或节假日期间发送
后续跟进
- 对需要采取行动的备忘录发送提醒
- 跟进所请求行动的完成情况
- 随时解答问题
- 信息发生变化时及时更新
记录保存
备忘录是正式文件记录:
归档内容:
- 所有政策备忘录
- 决策记录
- 重要公告
- 指令和要求
存储位置:
- 公司共享云盘
- 文档管理系统
- 政策相关内容存入员工手册
- 部门专属文件夹
保存期限:
- 政策:被替代后再保存 1 年
- 决策:永久归档
- 行动请求:完成后再保存 3 个月
- 信息通知:至少保存 1 年
集成方式
- 文档管理:SharePoint、Google Drive、Notion
- 电子邮件系统:Outlook、Gmail
- 协作工具:从 Slack、Teams 添加链接
- 人力资源系统:将政策备忘录纳入员工手册
- 项目管理:链接到相关项目或计划
- 日历:添加截止日期和跟进事项
评论
支持 Markdown