---
name: meeting-minutes-action
description: Turn raw meeting notes, transcripts, and discussion logs into structured meeting minutes, decision summaries, and follow-up action items with owners and deadlines. Use this whenever users ask for meeting minutes, meeting summary, 議事録, 議事メモ整理, 打合せ記録, 決定事項整理, or follow-up tasks from a single meeting; use it for minutes and action tracking, not for periodic project or leadership status reporting.
---

# Meeting Minutes Action

## Overview

Transform raw meeting notes into structured meeting minutes and execution-ready action items.

This skill is for:
- Cross-functional meetings
- Customer/vendor alignment calls
- Internal project syncs
- Decision tracking and follow-up ownership

## Triggering Cues

Use this skill when user messages include:

- Chinese cues: 会议纪要、行动项、待办整理、负责人、截止日期、复盘纪要
- Japanese cues: 議事録、アクションアイテム、ToDo、担当者、期限、決定事項、宿題
- English cues: meeting minutes, action items, owners and deadlines, follow-up notes

## Input Requirements

Ask for or infer:

1. Raw notes/transcript
2. Meeting date and participants (if available)
3. Preferred output language (default: conversation language)
4. Whether to include unresolved issues / risks

## Output Format

Always output with these sections:

1. **Meeting Summary** (3-6 bullets)
2. **Decisions Made**
3. **Open Issues / Risks**
4. **Action Items Table**

Use this action table schema:

| ID | Action | Owner (担当) | Due Date (期限) | Dependency | Status |
|----|--------|--------------|-----------------|------------|--------|

## Workflow

1. Extract facts only; separate decisions from discussion.
2. Normalize action items into verb-first tasks.
3. Assign owner and due date when explicit; mark as TBD if missing.
4. Highlight blockers/dependencies.
5. Produce concise, enterprise-ready minutes.

## Examples

### Example 1
Input:
- 产品、研发、运营周会聊天记录，内容杂乱且有重复。

Output style:
- Clear decisions vs pending issues
- Action table with owner/deadline
- Enterprise concise wording

### Example 2
Input:
- 客户例会记录，需要发给日方客户确认。

Output style:
- Formal Japanese meeting minutes tone
- Neutral phrasing (avoid blame)
- Explicit next steps for both sides

## Guidelines

- Never invent decisions that were not stated.
- Mark unknown owner/date as TBD explicitly.
- Keep minutes objective and non-judgmental.
- Preserve Japanese enterprise structure even when output is non-Japanese.
