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
Product judgment skills inside Claude Code to build better, faster
- Oji argues that as engineers accelerate with AI, PMs become the new bottleneck unless they also speed up product judgment and orchestration using reusable LLM “skills.”
- He demos a “New Project Scaffolding” orchestrator skill that runs an 11-step workflow: viability gating, market research, product brief creation, repo setup, testing, CI/CD, security hygiene, and a tailored CLAUDE.md.
- The viability gate is positioned as a rare mechanism that can credibly say “no” to weak ideas using explicit PM frameworks, not just agreeable chat behavior, and it is tested on two ideas with different outcomes.
- Oji emphasizes that LLM outputs are drafts, not truth—PMs must review artifacts (market research, PRD/brief) for credibility, missing personas, and strategic fit before proceeding.
- He extends the workflow beyond ideation into prototypes and customer discovery plans, and closes with guidance for rolling these skills out in teams via shared context and centrally governed CLAUDE.md/skill libraries.
IDEAS WORTH REMEMBERING
5 ideasAI makes PM judgment the limiting factor unless it’s systematized.
Oji observes engineers speed up rapidly with AI, while PM workflows (framing, prioritization, validation) often stay manual; codifying judgment into repeatable “skills” helps PMs operate at engineering speed.
Treat product building as a three-layer stack: business, product, and code.
He argues most AI tooling over-focuses on coding efficiency, but successful products require viability (business), discovery and UX (product), and quality delivery (code) working together in one flow.
A viability gate that can say “no” is a practical antidote to LLM agreeableness.
The scaffolding skill uses explicit eval dimensions (e.g., problem clarity, target user, competition, differentiation, feasibility, revenue) and recommends stopping when multiple dimensions are weak—something generic chat rarely does.
Scaffolding is not just boilerplate—it’s a handoff and quality system for non-engineers.
Beyond docs, the workflow creates a structured repo, a tailored CLAUDE.md, tests, CI templates, and security safeguards (e.g., secret hygiene), reducing the common “vibe-coded but unshippable” gap.
Market research from LLMs is useful only with credibility checks and follow-up validation.
Oji recommends using LLM research for 60–70% of initial coverage, then reviewing for staleness, missing competitors, and internal consistency before trusting conclusions or investing further.
WORDS WORTH SAVING
5 quotesThe era of mono-skilled professionals is dead, so I'm going to demonstrate the future of product builders
— Oji Udezue
I've been a product manager for 25 years, and I've never really felt that coding was worth my time until now.
— Oji Udezue
LLMs very rarely tell you no, and this skill will tell you absolutely no, don't do this.
— Oji Udezue
The danger in, in this kind of workflow is that you take it as gospel, right? You really do need to look through all the output, make sure that it makes sense for you.
— Oji Udezue
There's something we call the three-speed problem, which is for the past forty, fifty years, whatever you wanna call it, the longest pole has always been, uh, development.
— Oji Udezue
SPEAKERS
Oji Udezue
guestProduct leader and 3× Chief Product Officer (Typeform, Calendly, Parsable) with 25 years of product management experience.
Aakash Gupta
hostHost of Product Growth with Aakash Gupta, interviewing product leaders and discussing product growth and AI workflows.
High quality AI-generated summary created from speaker-labeled transcript.
