By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Building a Team OS with Claude Code for PM leverage
- The episode introduces a “Team OS,” a Git-backed knowledge base designed so coding agents can retrieve the right context on demand without bloating the LLM session.
- Hannah explains context-management fundamentals—context window, compaction, and “thinking room”—and shows how nested, lean CLAUDE.md doc indexes prevent unnecessary context loading.
- The team standardizes reusable “skills,” commands, and workflows so unstructured inputs (like customer calls) become consistent artifacts that Claude can synthesize reliably.
- Analytics is scaled by storing metric definitions, vetted SQL queries, and table schemas in structured folders, reducing hallucinations and enabling PMs/engineers to self-serve analysis.
- High-quality docs come from deliberate planning using Plan mode, checkpoints, verification criteria, parallel agents writing to temp files, and saving plan files to avoid rework and “context rot.”
IDEAS WORTH REMEMBERING
5 ideasTreat team context like a version-controlled product, not scattered docs.
By keeping PRDs, research, analytics references, and workflows in a repo, teams create shared, searchable context that an AI agent can use consistently across roles.
Keep the root CLAUDE.md extremely lean and push detail downward.
The root file loads every session, so it should include only high-frequency essentials (doc index, team roster/handles, key channels) while nested CLAUDE.md files act as local indexes.
Doc indexes reduce token burn and improve reasoning quality.
Nested indexes let Claude navigate directly to relevant folders, conserving context window and preserving “thinking room,” which improves reasoning compared with broad repo exploration.
Separate “summary” artifacts from “raw” artifacts to maximize fidelity.
Storing call summaries in a consistent format allows fast synthesis across many meetings, while transcripts remain available only when deeper detail is needed.
Standardized skills turn messy human input into machine-friendly structure.
Team-wide templates for things like customer call summaries create uniform outputs, enabling reliable cross-customer analysis even when many people contribute.
WORDS WORTH SAVING
5 quotesI have spent now, like, 1,500 hours in Claude, and I'm still iterating on my setup and improving it literally every single day.
— Hannah Stulberg
You don't want very much in your CLAUDE.md file. CLAUDE.mds should be very, very, very lean.
— Hannah Stulberg
The whole repository is structured around helping Claude read and use the right information at the right time.
— Hannah Stulberg
When we're rolling out a new feature, the feature is not rolled out until the repository is updated.
— Hannah Stulberg
Claude is like a really, really eager and highly talented junior employee.
— Hannah Stulberg
SPEAKERS
Hannah Stulberg
guestPM at DoorDash and former Google APM who created the viral “Claude Code for Everything” workflow and writes the Substack “In the Weeds.”
Aakash Gupta
hostHost of the Aakash Gupta podcast/newsletter who interviews product leaders and promotes offerings like bundle.aakashg.com.
High quality AI-generated summary created from speaker-labeled transcript.
