📌 참고: 이 문서는 공식 Claude Code 문서의 원문 + 레퍼런스입니다.

• 원문 링크를 직접 사용하셔도 됩니다
• 이 파일을 .claude/skills/ 하위에 복사하여 스킬로 등록할 수도 있습니다

(2026.03.15 기준)

이 스킬은 첨부자료를 포함하고 있습니다. 사용 시 , 아래의 general-comms.md, 3p-updates.md, company-newsletter.md 도 같이 첨부하여 사용하세요.

이 스킬을 사용할 때

사내 커뮤니케이션을 작성할 때 다음 용도로 이 스킬을 사용하세요:

• 3P 업데이트 (Progress, Plans, Problems)
• 사내 뉴스레터
• FAQ 응답
• 상태 보고서
• 리더십 업데이트
• 프로젝트 업데이트
• 장애 보고서

이 스킬 사용 방법

사내 커뮤니케이션을 작성하려면:

1. 요청에서 커뮤니케이션 유형을 식별합니다
2. examples/ 디렉토리에서 해당하는 가이드라인 파일을 로드합니다:
   • examples/3p-updates.md - Progress/Plans/Problems 팀 업데이트용
   • examples/company-newsletter.md - 전사 뉴스레터용
   • examples/faq-answers.md - 자주 묻는 질문 답변용
   • examples/general-comms.md - 위의 유형에 명확히 해당하지 않는 기타 모든 것
3. 해당 파일의 구체적인 지침에 따라 서식, 어조, 내용 수집을 진행합니다

커뮤니케이션 유형이 기존 가이드라인과 일치하지 않는 경우, 원하는 형식에 대한 명확한 설명이나 추가 맥락을 요청하세요.

키워드

3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms

---

3p-updates.md

Instructions

You are being asked to write a 3P update. 3P updates stand for "Progress, Plans, Problems." The main audience is for executives, leadership, other teammates, etc. They're meant to be very succinct and to-the-point: think something you can read in 30-60sec or less. They're also for people with some, but not a lot of context on what the team does.

3Ps can cover a team of any size, ranging all the way up to the entire company. The bigger the team, the less granular the tasks should be. For example, "mobile team" might have "shipped feature" or "fixed bugs," whereas the company might have really meaty 3Ps, like "hired 20 new people" or "closed 10 new deals."

They represent the work of the team across a time period, almost always one week. They include three sections:

1. Progress: what the team has accomplished over the next time period. Focus mainly on things shipped, milestones achieved, tasks created, etc.
2. Plans: what the team plans to do over the next time period. Focus on what things are top-of-mind, really high priority, etc. for the team.
3. Problems: anything that is slowing the team down. This could be things like too few people, bugs or blockers that are preventing the team from moving forward, some deal that fell through, etc.

Before writing them, make sure that you know the team name. If it's not specified, you can ask explicitly what the team name you're writing for is.

Tools Available

Whenever possible, try to pull from available sources to get the information you need:

• Slack: posts from team members with their updates - ideally look for posts in large channels with lots of reactions
• Google Drive: docs written from critical team members with lots of views
• Email: emails with lots of responses of lots of content that seems relevant
• Calendar: non-recurring meetings that have a lot of importance, like product reviews, etc.

Try to gather as much context as you can, focusing on the things that covered the time period you're writing for:

• Progress: anything between a week ago and today
• Plans: anything from today to the next week
• Problems: anything between a week ago and today

If you don't have access, you can ask the user for things they want to cover. They might also include these things to you directly, in which case you're mostly just formatting for this particular format.

Workflow

1. Clarify scope: Confirm the team name and time period (usually past week for Progress/Problems, next
   week for Plans)
2. Gather information: Use available tools or ask the user directly
3. Draft the update: Follow the strict formatting guidelines
4. Review: Ensure it's concise (30-60 seconds to read) and data-driven

Formatting

The format is always the same, very strict formatting. Never use any formatting other than this. Pick an emoji that is fun and captures the vibe of the team and update.

[pick an emoji] [Team Name] (Dates Covered, usually a week)
Progress: [1-3 sentences of content]
Plans: [1-3 sentences of content]
Problems: [1-3 sentences of content]

Each section should be no more than 1-3 sentences: clear, to the point. It should be data-driven, and generally include metrics where possible. The tone should be very matter-of-fact, not super prose-heavy.

---

company-newsletter.md

Instructions

You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.

Ideally it includes the following attributes:

• Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
• Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
• Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"

Tools to use

If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.

• Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread
• Email: look for things from executives that discuss company-wide announcements
• Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include.
• Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc.
• External press: if you see references to articles or press we've received over the past week, that could be really cool too.

If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.

Sections

The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.

Prioritization

Focus on:

• Company-wide impact (not team-specific details)
• Announcements from leadership
• Major milestones and achievements
• Information that affects most employees
• External recognition or press

Avoid:

• Overly granular team updates (save those for 3Ps)
• Information only relevant to small groups
• Duplicate information already communicated

Example Formats

:megaphone: Company Announcements

• Announcement 1
• Announcement 2
• Announcement 3

:dart: Progress on Priorities

• Area 1
  • Sub-area 1
  • Sub-area 2
  • Sub-area 3
• Area 2
  • Sub-area 1
  • Sub-area 2
  • Sub-area 3
• Area 3
  • Sub-area 1
  • Sub-area 2
  • Sub-area 3

:pillar: Leadership Updates

• Post 1
• Post 2
• Post 3

:thread: Social Updates

• Update 1
• Update 2
• Update 3

---

general-comms.md

Instructions

You are being asked to write internal company communication that doesn't fit into the standard formats (3P
updates, newsletters, or FAQs).

Before proceeding:
1. Ask the user about their target audience
2. Understand the communication's purpose
3. Clarify the desired tone (formal, casual, urgent, informational)
4. Confirm any specific formatting requirements

Use these general principles:

• Be clear and concise
• Use active voice
• Put the most important information first
• Include relevant links and references
• Match the company's communication style