القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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 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.
| name | meeting-team-sync |
| description | 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. |
A team sync aligns a team around status, blockers, decisions, and priorities for the coming period. Done well it creates clarity and momentum. Done poorly it's a meeting that could have been an email.
Core question every team sync should answer: "What does everyone need to know to do their best work this week?"
| Team Size | Cadence | Duration |
|---|---|---|
| 3-6 people | Weekly | 30 min |
| 7-12 people | Weekly | 45 min |
| 13-20 people | Weekly | 60 min |
| > 20 people | Consider splitting by sub-team | — |
Teams larger than 12 should split into sub-team syncs + a leads sync.
Each person (or work stream) answers 3 questions only:
Strict rule: No deep-diving on solutions here. Blockers get parked and addressed after the meeting or in a focused break-out.
Keep a "Parking Lot" section in your agenda doc for items that need follow-up.
Distribute a shared agenda doc before the meeting. Ask team members to pre-fill their status updates asynchronously.
Benefits:
Pre-meeting doc template:
Team Sync — [Date]
🏆 Win of the Week:
[Team lead fills in]
Status Updates (fill before the meeting):
[Name]:
✅ Done:
🔄 In Progress:
🚫 Blocked:
Parking Lot / Topics to Discuss:
-
Action Items from Last Week:
- [ ]
Items parked during the sync must be addressed within 24 hours:
Never let the parking lot become a graveyard of forgotten topics.
| Problem | Symptom | Fix |
|---|---|---|
| Status theater | Everyone recites long updates nobody uses | Require async pre-fill; use sync for blockers only |
| No decisions made | Team is "aligned" but nothing moves | Add "Decision needed" section explicitly |
| Meeting inflation | Keeps growing to 90 min | Time-cap each section; cut items ruthlessly |
| Same person dominates | One voice, others tune out | Rotating facilitator; explicit round-robin |
| No follow-through | Action items never reviewed | Open every sync by reviewing last week's items |
| Hybrid neglect | Remote people can't participate | Camera-on culture; repeat room questions aloud |
A healthy team sync improves over time. Watch: