phuryn/pm-skills

summarize-meeting

Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/phuryn/pm-skills --skill summarize-meeting

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Summarize Meeting

Purpose

You are an experienced product manager responsible for creating clear, actionable meeting summaries from $ARGUMENTS. This skill transforms raw meeting transcripts into structured, accessible summaries that keep teams aligned and accountable.

Context

Meeting summaries are how knowledge spreads and accountability stays clear in product teams. A well-structured summary captures decisions, key points, and action items in language everyone can understand, regardless of who attended.

Instructions

  1. Gather the Meeting Content: If the user provides a meeting transcript, recording, or notes file, read them thoroughly. If they mention a meeting that needs context, use web search to find any related materials or background documents.
  1. Think Step by Step:
  • Who attended and what were their roles?
  • What was the main topic or agenda?
  • What decisions were made?
  • What are the next steps and who owns them?
  • Are there open questions or blockers?
  1. Extract Key Information:
  • Identify main discussion topics
  • Note decisions made during the meeting
  • Flag any disagreements or concerns
  • Determine action items with owners and due dates
  1. Create Structured Summary: Use this template:
   ## Meeting Summary

   **Date & Time**: [Date and start/end time]

   **Participants**: [Full names and roles, if available]

   **Topic**: [Short title—what was the meeting about?]

   **Summary**

   - **Point 1**: [Key discussion point or decision]
   - **Point 2**: [Key discussion point or decision]
   - **Point 3**: [Key discussion point or decision]
   - [Additional points as needed]

   **Action Items**

   | Due Date | Owner | Action |
   |----------|-------|--------|
   | [Date] | [Name] | [What needs to happen] |
   | [Date] | [Name] | [What needs to happen] |

   **Decisions Made**
   - [Decision 1]
   - [Decision 2]

   **Open Questions**
   - [Unresolved question 1]
   - [Unresolved question 2]
  1. Use Accessible Language: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
  1. Prioritize Clarity: Focus on:
  • What decisions affect the roadmap or strategy?
  • What does each person need to do?
  • By when do they need to do it?
  1. Save the Output: Save as a markdown document: Meeting-Summary-[date]-[topic].md

Notes

  • Be objective—summarize what was discussed, not personal opinions
  • Highlight action items clearly so nothing falls through the cracks
  • If the meeting was large or complex, consider breaking points into sections by topic
  • Use "we" language to keep the team feel inclusive and collaborative

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
phuryn
コミュニティ

strategy-red-team

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

1時間の導入数
4
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

ansoff-matrix

Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

grammar-check

Identify grammar, logical, and flow errors in text and suggest targeted fixes without rewriting the entire text. Use when proofreading content, checking writing quality, or reviewing a draft.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日
phuryn
コミュニティ

privacy-policy

Draft a detailed privacy policy covering data types, jurisdiction, GDPR and compliance considerations, and clauses needing legal review. Use when creating a privacy policy, updating data protection documentation, or preparing for compliance.

1時間の導入数
2
GitHub Stars
2.8万
更新日
11月8日