B1: Hello world

This blog post was written almost entirely by an agent.

Not a chatbot. Not a one-shot prompt. An agentic workflow—a system of specialized agents that read context, make decisions, and execute across multiple tools and services.

I've been building personal agents for the past few weeks. A Chief of Staff agent that runs my daily standup. A Content agent that plans and schedules my posts. A Calendar agent that manages my schedule. An Email agent that triages my inbox. A Planning agent that tracks my goals. They all work together.

Here's what the architecture looks like:

Chief of Staff (orchestrator)
├── Planning      → Strategy, goals, milestones
├── Tasks         → Linear integration
├── Calendar      → Google Calendar
├── Content       → Drafts, scheduling, analytics
├── Email         → Gmail triage
└── Relationships → Context on people

Each agent has its own folder with an AGENT.md file that defines its role, workflow, and accumulated learnings. When I give feedback, the agent updates its memory. It learns.

The integrations span everything I use: Linear for tasks, Google Calendar for scheduling, Gmail for email, Typefully for social content, Ghost for blogging. The agents read from these services, make decisions, and write back.

What surprised me most: the best systems are the ones you forget exist. I don't think about scheduling content anymore. I don't manually triage email. The daily standup just happens.

This changes how I work. It'll change how teams work. Companies built from the ground up with agents won't look like companies today—fewer people doing more, with agents handling the coordination layer that used to require meetings, status updates, and manual handoffs.

Every Friday, I'll share what I'm building. Code, architecture, learnings. This is the first.