Weekly Schedule of Meetings
A team's recurring week is an operating design, even when it grew one calendar invite at a time. This playbook gives each day a theme, places meetings against that logic, schedules input deadlines, and protects working time on the grid.
When meetings are placed only where a slot is free, the week has no stable pattern. Inputs may be written inside the meeting that needs them, and unscheduled focus time is easy to displace.
A designed week fixes the order rather than the volume. Each day carries one theme, so a person who knows it is Wednesday knows what kind of question is in play. Each recurring meeting has an input deadline on the working day before it. Focus time is a row on the grid with nothing inside it, because a block that is not written down is an intention. The point is not fewer meetings, it is a week a team can actually hold.
Focus time that is not on the grid is not scheduled.
THE DEFAULT THEMES, which the team's constraints override Monday The team's week Tuesday Business review and execution Wednesday Finance, customers, and partners Thursday Strategy, product, and growth Friday Culture, recruiting, and admin One row per meeting and one row per protected block, in time order: | Day | Time | Meeting | Duration | Owner | Attendees | Inputs due | Friday feeds Monday. The inputs Monday's team update consumes are due Friday, which is what the deadline rule produces on its own. The artifact carries no date and no week number. A cadence repeats, so nothing in it refers to a particular week.
EVERY time and duration says which it is 09:00, as supplied the user gave it, and it never changes 11:00, proposed the skill placed it, override in one word Where a change would help a supplied value, the supplied value stays and the recommendation goes beside it, labeled as a recommendation. THREE THINGS ARE NEVER PROPOSED an owner it is a person: Owner: unassigned a time zone a wrong one excludes someone from every meeting an outside-owned duration do not replace it; the team does not control it Suggested starting points are 25 and 50 minutes rather than 30 and 60. The buffer creates transition time. Adjust the duration after reviewing whether the meeting reaches its outcome.
GAPS ARE LABELED IN POSITION, never deleted, never guessed Owner: unassigned Duration needed Time needed Roster needed Reference zone needed HEDGES KEEP THEIR HEDGE, and are not replaced by a placeholder "I think 11 people" -> 11, unconfirmed "roughly 07:00" -> 07:00, approximate "somewhere in Europe" -> Europe, exact zone unconfirmed The hedge travels. A shared window computed from approximate hours is an approximate window and says so at its edges. Arithmetic on supplied figures is welcome. The artifact may sum the durations it places. It never claims hours saved or a share of the week.
THE SCORECARD, worked line by line and never shown Themes one per day, every meeting on a day that matches Placement nothing inside a focus block or unavailable hours Anchors no supplied fixed time was moved Inputs every deadline lands before the meeting it feeds Ownership no owner inferred from a job function Load a sum of durations, or not stated at all Each fail becomes a finding, then the revised week, then a verdict: holds | one pass needed | redesign Every change in the revised week traces to a finding above it. A change nobody can trace to a finding is a preference.
weekly-schedule-of-meetings/
├── SKILL.md ← the three modes + the no-artifact reply
├── meta.yaml ← version, sources, test prompts, changelog
├── LICENSE.md ← MIT
├── assets/
│ ├── audit-scorecard.md ← the criteria a week has to satisfy
│ ├── cadence-template.md ← the weekly grid and its sections
│ └── operating-calendar-template.md ← what does not run weekly
└── references/
├── scheduling-rules.md ← every derived value and convention
└── worked-example.md ← a full cadence with supplied constraints"Use the weekly-schedule-of-meetings skill to design our team's week from what we run today."