Summarize a meeting transcript into structured notes with date, participants, topic, key decisions, summary points, and action items. Use when processing meeting recordings, creating meeting notes, writing meeting minutes, or recapping discussions.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
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.
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.
Think Step by Step:
Extract Key Information:
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]
Use Accessible Language: Write for a primary school graduate. Use simple terms. Avoid jargon or explain it briefly.
Prioritize Clarity: Focus on:
Save the Output: Save as a markdown document: Meeting-Summary-[date]-[topic].md
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
日本語の概要は準備中です。原文の説明を表示しています。