DemoReal run · claude-sonnet-5-5 · October 2026

Using the meeting-minutes skill, write minutes for this fictional meeting. Title: Platform Weekly Sync, 2026-03-04, 30 minutes, organizer Priya, reviewer Sam. Present: Priya, Alex, Jo, Sam. Notes: we agreed to move the database upgrade to 18 March because the load test is not finished; Alex will finish the load test by 11 March; Jo will update the runbook with rollback steps by 13 March; open question: who owns the on-call handoff doc; risk: vendor patch might slip. No agenda or transcript.

Skill: meeting-minutes

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)

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.

What it does

Turns notes, a transcript or a recording summary into minutes in a fixed 12-part schema: metadata, attendance, agenda, summary, decisions (with who decided and why), action items (owner, due date, acceptance criteria), notes by agenda item, parking lot, risks and blockers, next meeting, references and a version log. Decisions and action items come first, and anything unknown is marked TBD with a note on how to find it.

How it works

The model asks up to three clarifying questions if the title, date, organizer, agenda or reviewer are missing.
It drafts the minutes in the strict schema, keeping them to about one page for a 30-minute meeting.
It lists the gaps to fill before publishing and suggests sending the draft to the organizer for a quick check.

Good for

Stand-ups, design reviews, planning and triage meetings, and teams that want minutes that convert straight into tickets.

Notes & risks

Pure instructions: no scripts, no network access, no file writes, no accounts. The skill describes publishing the final minutes to a channel and creating tickets as optional follow-up steps, but it does not do that by itself; check where the output goes before sharing. Minutes may contain names and other personal data from your discussion, and the skill says not to publish raw personal data unless authorised. Make sure you are allowed to record or share what was discussed.