ritual-calendar
Skill0 starsChanged 19 days agoMITView on GitHub
Design or audit a product team's operating rhythm — the recurring reviews, planning sessions, retros, readouts, and syncs — so each meeting has one clear purpose, the right people, and an output, with no gaps or overlap. Use when someone asks for a team operating cadence, meeting rhythm, ritual calendar, wants to cut meetings, set up a new team's rhythm, or figure out which meetings are actually needed.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- beta-program-managerSkill
- cross-team-dependency-mapSkill
- customer-advisory-board-prepSkill
- data-request-routerSkill
- decision-logSkill
- deprecation-planSkill
- duplicate-request-mergingSkill
- experiment-logSkill
- feature-flag-trackingSkill
- feedback-taggingSkill
- information-debt-auditSkill
- internal-enablement-briefSkill
- kpi-health-checkSkill
- launch-readiness-checklistSkill
- meeting-to-action-converterSkill
- new-pm-onboarding-packSkill
- pricing-packaging-change-logSkill
- process-documentationSkill
- product-metrics-definitionsSkill
- product-ops-contextSkill
- quarterly-planning-prepSkill
- raci-builderSkill
- release-notes-draftingSkill
- request-intake-triageSkill
- retro-facilitationSkill
- roadmap-hygieneSkill
- sprint-review-summarySkill
- support-escalation-patternsSkill
- tool-stack-auditSkill
- vendor-evaluation-scorecardSkill
- voice-of-customer-digestSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Every recurring meeting should earn its slot by producing something: a decision, an update people act on, or a fix.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Ritual calendar
Every recurring meeting should earn its slot by producing something: a decision, an update people act on, or a fix. A ritual calendar lays the whole rhythm out at once, so gaps and duplicates show up.
Before you start
If .agents/product-ops-context.md exists (or .claude/product-ops-context.md), read it first. Use the team, owners, tools, meetings, and metric definitions it already has, and only ask for what's missing or specific to this task. If it doesn't exist, go ahead with what you're given, and suggest running product-ops-context once so the next skill doesn't have to ask.
Step 1: List what exists (for an audit)
For each recurring meeting:
| Meeting | Cadence | Length | Attendees | Purpose (as stated) | Output | Owner | Could it be async? |
"Output" is what exists after the meeting that didn't before: a decision log entry, an updated tracker, a recap with action items. If there's no output, write "None." That's a finding.
Step 2: Check coverage
A product team typically needs a moment for each of these. Check which are covered, by which meeting, and which are missing:
| Need | Typical cadence | Typical output |
| Plan the work | Quarterly, with a mid-quarter check | Plan, priorities |
| Decide what's next | Every sprint or cycle | Committed scope |
| See what shipped | Every sprint or cycle | Sprint summary |
| Check product health | Weekly or every two weeks | KPI health check |
| Hear from customers | Weekly or monthly | VoC digest |
| Review launches | Before each launch | Go / no-go readout |
| Improve how we work | After launches and each quarter | Retro changes |
| Share with the wider company | Monthly or quarterly | Readout or update |
Step 3: Find the problems
- No purpose or no output
- Overlap: two meetings cover the same need with the same people
- Wrong cadence: too often for how fast the thing changes, or too rare to catch problems
- Wrong people: decision meetings without the decider; update meetings with people who only need the recap
- Should be async: pure status updates that a written post would cover
- Missing: a need from Step 2 with no meeting or written ritual
Step 4: Recommend the rhythm
# Team rhythm — [Team] — [Date]
## Weekly
| Ritual | Day | Length | Who | Purpose | Output | Owner |
## Every sprint / cycle
[Same table]
## Monthly
[Same table]
## Quarterly
[Same table]
## Changes from today
- **Cut:** [meeting] — [why; what replaces it]
- **Merge:** [A] + [B] → [new]
- **Move to async:** [meeting] → [written format]
- **Add:** [ritual] — [the gap it fills]
## Total time per person per week
- Before: [hours] · After: [hours]Compute time totals with real arithmetic. Recommend changes; the team decides. Never create, move, or cancel calendar events yourself.
Related skills
- meeting-to-action-converter — make every meeting end with owned actions
- raci-builder — decide who belongs in each meeting
- quarterly-planning-prep — place planning in the rhythm
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

