The weekly cadence

Why cadence beats enthusiasm

The ritual gets installed here: a booked weekly slot, an ownership map with at least five names on it, and a backlog with ten real entries. Every team leaves demo day energized. The teams still compounding six months later are not the most enthusiastic ones - they are the ones that installed a ritual. Capability that is not scheduled decays. The cadence is the schedule that prevents the decay.

It costs thirty minutes a week, plus ownership that is mostly ambient. That is the entire price of keeping a 12-week investment compounding instead of evaporating.

The weekly ship-and-share

The agenda, exactly as we run it with client teams:

1. Thirty minutes, same slot every week, attendance expected like any standing meeting.
2. Two people demo something small (five minutes each): a new skill, an improved prompt pattern, an automation tweak, a new agent. Rotate so everyone demos roughly monthly. The team target: at least one new or improved agent or skill ships every week.
3. One "this broke" slot: someone shows a failure and how they debugged it. Normalizing failures is what keeps people reporting them instead of quietly abandoning the tool.
4. Five minutes on the backlog: what got built last week, what is claimed next (next section).
5. Capture in five lines to the workspace repo: what shipped, what broke, what is next. The log doubles as your adoption history.

Ownership: every asset has one name on it

The cadence keeps things moving; ownership keeps things alive. The rules, all of which you already half-installed in week eleven:

• Every shared skill has an owner - reviews changes, fixes drift, prunes or improves it, and bumps the plugin version in the team marketplace when it changes. Already your week-eleven rule; now enforce it for everything new.
• Every scheduled automation has an owner who checks its run log weekly. The heartbeat habit from the foundation capstone, assigned by name.
• The infrastructure has owners: one for the workspace repo and settings, one for the skills library, one for the cadence meeting itself.
• Ownership is succession-proof: when someone leaves or changes roles, their assets are reassigned in the same week, in the meeting, out loud.

The backlog: where the next quarter comes from

Keep one file in the workspace repo: the automation backlog. Anyone adds to it the moment they catch themselves doing a chore the second time. Each entry is three lines - the chore, who feels the pain and how often, rough size (afternoon, week, or call-Anfloy). The weekly meeting picks from the top; the final lesson turns this into a roadmap.

Two outside feeds keep the backlog fresh: Anthropic's own rollout materials - the docs ship champion-kit and communications-kit pages built exactly for internal adoption programs, and Anthropic Academy courses like Claude 101 and Claude Code in Action are solid refreshers for new joiners between your cohorts. Steal from both; that is what they are for.

Do this now

Sources and further reading

• Claude Code documentation
• Agent Skills - browse the open skills ecosystem