scaffold-cadence

name	scaffold-cadence
description	Install one operational cadence at a time in Container/cadences/. The discipline is one-at-a-time, never bundled — past four sticky cadences you're over-instrumented. Use when the user says 'install a cadence', 'add a weekly review', 'set up the keystone review', 'scaffold a Friday review', 'add a monthly retro', or any 'install one operational ritual' request. Drafts the cadence file, names the calendar slot, defines drift signals, and asks the user to commit to a 4-week trial.
allowed-tools	Read, Write, Edit, Glob

scaffold-cadence

Install one operational cadence in Container/cadences/. Just one. Never bundle.

The discipline: install one cadence; let it run for at least 4 weeks; only then add another. Trying to install three at once is a guaranteed regression — the first one slips, then the others collapse around it.

---

When to use

• User asks to install a weekly review, monthly retro, decision-point cadence, etc.
• User has finished discover-stack and is ready for the keystone install
• User wants to add a second/third cadence after the first is sticky

When NOT to use

• For one-off planning (use a Container/week-of-*.md file instead)
• For per-engagement decisions (those go in the client repo, not in cadences)
• When the user is trying to install >1 cadence — politely insist on one at a time

---

Stance

Cadence > content. A short, durable cadence beats a beautiful one-off doc every time. The skill's job is to install something the user will actually do on the slotted day, not to design the perfect protocol.