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 要求未經授權不要發布原始個人資料。請確認你有權記錄並分享會議內容。