القائمة
Plan and run a company or department all-hands meeting. Use when preparing for a quarterly all-hands, town hall, or company-wide meeting where leadership addresses the full organization.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | meeting-all-hands |
| description | Plan and run a company or department all-hands meeting. Use when preparing for a quarterly all-hands, town hall, or company-wide meeting where leadership addresses the full organization. |
An all-hands is a leadership communication event. Its purpose is to:
What it is NOT: A collection of department status updates read off a slide.
| Scale | Format Recommendation |
|---|---|
| < 50 people | Single room or video call; high interactivity possible |
| 50-200 people | Auditorium or large video call; moderate interactivity |
| 200-500 people | Video production quality needed; structured Q&A |
| 500+ people | Broadcast model; pre-screened Q&A; breakout by team after |
| Frequency | Best For |
|---|---|
| Monthly | Fast-moving startups, high uncertainty periods |
| Quarterly | Most companies — aligns with business cadence |
| Bi-annual | Large orgs; supplement with team-level all-hands |
| Mistake | Impact | Fix |
|---|---|---|
| Pure status update format | Employees feel like they got a report, not a conversation | Lead with narrative, not metrics |
| No hard topics addressed | Erodes trust — employees know what's happening | Name the elephant in the room |
| No Q&A or filtered Q&A | Signals leadership doesn't want accountability | Open, anonymous, unfiltered |
| Too long (>90 min) | Attention collapses; message is lost | Hard cap at 75 min; cut content, not Q&A |
| Generic recognition | Feels performative | Specific names + specific actions |
| No follow-through on Q&A commitments | Trust killer | Assign owners; publish answers async |
Plan and run a customer meeting — discovery call, demo, business review, or renewal conversation. Use when preparing for any external meeting with a customer, prospect, or client.
Plan and run a daily standup (daily scrum). Use when structuring a daily standup ritual for an engineering team, product team, or any group that runs daily check-ins.
Plan and run effective 1:1 meetings between a manager and a direct report (or peer). Use when preparing for a one-on-one, building a recurring 1:1 agenda, or coaching on how to make 1:1s valuable.
Plan and run a recurring team sync (weekly or bi-weekly team meeting). Use when structuring a team standup, weekly sync, or sprint review meeting for an ongoing team.
Plan podcast episodes — structure, talking points, guest prep, show notes, and distribution strategy. Use when the user wants to create a new podcast episode, prepare for a guest interview, or launch a podcast series.
Plan and deliver high-impact presentations to senior executives and decision-makers — C-suite, VPs, boards, steering committees, and investment committees. Use when a user is preparing to present a strategy, project status, budget ask, proposal, or decision brief to people who are time-pressured and focused on business outcomes.
