kasey's Claude Code chief of staff
kasey (@kaseyklimes) · Catalog date October 16, 2026
kasey uses Claude Code routines as a solo founder. A daily chief-of-staff routine reads transcripts, calendar, email, Slack, and GitHub, updates work and personal action-item sheets, books the day's blocks, and emails a briefing. The post calls it one of a dozen daily routines.
Evidence. Sourced, incomplete
A public source is linked. Some results, prompts, or operating details are still unknown. This catalog has not re-run the crew.
- Goal
- Keep a solo founder's work and personal action items moving
- Use
- Coordination
- Platforms
- Claude Code
- Crew size
- Multiple agents, count not stated
- Difficulty
- Not stated
Roles
The post says the chief-of-staff routine is one of a dozen routines running daily. It also names routines for CRM, investor relations, and a founder coach. It does not list the rest, so this entry does not invent them.
Constraints shared by every role
To be added.
Chief of staff
Owns. The daily routine that reviews inputs, updates the action-item sheets, books calendar blocks, and emails a briefing.
Uses the shared constraints above.
Research subagent
Owns. Writes a cheat sheet on how to accomplish complex action items, included in the morning briefing.
Uses the shared constraints above.
CRM
Owns. Named as a routine that manages the CRM. The post does not describe the steps.
Uses the shared constraints above.
Investor relations
Owns. Named as a routine. The post does not describe the steps.
Uses the shared constraints above.
Founder coach
Owns. Named as a routine. The post does not describe the steps.
Uses the shared constraints above.
Routines
Chief of staff
Daily
Review Granola transcripts, calendar events, email, Slack, and GitHub. Update a work sheet and a personal sheet with action items, due dates, time estimates, locations, and urgency and importance scores relative to strategy docs the routine can access. Check off and archive items the data shows are done.
Morning calendar and briefing
Every morning
Use Fable to fill open calendar time with action items that have to happen that day, use the Google Maps API to order items that have locations so transit time is shorter, and email a briefing. A research subagent adds a cheat sheet for complex items.
Guardrails
- To be added.
Handoffs
The chief-of-staff routine emails the author a daily briefing. The research subagent contributes a cheat sheet for complex items. The author says other agents can be pointed at the action-item sheets. Handoffs among the CRM, investor-relations, and founder-coach routines are not described.
- Chief of staff
- Research subagent
- CRM
- Investor relations
- Founder coach
Human operator
The chief-of-staff routine emails the author a daily briefing. The research subagent contributes a cheat sheet for complex items. The author says other agents can be pointed at the action-item sheets. Handoffs among the CRM, investor-relations, and founder-coach routines are not described.
Results
- What worked
- The author says items get checked off and archived when the data shows they are done, and writes "I rarely have to check anything off."
- What broke
- To be added.
- Lessons
- To be added.
Prompts
To be added.
Source
kasey, @kaseyklimes, August 14, 2026
https://x.com/kaseyklimes/status/2088283385323995483
Notes
The catalog date is the day this entry was drafted. The source post is dated August 14, 2026.
The post names Granola, calendar events, email, Slack, GitHub, Google Sheets, Fable, and the Google Maps API. It says "emails," not a specific email product. It does not state guardrails, a prompt, what broke, or what the other routines do beyond the names above. The author also mentions planning a wedding. That context is not given as a separate routine.
Difficulty is not stated.