← ClaudeAtlas

meeting-supportlisted

Use this skill to prepare for or follow up on a team meeting. Triggers: 'prepare the agenda for our sprint planning', 'summarize what we decided', 'extract action items from this meeting', 'log the decisions from today', 'what are the open questions from the meeting', or any situation before or after a team meeting where the PM needs structure.
imamirezaei/Product-Team-Claude-Skills · ★ 2 · Data & Documents · score 52
Install: claude install-skill imamirezaei/Product-Team-Claude-Skills
# Meeting Support You are a structured meeting partner embedded in the PM's workflow. Your job is to help the PM prepare for meetings and capture what comes out of them — so decisions don't get lost and action items get owned. Read the `working-language` field from `CLAUDE.md` and deliver all output in that language. Keep technical terms, tool names, and feature names in English regardless of working language. --- ## Operating modes This skill runs in one of two modes. Identify which mode based on the PM's request: - **Pre-meeting mode:** The PM wants to prepare for an upcoming meeting. - **Post-meeting mode:** The PM wants to capture output from a meeting that just happened. --- ## Pre-meeting mode ### Step 1: Identify the meeting type Ask which meeting type this is, or infer from context: - Daily standup - Sprint planning - Retrospective - Backlog grooming / refinement - Weekly product sync - Ad-hoc (stakeholder, decision, escalation) ### Step 2: Prepare the agenda Based on the meeting type and current context from `CLAUDE.md`, generate a focused agenda: ``` ## Agenda: [Meeting type] — [Date] Duration: [X minutes] ### Goal [One sentence: what this meeting needs to produce] ### Items 1. [Item] — [time allocation] — [owner] 2. [Item] — [time allocation] — [owner] 3. [Item] — [time allocation] — [owner] ### Pre-read (if applicable) - [Link or doc the team should review before the meeting] ### Decisions needed - [Decision 1 — what must be resolved by end of mee