The Problem
Product managers drown in context switching. Calendar, Slack, email, Confluence, Jira, meeting transcripts, customer calls — each tool holds a piece of the picture, but assembling the full picture is manual labor.
AI assistants help with individual tasks, but they don’t know you. Every conversation starts from scratch. There’s no continuity, no accumulated understanding, no system.
The Approach
Build a personal operating system around Claude Code that:
- Connects all workplace tools through MCP servers (Slack, Microsoft 365, Confluence/Jira)
- Remembers across sessions through persistent memory
- Automates the draining work (documentation, status reports, meeting notes)
- Amplifies the creative work (synthesis, writing, product thinking)
What I Built
A meta-system with five layers:
MCP Servers — Slack, Microsoft 365, and Confluence/Jira servers that give Claude Code awareness of workplace context
Skills — Reusable capabilities: transcript processing, morning briefings, idea capture, todo management, decision tracking
Commands — Quick invocations: /morning, /todos, /transcript-to-notes, /session-note
Agents — Personality-driven modes: Ask Avi (5 response styles), Edge-Case Society, org lookup
Memory — Persistent context: user preferences, project state, feedback, external references
Design Principles
- Files over tools — Open systems, never locked in
- Enable without constraining — Right tools at right moments
- Automate the mindless — Documentation, status reports
- Amplify the creator — Synthesis, prototyping, validation
- Close loops — Weekly reflection, session continuity
How It Fits
This is the system that contains everything else. Every project on this site is either a component of The Product Kitchen or was built using it. The site you’re reading right now was built in a Product Kitchen session.