How I run my week as a PM with AI
Not a side project. This is my actual workday.
The system
My workday starts with one command I built with Claude Code. I call it DayBrief. It runs every morning against my real work Slack and Gmail through the integrations my company already connected.
It sorts everything that landed overnight into four buckets: what needs me now, what needs me today, what carried over from yesterday, and what’s just worth knowing. It pulls deeper context only where a decision actually needs it. I start the day with a prioritized queue instead of an unread pile.
Two decisions
I killed the version with its own keys. v1 was a standalone app with its own API keys and personal tokens. It worked, and I killed it anyway. v2 runs on integrations my company had already approved, with no credentials living in a self-built tool. v1 taught me what the tool should do. v2 made it something an organization could live with.
I also cut half the product. It originally ran twice a day, a morning brief and an evening review. The evening review was nice to read, but the morning brief already covered what mattered, so I cut the evening run and kept one.
The same loop, elsewhere
The pattern (a prompt, a schedule, state files, an output channel) is the same one that ran the Campus Scout nightly report, and the same instincts run the Developer Docs Pipeline at work. Build the loop once, point it at different problems.