My chief of staff, Claude Code

Original post: https://x.com/jimprosser/status/2029699731539255640

Key ideas

• Jim describes building a personal “chief of staff” workflow in ~36 hours using Claude Code, despite non-engineer background.
• Two overnight automations:
  • Calendar + route-time planning (Google Calendar + Maps)
  • Inbox triage into actionable tasks (with dedupe in task manager)
• Morning “AM Sweep” classifies tasks into 4 buckets:
  • Green: AI can fully complete
  • Yellow: AI can prep ~80%
  • Red: requires human judgment/presence
  • Gray: not actionable today
• Uses multiple parallel subagents for drafting emails, updating notes/knowledge base, scheduling, and research.
• Follow-up “Time Block” flow converts tasks into a realistic day plan with location-aware batching and constraints.

Design principles highlighted

• Focus on systems design and handoff boundaries, not coding syntax.
• Build layered components where each stage feeds clean context/metadata to the next.
• Keep strict human control over high-stakes actions:
  • AI drafts, human sends
  • AI does prep, human decides when ambiguous
• Practical rubric: dispatch / prep / yours / skip.

Claimed impact

• Saves roughly 30–45 minutes each weekday morning.
• Reduces cognitive load by starting in decision mode, not inbox/ops assembly mode.
• Claimed incremental cost is low versus hiring part-time ops support.

Why this is interesting

This is a strong example of agentic workflow design as an operations layer (not just chat prompting): bounded autonomy, parallel specialists, and explicit human-in-the-loop controls.