Cadence patterns, routine health, rhythm awareness, communication timing.
From chief-of-staffnpx claudepluginhub tenfourty/cc-marketplace --plugin chief-of-staffThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
This skill defines how the Chief of Staff maintains cadence, routines, and structured communication patterns.
Operating Rhythm (OR) is the cadence of communication and interactions that keep an organisation aligned and executing. Per the McChrystal framework, OR is not just about scheduling meetings — it's about ensuring strategic initiatives are pushed through effectively and everyone is aligned on goals.
The Chief of Staff designs, monitors, and optimises the OR. The AI CoS tracks it and ensures nothing falls through the cracks.
The rhythms below are defaults. Actual cadence is stored in a pinned kbx note tagged cadence and personalised during /setup.
/briefing): Calendar review, priority actions, overdue items, key signals. Day-aware: Saturday/Sunday/Monday includes week-ahead with calendar streamlining./debrief): After important meetings, extract actions and decisions. Follow-on options: tldr, follow-up email, schedule follow-up, examine what wasn't asked, run blind spots analysis./status): As needed throughout the day/todos): Quick inventory of action items from recent meetings and commitments others owe/review): Strategic synthesis, pattern analysis, coach-voice reflection. Post-review outputs: coaching session, status update for CEO, recap for direct reports, deep risk analysis./coach): Mochary Method coaching — energy audit, accountability, conscious leadership. Can run standalone or after review./blindspots): Adversarial risk analysis on a meeting, topic, or the past week/decision help): Active decision coaching with framework selection/codify): Distil universal principles from meetings on a topic/culture): Surface the tacit, unspoken organisational culture/supergoal): Define a single high-stakes focusing goalWhen: Start of the working day (configurable)
Duration: 5-10 minute read
Trigger: /briefing command
Outputs: Structured daily brief
What it checks:
When: Friday afternoon or Monday morning (configurable)
Duration: 15-30 minute interactive session
Trigger: /review command
Outputs: Weekly review document, kbx updates, adjusted priorities
What it checks:
kbx search with date ranges for meeting transcript analysiskbx note list --tag decision for the week's decisionskbx project find for initiative statusWhen: After any significant meeting
Duration: 3-5 minutes
Trigger: /debrief command
Outputs: Action items, decision log entries, task updates
What it checks:
kbx search for the most recent meeting transcriptkbx person find for attendee contextMonitor these to assess whether the OR is working:
| Indicator | Healthy | Unhealthy |
|---|---|---|
| Briefing frequency | Daily or near-daily | Skipped 3+ days |
| Review frequency | Weekly | Skipped 2+ weeks |
| Debrief frequency | After most meetings | Rarely or never |
| Task list freshness | Tasks updated within 3 days | Items stale >1 week |
| Decision log currency | Current month has entries in kbx | No decision notes in 2+ weeks |
| kbx pinned notes freshness | Updated this week | Stale >2 weeks |
If OR health degrades, surface it in the weekly review (coach voice): "Your operating rhythm has gaps this week — no debriefs captured and 3 days without a briefing. The risk is that action items from meetings are going untracked."
Recurring meeting information is stored in a pinned kbx note tagged meetings. Monitor:
(From the McChrystal playbook, Appendix 4)
The Chief of Staff should flag when the rhythm is disrupted:
In each case, note the disruption and suggest adjusted routines.
kbx and the task/calendar backends are the primary tools underpinning the operating rhythm:
| Tool | Role in OR |
|---|---|
| Calendar backend (see CoS Configuration note) | Calendar awareness for briefings and reviews |
| Task backend (see task-backend skill) | Task movement tracking, overdue detection |
| Task backend — create / close | Task lifecycle from debriefs. Include project: <Name> in description to link to kbx projects. One project per task. |
kbx context | Pinned docs provide CIRs, initiatives, rhythm, meetings |
kbx search | Transcript analysis for decisions and actions |
kbx memory add | Create new notes (decisions, people context) |
kbx note edit | Update existing notes (body, tags, pin/unpin) |
| Chat MCP | Real-time communication signals |
The two systems complement each other. The task/calendar backend handles the "what" (events and tasks). kbx handles the "who" and "why" (people, context, decisions). The CoS plugin provides the "so what" (analysis, patterns, strategic advice).