Platform Weekly Sync: Meeting Minutes
Source material: ad-hoc notes (no agenda, transcript or recording), so some details may be missing.
1. Metadata
- Title: Platform Weekly Sync
- Date: 2026-03-04
- Start Time (UTC): TBD (ask Priya)
- Duration: 30 minutes
- Organizer: Priya
- Location / Virtual Link: Unknown
- Minutes Author: Agent (Claude)
- Reviewer: Sam
- Distribution List: TBD. Suggested: Priya, Alex, Jo, Sam
2. Attendance
- Present: Priya (organizer), Alex, Jo, Sam (reviewer). Roles are not recorded.
- Regrets / Absent: None recorded
- Notetaker / Recorder: Agent
3. Agenda
No agenda was provided. Topics below are inferred from the notes:
- Database upgrade schedule
- Load test and runbook readiness
- On-call handoff doc ownership
- Risks
4. Summary
The team moved the database upgrade to 2026-03-18 because the load test is not finished. Alex and Jo took actions to finish the load test and add rollback steps to the runbook. Ownership of the on-call handoff doc is still open.
5. Decisions Made
- Decision 1: Move the database upgrade to 2026-03-18.
- Who decided / approved: Meeting attendees (specific approver not recorded)
- Rationale: The load test is not finished.
- Effective date: 2026-03-18
6. Action Items
- [A1] Finish the load test
- Owner: Alex
- Due: 2026-03-11
- Acceptance Criteria: Load test completed. Result criteria are TBD.
- Linked artifacts: None
- [A2] Update the runbook with rollback steps
- Owner: Jo
- Due: 2026-03-13
- Acceptance Criteria: Runbook includes rollback steps for the database upgrade.
- Linked artifacts: None
- [A3] Confirm an owner for the on-call handoff doc
- Owner: TBD (Priya to assign, suggested)
- Due: TBD
- Acceptance Criteria: A named owner is recorded.
A3 comes from the open question and was not assigned in the meeting.
7. Notes by Agenda Item
- Database upgrade schedule
- Key points:
- The upgrade moves to 2026-03-18 because the load test is incomplete.
- Alex will finish the load test by 2026-03-11.
- Jo will add rollback steps to the runbook by 2026-03-13.
- Open issues:
- Q1: Who owns the on-call handoff doc? (unassigned)
- Key points:
8. Parking Lot / Unresolved Items
- Item: Owner of the on-call handoff doc
- Why parked / next step: No owner was identified.
- Suggested owner / forum: Priya, or the next Platform Weekly Sync
9. Risks / Blockers
- Risk 1: The vendor patch might slip. Impact on the 2026-03-18 upgrade is not discussed (TBD). Mitigation owner: TBD.
10. Next Meeting / Follow-up
- Proposed date: TBD, presumably the next weekly sync (about 2026-03-11)
- Objectives: Confirm the load test result, check runbook progress, assign the on-call handoff doc owner, and review the vendor patch status.
11. Attachments / References
- Agenda: None
- Slides: None
- Transcript / Recording: None
- Related tickets: None
12. Version & Change Log
- Version: 1.0 (draft, pending review by Sam)
- Last updated: 2026-10-05, time TBD
- Changes: Initial draft from ad-hoc notes
Gaps to fill before publishing: start time, location, roles, distribution list, owner and due date for A3, and a mitigation owner for the vendor patch risk.
Real run in an isolated folder with only this skill installed. Only the Skill and Read tools were enabled, so nothing was fetched from the web and no file was written. The example is fictional. The meeting notes are invented and no agenda or transcript was given, so the model marked the source as ad-hoc notes.
它做什么
把笔记、转写稿或录音摘要整理成固定的 12 部分结构:元信息、出席情况、议程、摘要、决议(含谁做的决定及理由)、待办事项(负责人、截止日期、验收标准)、按议程的记录、待定事项、风险与阻碍、下次会议、参考资料和版本记录。决议和待办放在最前面,未知信息一律标为 TBD 并说明如何补全。
工作方式
- 如果缺少标题、日期、组织者、议程或审阅人,模型最多会先问三个澄清问题。
- 按严格结构起草纪要,30 分钟会议的篇幅控制在大约一页。
- 列出发布前需要补齐的缺口,并建议先发给组织者快速核对。
适合什么场景
站会、设计评审、规划会和问题分诊会,以及希望纪要能直接转成工单的团队。
纯指令文件:没有脚本,不联网、不写文件、不需要账号。Skill 里把“把最终纪要发布到某个频道”和“创建工单”写成可选的后续步骤,但它自己不会去做;分享之前请先确认输出会去哪里。纪要可能包含讨论中出现的姓名等个人信息,Skill 要求未经授权不要发布原始个人信息。请确保你有权记录和分享会上的内容。