track-meeting

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Track Meeting Skill

When to use this Skill

何时使用该Skill

Activate when the user:

Mentions creating or recording meeting notes
Uses keywords: "meeting", "standup", "retrospective", "planning", "review"
Wants to document a team discussion
Needs to track meeting action items
References specific meeting types (daily standup, sprint planning, etc.)

当用户出现以下情况时激活：

提及创建或记录会议笔记
使用关键词：“meeting”、“standup”、“retrospective”、“planning”、“review”
想要记录团队讨论内容
需要跟踪会议行动项
提及特定会议类型（每日站会、迭代规划会等）

Workflow

工作流程

Phase 1: Context Discovery

阶段1：上下文发现

Objective: Understand the project context and meeting format requirements.

Steps:

Locate project RULE.md:

bash

# Check current directory
ls RULE.md
# If not found, check parent directories
ls ../RULE.md
ls ../../RULE.md

Read RULE.md using

Read

tool:

Extract
```
methodology
```
field (determines meeting types)

Find

Document Templates > Meeting Notes Format

section

Note
```
file_naming_convention
```
pattern
Check
```
meetings/
```
directory structure

Read

Auto Workflows > When Claude creates meeting notes

section

Determine meeting types available based on methodology:
- Scrum: daily-standups, sprint-planning, sprint-reviews, retrospectives, general
- Kanban: board-reviews, planning, general
- Waterfall: phase-reviews, status-updates, general
- Agile/Hybrid: planning, reviews, general
Check existing meetings directory:
bash
```
ls -la meetings/
```
Understand the current structure and recent meetings.
Read meetings/README.md if exists:
- Understand current meeting index
- Note recent meetings for context

Example:

Found RULE.md:
- Methodology: Scrum (2-week sprints)
- Meeting types: daily-standups, sprint-planning, sprint-reviews, retrospectives
- Format: Structured with YAML frontmatter
- Naming: Date-prefixed (YYYY-MM-DD_meeting-name.md)
- Directory: meetings/{type}/

目标：了解项目上下文和会议格式要求。

步骤：

定位项目RULE.md：

bash

# 检查当前目录
ls RULE.md
# 如果未找到，检查上级目录
ls ../RULE.md
ls ../../RULE.md

使用Read工具读取RULE.md：
- 提取
```
methodology
```
  字段（用于确定会议类型）
- 查找
```
Document Templates > Meeting Notes Format
```
  章节
- 记录
```
file_naming_convention
```
  命名规则
- 检查
```
meetings/
```
  目录结构
- 阅读
```
Auto Workflows > When Claude creates meeting notes
```
  章节
根据方法论确定可用的会议类型：
- Scrum：daily-standups、sprint-planning、sprint-reviews、retrospectives、general
- Kanban：board-reviews、planning、general
- Waterfall：phase-reviews、status-updates、general
- Agile/Hybrid：planning、reviews、general
检查现有meetings目录：
bash
```
ls -la meetings/
```
了解当前目录结构和近期会议情况。
如果存在，读取meetings/README.md：
- 了解当前会议索引
- 记录近期会议以获取上下文

示例：

找到RULE.md：
- 方法论：Scrum（2周迭代）
- 会议类型：daily-standups、sprint-planning、sprint-reviews、retrospectives
- 格式：带YAML前置元数据的结构化格式
- 命名规则：日期前缀（YYYY-MM-DD_meeting-name.md）
- 目录：meetings/{type}/

Phase 2: Gather Meeting Details

阶段2：收集会议详情

Objective: Collect all necessary information about the meeting.

Steps:

Extract from user message (if provided):
- Meeting type (standup, planning, etc.)
- Date (today if not specified)
- Meeting title or topic

Prompt for missing information:

Meeting type (if not clear):

What type of meeting is this?
[Present options based on RULE.md methodology]
- Daily Standup
- Sprint Planning
- Sprint Review
- Retrospective
- General/Other

Meeting title (if not provided):

What's the meeting title?
Example: "Sprint 5 Planning" or "Q4 Roadmap Discussion"

Date (if not provided):

Meeting date? (Press Enter for today: YYYY-MM-DD)

Attendees:

Who attended? (You can list names or reference team roles from RULE.md)
Example: "@alice @bob @carol" or "Whole dev team"

Duration (optional):

How long was the meeting? (optional, in minutes)

Prepare meeting metadata:
- Generate filename per RULE.md convention
- Determine target directory (e.g.,
```
meetings/sprint-planning/
```
  )
- Extract current date if not specified
- Default duration if not provided

Example:

Gathered:
- Type: Sprint Planning
- Title: "Sprint 5 Planning"
- Date: 2025-11-13
- Attendees: Alice (PO), Bob (SM), Carol, David, Eve, Frank (devs)
- Duration: 90 minutes
- Filename: 2025-11-13_sprint-5-planning.md
- Target: meetings/sprint-planning/

目标：收集关于会议的所有必要信息。

步骤：

从用户消息中提取信息（如果提供）：
- 会议类型（站会、规划会等）
- 日期（未指定则为今日）
- 会议标题或主题

提示用户补充缺失的信息：

会议类型（如果不明确）：

这是什么类型的会议？
[根据RULE.md方法论提供选项]
- 每日站会
- 迭代规划会
- 迭代评审会
- 回顾会
- 通用/其他

会议标题（如果未提供）：

会议标题是什么？
示例：“Sprint 5 规划会”或“Q4路线图讨论”

日期（如果未提供）：

会议日期？（按回车键使用今日日期：YYYY-MM-DD）

参会人员：

哪些人参加了会议？（可以列出姓名或引用RULE.md中的团队角色）
示例：“@alice @bob @carol”或“整个开发团队”

时长（可选）：

会议持续了多久？（可选，以分钟为单位）

准备会议元数据：
- 根据RULE.md的命名规则生成文件名
- 确定目标目录（例如：
```
meetings/sprint-planning/
```
  ）
- 未指定日期则提取当前日期
- 未提供时长则使用默认值

示例：

已收集信息：
- 类型：迭代规划会
- 标题：“Sprint 5 规划会”
- 日期：2025-11-13
- 参会人员：Alice（PO）、Bob（SM）、Carol、David、Eve、Frank（开发人员）
- 时长：90分钟
- 文件名：2025-11-13_sprint-5-planning.md
- 目标目录：meetings/sprint-planning/

Phase 3: Create Meeting Structure

阶段3：创建会议结构

Objective: Generate the meeting note with proper template.

Steps:

Read template from RULE.md: Extract the exact format from
```
Document Templates > Meeting Notes Format
```
.

Generate meeting document following template:

For Structured format (most common):

markdown

---
title: [Meeting Title]
type: [meeting-type]
date: YYYY-MM-DD
attendees:
  - Name 1
  - Name 2
duration_minutes: [number]
related_sprint: [sprint number or "N/A"]
related_milestone: [milestone or "N/A"]
---

# [Meeting Title]

**Date**: YYYY-MM-DD
**Type**: [Type]
**Duration**: [X] minutes

## Attendees
- Name 1
- Name 2

## Agenda
[To be filled or pre-populated if provided]

## Discussion
[Meeting notes and key points]

## Action Items
[Will be extracted or added]

## Decisions
[Key decisions made during the meeting]

## Next Steps
[What happens next]

---
*Created by ProjectMaster track-meeting Skill*

For Simple format:

markdown

# [Meeting Title]

**Date**: YYYY-MM-DD
**Attendees**: Names

## Notes
[Content]

## Action Items
- [ ] Item 1
- [ ] Item 2

## Decisions
[Decisions]

For Table format:

markdown

# [Meeting Title]

| Field | Value |
|-------|-------|
| Date | YYYY-MM-DD |
| Type | [Type] |
| Attendees | Names |
| Duration | X mins |

## Discussion Points

| Topic | Notes | Owner |
|-------|-------|-------|
| [Topic 1] | [Notes] | @name |

## Action Items

| Task | Owner | Due Date | Status |
|------|-------|----------|--------|
| [Task] | @name | YYYY-MM-DD | [ ] |

Determine content source:

If user provides content directly:
- Fill template with provided information
- Parse for action items
- Extract decisions
If creating empty template:
- Leave sections as prompts
- User will fill in later
If user provides partial information:
- Fill what's available
- Mark sections for completion:
```
[To be filled]
```

目标：使用合适的模板生成会议笔记。

步骤：

从RULE.md中读取模板：从
```
Document Templates > Meeting Notes Format
```
中提取确切格式。

按照模板生成会议文档：

结构化格式（最常用）：

markdown

---
title: [会议标题]
type: [meeting-type]
date: YYYY-MM-DD
attendees:
  - 姓名1
  - 姓名2
duration_minutes: [数字]
related_sprint: [迭代编号或“N/A”]
related_milestone: [里程碑或“N/A”]
---

# [会议标题]

**日期**：YYYY-MM-DD
**类型**：[类型]
**时长**：[X]分钟

## 参会人员
- 姓名1
- 姓名2

## 议程
[待填写或如果已提供则预先填充]

## 讨论内容
[会议笔记和关键点]

## 行动项
[将被提取或添加]

## 决策结果
[会议期间做出的关键决策]

## 后续步骤
[接下来的安排]

---
*由ProjectMaster track-meeting Skill创建*

简洁格式：

markdown

# [会议标题]

**日期**：YYYY-MM-DD
**参会人员**：姓名列表

## 笔记
[内容]

## 行动项
- [ ] 项1
- [ ] 项2

## 决策结果
[决策内容]

表格格式：

markdown

# [会议标题]

| 字段 | 值 |
|-------|-------|
| 日期 | YYYY-MM-DD |
| 类型 | [Type] |
| 参会人员 | 姓名列表 |
| 时长 | X分钟 |

## 讨论要点

| 主题 | 笔记 | 负责人 |
|-------|-------|-------|
| [主题1] | [笔记] | @name |

## 行动项

| 任务 | 负责人 | 截止日期 | 状态 |
|------|-------|----------|--------|
| [任务] | @name | YYYY-MM-DD | [ ] |

确定内容来源：

如果用户直接提供内容：
- 将提供的信息填充到模板中
- 解析内容以提取行动项
- 提取决策结果
如果创建空模板：
- 将章节留作提示内容
- 用户后续自行填写
如果用户提供部分信息：
- 填充已有的信息
- 标记待完成的章节：
```
[待填写]
```

Phase 4: Action Item Extraction

阶段4：行动项提取

Objective: Automatically identify and format action items.

Steps:

Scan user-provided content for action items:
- Lines starting with "TODO", "Action:", "[ ]", "-[ ]"
- Phrases like "needs to", "should", "must", "will [do]"
- @mentions indicating assignments
- Date mentions indicating deadlines

Extract action items:

Pattern detection:
- "Bob will update the database schema" → @bob: Update database schema
- "TODO: Review PR #123" → Review PR #123
- "Alice needs to finalize designs by Friday" → @alice: Finalize designs - due: [next Friday]

Format as task list:

markdown

## Action Items
- [ ] [Task description] - @[owner] - due: YYYY-MM-DD
- [ ] [Task description] - @[owner] - due: YYYY-MM-DD

If no owner specified: Leave as

- [ ] [Task]

If no due date: Omit due date or use "TBD"

Ask user to confirm/modify action items:

I've extracted these action items:
1. @bob: Update database schema - due: 2025-11-20
2. @alice: Finalize designs - due: 2025-11-15
3. Review PR #123 - no owner assigned

Are these correct? Any additions or changes?

Update based on feedback.

目标：自动识别并格式化行动项。

步骤：

扫描用户提供的内容以查找行动项：
- 以“TODO”、“Action:”、“[ ]”、“-[ ]”开头的行
- 类似“需要”、“应该”、“必须”、“将[执行]”这样的短语
- 表示任务分配的@提及
- 表示截止日期的日期提及

提取行动项：

模式检测：
- “Bob will update the database schema” → @bob: 更新数据库架构
- “TODO: Review PR #123” → 评审PR #123
- “Alice needs to finalize designs by Friday” → @alice: 最终确定设计 - 截止日期：[下周五]

格式化为任务列表：

markdown

## 行动项
- [ ] [任务描述] - @[负责人] - 截止日期：YYYY-MM-DD
- [ ] [任务描述] - @[负责人] - 截止日期：YYYY-MM-DD

如果未指定负责人：保留为

- [ ] [任务]

如果未指定截止日期：省略截止日期或使用“待确定”

请用户确认/修改行动项：

我已提取以下行动项：
1. @bob: 更新数据库架构 - 截止日期：2025-11-20
2. @alice: 最终确定设计 - 截止日期：2025-11-15
3. 评审PR #123 - 未分配负责人

这些是否正确？是否需要添加或修改？

根据反馈更新内容。

Phase 5: Cross-Reference Linking

阶段5：交叉引用链接

Objective: Link meeting to related project artifacts.

Steps:

Identify related items from meeting content:
- Sprint numbers (e.g., "Sprint 5")
- Milestone names
- Issue numbers (#123)
- Document references
- Previous meeting references

Check if items exist:

bash

# For sprint reference
ls sprints/sprint-05/
# For milestone
grep "milestone-name" milestones.yaml
# For previous meetings
ls meetings/*/YYYY-MM-DD*.md

Add links to metadata:

yaml

---
related_sprint: sprint-05
related_milestone: beta-release
related_issues: [123, 456]
related_docs: [docs/architecture.md]
related_meetings: [meetings/sprint-planning/2025-11-06_sprint-4-planning.md]
---

Add links in content (if appropriate):

markdown

## Context
This meeting is for [Sprint 5](../../sprints/sprint-05/sprint-plan.md) planning.

Related to [Beta Release](../../milestones.yaml#beta-release) milestone.

Follow-up from [previous retrospective](../retrospectives/2025-11-06_sprint-4-retro.md).

目标：将会议与相关项目工件关联。

步骤：

从会议内容中识别相关项：
- 迭代编号（例如：“Sprint 5”）
- 里程碑名称
- 问题编号（#123）
- 文档引用
- 之前的会议引用

检查这些项是否存在：

bash

# 检查迭代引用
ls sprints/sprint-05/
# 检查里程碑
grep "milestone-name" milestones.yaml
# 检查之前的会议
ls meetings/*/YYYY-MM-DD*.md

在元数据中添加链接：

yaml

---
related_sprint: sprint-05
related_milestone: beta-release
related_issues: [123, 456]
related_docs: [docs/architecture.md]
related_meetings: [meetings/sprint-planning/2025-11-06_sprint-4-planning.md]
---

在内容中添加链接（如果合适）：

markdown

## 上下文
本次会议是为[Sprint 5](../../sprints/sprint-05/sprint-plan.md)规划召开的。

与[Beta发布](../../milestones.yaml#beta-release)里程碑相关。

跟进[上次回顾会](../retrospectives/2025-11-06_sprint-4-retro.md)的内容。

Phase 6: Create and Save Meeting Note

阶段6：创建并保存会议笔记

Objective: Write the meeting note to the correct location.

Steps:

Determine full file path:

meetings/[meeting-type]/[filename].md
Example: meetings/sprint-planning/2025-11-13_sprint-5-planning.md

Ensure target directory exists:
bash
```
mkdir -p meetings/[meeting-type]
```
Write file using
```
Write
```
tool:
- Use complete path
- Include all generated content
- Ensure proper formatting

Verify creation:

bash

ls -la meetings/[meeting-type]/[filename].md

Example output:

✅ Created: meetings/sprint-planning/2025-11-13_sprint-5-planning.md

目标：将会议笔记写入正确的位置。

步骤：

确定完整文件路径：

meetings/[meeting-type]/[filename].md
示例：meetings/sprint-planning/2025-11-13_sprint-5-planning.md

确保目标目录存在：
bash
```
mkdir -p meetings/[meeting-type]
```
使用Write工具写入文件：
- 使用完整路径
- 包含所有生成的内容
- 确保格式正确

验证文件创建：

bash

ls -la meetings/[meeting-type]/[filename].md

示例输出：

✅ 已创建：meetings/sprint-planning/2025-11-13_sprint-5-planning.md

Phase 7: Governance Update

阶段7：治理更新

Objective: Maintain README.md indexes per governance protocol.

Steps:

Update meetings/README.md:

Read current content:

bash

Read meetings/README.md

Add new meeting to index:

markdown

## Recent Meetings

### Sprint Planning
- [2025-11-13: Sprint 5 Planning](sprint-planning/2025-11-13_sprint-5-planning.md) - Planned authentication features (Last updated: 2025-11-13)
- [2025-10-30: Sprint 4 Planning](sprint-planning/2025-10-30_sprint-4-planning.md) - ... (Last updated: 2025-10-30)

[Keep sorted by date, most recent first]

Update last modified date:

markdown

---
Last updated: 2025-11-13

Update meetings/[type]/README.md (if exists):

Add to category-specific index:

markdown

# Sprint Planning Meetings

## Meetings

- [2025-11-13: Sprint 5 Planning](2025-11-13_sprint-5-planning.md) - Description
- [Previous meetings...]

---
Last updated: 2025-11-13

Update project root README.md:

Add to Recent Activity:

markdown

## Recent Activity

- 2025-11-13: Sprint 5 Planning meeting notes added
- [Previous activities...]

Update last modified:

markdown

---
Last updated: 2025-11-13

Execute custom workflows from RULE.md:

Read

Auto Workflows > When Claude creates meeting notes

markdown

## When Claude creates meeting notes:
1. Extract all action items with @mentions
2. Update team member task lists
3. Link to related user stories if mentioned
4. Add to README.md meeting index
5. [Custom step specific to this project]

Execute each specified step.

目标：根据治理协议维护README.md索引。

步骤：

更新meetings/README.md：

读取当前内容：

bash

Read meetings/README.md

将新会议添加到索引中：

markdown

## 近期会议

### 迭代规划会
- [2025-11-13: Sprint 5规划会](sprint-planning/2025-11-13_sprint-5-planning.md) - 规划认证功能（最后更新：2025-11-13）
- [2025-10-30: Sprint 4规划会](sprint-planning/2025-10-30_sprint-4-planning.md) - ...（最后更新：2025-10-30）

[按日期排序，最新的排在前面]

更新最后修改日期：

markdown

---
最后更新：2025-11-13
---

更新meetings/[type]/README.md（如果存在）：

添加到特定类别的索引中：

markdown

# 迭代规划会

## 会议列表

- [2025-11-13: Sprint 5规划会](2025-11-13_sprint-5-planning.md) - 描述
- [之前的会议...]

---
最后更新：2025-11-13

更新项目根目录的README.md：

添加到近期活动中：

markdown

## 近期活动

- 2025-11-13：添加了Sprint 5规划会会议笔记
- [之前的活动...]

更新最后修改日期：

markdown

---
最后更新：2025-11-13
---

执行RULE.md中的自定义工作流：

读取

Auto Workflows > When Claude creates meeting notes

：

markdown

## 当Claude创建会议笔记时：
1. 提取所有带@提及的行动项
2. 更新团队成员的任务列表
3. 如果提及则链接到相关的用户故事
4. 添加到README.md会议索引
5. [针对该项目的自定义步骤]

执行每个指定的步骤。

Phase 8: Report

阶段8：报告

Objective: Confirm completion and guide next steps.

Report format:

✅ Meeting Notes Created Successfully!

📄 File: meetings/[type]/[filename].md
📅 Date: YYYY-MM-DD
👥 Attendees: [count] people
⏱️  Duration: [X] minutes

📋 Action Items: [count]
[List action items with owners]

🔗 Linked to:
- Sprint [X]
- Milestone: [name]
- Issues: #[numbers]

📚 Updated governance:
✓ meetings/README.md
✓ meetings/[type]/README.md
✓ Project README.md

💡 Next steps:
- Review action items with team
- Track action item completion
- Link to sprint/milestone if not already done

[If action items with owners exist:]
Reminder to notify:
- @[owner1] about [task]
- @[owner2] about [task]

[If custom workflows were executed:]
🤖 Executed custom workflows from RULE.md:
- [Workflow description]

目标：确认完成并指导后续步骤。

报告格式：

✅ 会议笔记创建成功！

📄 文件：meetings/[type]/[filename].md
📅 日期：YYYY-MM-DD
👥 参会人员：[数量]人
⏱️ 时长：[X]分钟

📋 行动项：[数量]项
[列出带负责人的行动项]

🔗 关联到：
- 迭代[X]
- 里程碑：[名称]
- 问题：#[编号]

📚 已更新治理内容：
✓ meetings/README.md
✓ meetings/[type]/README.md
✓ 项目README.md

💡 后续步骤：
- 与团队评审行动项
- 跟踪行动项的完成情况
- 如果尚未关联，链接到迭代/里程碑

[如果存在带负责人的行动项：]
提醒通知：
- @[负责人1] 关于[任务]
- @[负责人2] 关于[任务]

[如果执行了自定义工作流：]
🤖 已执行RULE.md中的自定义工作流：
- [工作流描述]

Special Cases

特殊情况

Case 1: Quick standup notes

情况1：快速站会笔记

If user provides brief standup update:

User: "Today's standup: Everyone on track, Bob blocked on API issue, Alice will help"

Response:

Detect it's a standup (keyword "standup")

Create minimal standup format:

markdown

---
title: Daily Standup
type: standup
date: 2025-11-13
---

# Daily Standup - 2025-11-13

## Updates
- Team on track
- Bob: Blocked on API issue
- Alice: Will assist Bob

## Action Items
- [ ] Alice: Help Bob with API issue

Save with date-based filename:
```
2025-11-13_standup.md
```
Update governance
Report: "Standup notes recorded. Alice assigned to help Bob."

如果用户提供简短的站会更新：

用户：“今日站会：所有人进度正常，Bob在API问题上受阻，Alice会帮忙”

响应：

检测到站会（关键词“standup”）

创建极简站会格式：

markdown

---
title: 每日站会
type: standup
date: 2025-11-13
---

# 每日站会 - 2025-11-13

## 更新内容
- 团队进度正常
- Bob：在API问题上受阻
- Alice：将协助Bob

## 行动项
- [ ] Alice：协助Bob解决API问题

使用基于日期的文件名保存：
```
2025-11-13_standup.md
```
更新治理内容
报告：“已记录站会笔记。已分配Alice协助Bob。”

Case 2: Retrospective with structured feedback

情况2：带结构化反馈的回顾会

For retrospectives, use special format:

markdown

undefined

对于回顾会，使用特殊格式：

markdown

undefined

Sprint [X] Retrospective

迭代[X]回顾会

What Went Well 🎉

做得好的地方 🎉

Item 1
Item 2

项1
项2

What Could Be Improved 🔧

需要改进的地方 🔧

Item 1
Item 2

项1
项2

Action Items for Next Sprint

下一个迭代的行动项

Action 1 - @owner
Action 2 - @owner

行动1 - @负责人
行动2 - @负责人

Appreciation 💙

感谢 💙

Shoutout to @person for [accomplishment]

感谢@person 完成[成就]

Metrics

指标

Velocity: [X] points
Completed: [X]/[Y] stories
Sprint goal: [Met/Partially Met/Not Met]

undefined

交付速度：[X]点
已完成：[X]/[Y]个用户故事
迭代目标：[已完成/部分完成/未完成]

undefined

Case 3: Meeting notes from transcript

情况3：基于转录内容的会议笔记

If user provides meeting transcript or long notes:

Parse content to extract:
- Speakers and what they said
- Key decisions
- Action items (look for commitments, assignments)
- Questions and answers
Structure into sections:
- Discussion (organized by topic if possible)
- Decisions (extract conclusions)
- Action Items (extract commitments)
Confirm with user: "I've structured the transcript. Here are the key points and action items I extracted. Please review..."

如果用户提供会议转录内容或长篇笔记：

解析内容以提取：
- 发言人和他们的发言内容
- 关键决策
- 行动项（查找任务、分配、承诺）
- 问答内容
组织为章节：
- 讨论内容（尽可能按主题组织）
- 决策结果（提取结论）
- 行动项（提取承诺）
请用户确认： “我已整理好转录内容。以下是我提取的要点和行动项，请审核...”

Case 4: Meeting series

情况4：系列会议

If user is creating recurring meeting notes:

Detect series (e.g., "weekly standup", "daily standup"):
- Check for existing notes with similar titles
- Note pattern in governance
Use consistent naming:
- Daily standups:
```
YYYY-MM-DD_standup.md
```
- Weekly meetings:
```
YYYY-MM-DD_weekly-sync.md
```

Link to previous:

markdown

## Previous Meeting
[Last week's sync](2025-11-06_weekly-sync.md)

## Follow-up on Previous Action Items
- [X] Item from last week - completed
- [ ] Item from last week - in progress

如果用户正在创建 recurring 会议笔记：

检测系列会议（例如：“每周同步会”、“每日站会”）：
- 检查是否存在标题类似的现有笔记
- 记录治理中的模式
使用一致的命名规则：
- 每日站会：
```
YYYY-MM-DD_standup.md
```
- 每周会议：
```
YYYY-MM-DD_weekly-sync.md
```

链接到之前的会议：

markdown

## 上次会议
[上周同步会](2025-11-06_weekly-sync.md)

## 上次行动项跟进
- [X] 上周的项 - 已完成
- [ ] 上周的项 - 进行中

Case 5: Emergency or incident meetings

情况5：紧急或事件会议

For urgent meetings about incidents:

Use incident template (if defined in RULE.md):

markdown

---
title: [Incident Title]
type: incident
severity: [high|critical]
date: YYYY-MM-DD HH:MM
---

# Incident: [Title]

## Timeline
- HH:MM - Incident detected
- HH:MM - Team notified
- HH:MM - Root cause identified
- HH:MM - Fix deployed
- HH:MM - Incident resolved

## Impact
[Description of impact]

## Root Cause
[What caused the incident]

## Resolution
[How it was fixed]

## Action Items
- [ ] Prevent recurrence: [task]
- [ ] Post-mortem: [task]

对于关于事件的紧急会议：

使用事件模板（如果在RULE.md中定义）：

markdown

---
title: [事件标题]
type: incident
severity: [高/严重]
date: YYYY-MM-DD HH:MM
---

# 事件：[标题]

## 时间线
- HH:MM - 检测到事件
- HH:MM - 通知团队
- HH:MM - 确定根本原因
- HH:MM - 部署修复方案
- HH:MM - 事件解决

## 影响
[影响描述]

## 根本原因
[事件的起因]

## 解决方案
[如何修复的]

## 行动项
- [ ] 防止复发：[任务]
- [ ] 事后总结：[任务]

Error Handling

错误处理

Error: RULE.md not found

错误：未找到RULE.md

Response:

⚠️ No RULE.md found in this directory or parent directories.

This appears to not be a ProjectMaster-initialized project.

Options:
1. Initialize project first: "Initialize a new project for [name]"
2. Create meeting note with default format (no governance)
3. Specify a different directory

What would you like to do?

If user chooses option 2, use default structured format.

响应：

⚠️ 未在当前目录或上级目录中找到RULE.md。

这似乎不是一个由ProjectMaster初始化的项目。

选项：
1. 先初始化项目：“为[名称]初始化一个新项目”
2. 使用默认格式创建会议笔记（无治理）
3. 指定其他目录

您想怎么做？

如果用户选择选项2，使用默认的结构化格式。

Error: meetings/ directory doesn't exist

错误：meetings/目录不存在

Response:

⚠️ No meetings/ directory found.

I'll create it now with proper governance structure.

Then:

bash

mkdir -p meetings/
echo "[README.md content]" > meetings/README.md

Proceed with meeting creation.

响应：

⚠️ 未找到meetings/目录。

我将立即创建该目录并配置适当的治理结构。

然后执行：

bash

mkdir -p meetings/
echo "[README.md内容]" > meetings/README.md

继续创建会议笔记。

Error: Invalid meeting type

错误：无效的会议类型

If user specifies a meeting type not in RULE.md:

Response:

⚠️ Meeting type "[type]" not recognized for this project.

Available types based on your RULE.md:
- [type1]
- [type2]
- [type3]

Would you like to:
1. Use one of the available types
2. Create as "General" meeting
3. Add "[type]" to RULE.md as a new meeting type

Which option?

如果用户指定的会议类型不在RULE.md中：

响应：

⚠️ 未识别该项目的会议类型“[type]”。

根据您的RULE.md，可用类型包括：
- [type1]
- [type2]
- [type3]

您想：
1. 使用可用类型之一
2. 创建为“通用”会议
3. 将“[type]”添加到RULE.md中作为新的会议类型

选择哪个选项？

Error: Filename conflict

错误：文件名冲突

If filename already exists:

Response:

⚠️ A meeting note already exists with this name:
meetings/[type]/[filename].md

Options:
1. Create with different name (e.g., append "-v2")
2. Update/append to existing note
3. Cancel creation

What would you like to do?

如果文件名已存在：

响应：

⚠️ 已存在同名的会议笔记：
meetings/[type]/[filename].md

选项：
1. 使用不同名称创建（例如，追加“-v2”）
2. 更新/追加到现有笔记
3. 取消创建

您想怎么做？

Integration with Other Skills

与其他Skill的集成

With manage-sprint Skill

与manage-sprint Skill集成

If meeting is sprint-related (planning, review, retrospective):

Check for current sprint:
bash
```
ls sprints/current/
```
Link meeting to sprint:
yaml
```
related_sprint: sprint-05
```

Update sprint documentation: Add reference in

sprints/sprint-05/sprint-plan.md

markdown

## Meetings
- [Planning](../../meetings/sprint-planning/2025-11-13_sprint-5-planning.md)

如果会议与迭代相关（规划、评审、回顾）：

检查当前迭代：
bash
```
ls sprints/current/
```
将会议链接到迭代：
yaml
```
related_sprint: sprint-05
```

更新迭代文档：在

sprints/sprint-05/sprint-plan.md

中添加引用：

markdown

## 会议
- [规划会](../../meetings/sprint-planning/2025-11-13_sprint-5-planning.md)

With track-milestone Skill

与track-milestone Skill集成

If meeting discusses milestone:

Extract milestone mentions from content
Link in metadata:
yaml
```
related_milestone: beta-release
```

Update milestone notes: If milestones.yaml supports notes:

yaml

notes: "Discussed in meeting: meetings/planning/2025-11-13_sprint-5-planning.md"

如果会议讨论里程碑：

从内容中提取里程碑提及
在元数据中添加链接：
yaml
```
related_milestone: beta-release
```

更新里程碑笔记：如果milestones.yaml支持笔记：

yaml

notes: “在会议中讨论：meetings/planning/2025-11-13_sprint-5-planning.md”

With AkashicRecords Skills

与AkashicRecords Skills集成

If user wants to reference knowledge base articles in meeting:

Detect article mentions (URLs, document names)
Use search-content to locate articles

Link in meeting notes:

markdown

## References
- [Architecture Decision 001](../../decisions/001-database-choice.md)
- [API Documentation](../../knowledge/api-docs.md)

如果用户想要在会议中引用知识库文章：

检测文章提及（URL、文档名称）
使用search-content定位文章

在会议笔记中添加链接：

markdown

## 参考资料
- [架构决策001](../../decisions/001-database-choice.md)
- [API文档](../../knowledge/api-docs.md)

Best Practices

最佳实践

1. Always read RULE.md first

1. 始终先读取RULE.md

Meeting format varies by team. Read RULE.md before creating to ensure compliance.

会议格式因团队而异。创建前先读取RULE.md以确保符合规范。

2. Extract action items automatically

2. 自动提取行动项

Look for tasks, assignments, and commitments. Parse them into structured format.

查找任务、分配和承诺。将它们解析为结构化格式。

3. Link generously

3. 尽可能多添加链接

Connect meetings to sprints, milestones, decisions, and other meetings. Rich linking improves navigability.

将会议与迭代、里程碑、决策和其他会议关联。丰富的链接可提高可导航性。

4. Maintain consistent naming

4. 保持命名一致

Follow RULE.md naming convention exactly. Consistency enables better searching and sorting.

严格遵循RULE.md的命名规则。一致性有助于更好地搜索和排序。

5. Update governance immediately

5. 立即更新治理内容

Don't defer README.md updates. Do them as part of meeting creation.

不要推迟更新README.md。将其作为会议创建流程的一部分。

6. Confirm action items with user

6. 与用户确认行动项

Automatic extraction may miss context. Always confirm extracted action items.

自动提取可能会遗漏上下文。始终确认提取的行动项。

7. Use appropriate granularity

7. 使用适当的粒度

Daily standups: Brief, minimal format Sprint planning: Detailed, comprehensive format Retrospectives: Structured sections (what went well, what to improve)

每日站会：简洁、极简格式迭代规划会：详细、全面的格式回顾会：结构化章节（做得好的地方、需要改进的地方）

8. Preserve formatting

8. 保留格式

If user provides formatted content, preserve structure while adding governance elements.

如果用户提供了格式化的内容，在添加治理元素的同时保留原有结构。

Examples

示例

Example 1: Sprint Planning Meeting

示例1：迭代规划会

User: I need to create notes for our sprint 5 planning meeting

Claude: I'll create sprint planning notes. Let me gather details...

Meeting title? (e.g., "Sprint 5 Planning")

User: Sprint 5 Planning

Claude: Great! Attendees?

User: Whole team - Alice (PO), Bob (SM), Carol, David, Eve, Frank (devs)

Claude: How long was the meeting?

User: About 90 minutes

Claude: Perfect! Any content to include, or should I create a template for you to fill?

User: Create template, but add that we're focusing on authentication features

Claude: Got it! Creating structured sprint planning notes...

✅ Created: meetings/sprint-planning/2025-11-13_sprint-5-planning.md

📄 Structured template with:
- Sprint goal: Authentication features
- Sections for user stories, estimates, assignments
- Action items section
- Links to Sprint 5 documentation

📚 Updated:
✓ meetings/README.md
✓ meetings/sprint-planning/README.md
✓ Project README.md
✓ sprints/sprint-05/sprint-plan.md (added planning meeting link)

You can now edit the file to add detailed notes, user stories, and estimates.

用户：我需要为我们的Sprint 5规划会创建笔记

Claude：我将创建迭代规划会笔记。让我收集详细信息...

会议标题？（例如：“Sprint 5规划会”）

用户：Sprint 5规划会

Claude：好的！参会人员有哪些？

用户：整个团队 - Alice（PO）、Bob（SM）、Carol、David、Eve、Frank（开发人员）

Claude：会议持续了多久？

用户：大约90分钟

Claude：完美！是否需要添加内容，还是我创建一个模板供您填写？

用户：创建模板，但要加上我们重点关注认证功能

Claude：收到！正在创建结构化迭代规划会笔记...

✅ 已创建：meetings/sprint-planning/2025-11-13_sprint-5-planning.md

📄 结构化模板包含：
- 迭代目标：认证功能
- 用户故事、估算、分配章节
- 行动项章节
- 链接到Sprint 5文档

📚 已更新：
✓ meetings/README.md
✓ meetings/sprint-planning/README.md
✓ 项目README.md
✓ sprints/sprint-05/sprint-plan.md（添加了规划会链接）

您现在可以编辑文件以添加详细笔记、用户故事和估算。

Example 2: Quick Daily Standup

示例2：快速每日站会

User: Today's standup: Carol finished user signup, David starting login, Eve blocked on OAuth config, Bob will help Eve

Claude: Recording daily standup...

✅ Created: meetings/daily-standups/2025-11-13_standup.md

📋 Summary:
- Carol: Completed user signup ✓
- David: Starting login feature
- Eve: Blocked on OAuth configuration
- Bob: Will assist Eve

Action Items:
- [ ] Bob: Help Eve with OAuth configuration

📚 Governance updated

💡 Reminder: Bob to assist Eve with OAuth blocker

用户：今日站会：Carol完成了用户注册功能，David开始登录功能，Eve在OAuth配置上受阻，Bob会帮忙

Claude：正在记录每日站会...

✅ 已创建：meetings/daily-standups/2025-11-13_standup.md

📋 摘要：
- Carol：已完成用户注册 ✓
- David：开始登录功能开发
- Eve：在OAuth配置上受阻
- Bob：将协助Eve

行动项：
- [ ] Bob：协助Eve解决OAuth配置问题

📚 已更新治理内容

💡 提醒：Bob需协助Eve解决OAuth阻塞问题

Example 3: Retrospective

示例3：回顾会

User: Create retro notes for sprint 4

Claude: I'll create a Sprint 4 retrospective note. Let me use the retrospective template...

What went well in Sprint 4?

User: We delivered all planned features, team collaboration was great, no major bugs

Claude: What could be improved?

User: Estimations were off, needed better testing before review

Claude: Any specific action items for next sprint?

User: Allocate more time for testing, involve QA earlier, re-calibrate story points

Claude: Creating retrospective...

✅ Created: meetings/retrospectives/2025-11-13_sprint-4-retro.md

📊 Sprint 4 Retrospective:

🎉 What Went Well:
- Delivered all planned features
- Strong team collaboration
- No major bugs

🔧 What Could Be Improved:
- Estimation accuracy
- Testing workflow timing

📋 Action Items for Sprint 5:
- [ ] Allocate dedicated testing time in sprint planning
- [ ] Involve QA from story refinement stage
- [ ] Re-calibrate story point estimates based on Sprint 4 actuals

📚 Updated governance and linked to Sprint 4 documentation

💡 These action items will be tracked in Sprint 5 planning.

用户：为Sprint 4创建回顾会笔记

Claude：我将创建Sprint 4回顾会笔记。让我使用回顾会模板...

Sprint 4中哪些地方做得好？

用户：我们交付了所有规划的功能，团队协作很棒，没有重大bug

Claude：哪些地方需要改进？

用户：估算不准确，评审前需要更好的测试

Claude：下一个迭代有具体的行动项吗？

用户：分配更多时间用于测试，更早让QA参与，重新校准故事点

Claude：正在创建回顾会笔记...

✅ 已创建：meetings/retrospectives/2025-11-13_sprint-4-retro.md

📊 Sprint 4回顾会：

🎉 做得好的地方：
- 交付了所有规划的功能
- 团队协作紧密
- 无重大bug

🔧 需要改进的地方：
- 估算准确性
- 测试工作流时机

📋 下一个迭代的行动项：
- [ ] 在迭代规划中分配专门的测试时间
- [ ] 在故事细化阶段就让QA参与
- [ ] 根据Sprint 4的实际情况重新校准故事点估算

📚 已更新治理内容并链接到Sprint 4文档

💡 这些行动项将在Sprint 5规划中被跟踪。

Notes

说明

Meeting notes are the heartbeat of project communication. Rich, structured notes enable better async collaboration.
Action item extraction is intelligent but not perfect. Always review and confirm.
Cross-referencing meetings to sprints, milestones, and decisions creates a knowledge graph that's easy to navigate.
The RULE.md-defined format ensures consistency across the team without imposing rigid templates.
This Skill adapts to your team's actual workflow - Scrum, Kanban, Waterfall, or hybrid.

Effective meeting notes transform ephemeral discussions into persistent project knowledge. This Skill makes that transformation automatic.

会议笔记是项目沟通的核心。丰富、结构化的笔记可实现更好的异步协作。
行动项提取功能很智能但并非完美。请始终审核并确认。
将会议与迭代、里程碑和决策交叉引用，可创建易于导航的知识图谱。
RULE.md定义的格式确保团队内部的一致性，同时不会强加僵化的模板。
该Skill可适应您团队的实际工作流——Scrum、Kanban、Waterfall或混合模式。

有效的会议笔记将短暂的讨论转化为持久的项目知识。该Skill可自动完成这一转化过程。