At a glance
WHAT IT’S REALLY ABOUT
How PMs use Claude Code skills to build faster, smarter
- The episode argues that “mono-skilled” roles are fading because engineering speed is rising faster than PM/product judgment, making non-engineering work the new bottleneck.
- Oji showcases a Claude Code “new project scaffolding” orchestrator skill that runs an 11-step workflow from viability gating and market research through PRD-style briefs, architecture, testing, CI/CD, and security setup.
- A live demo compares two ideas—Code Memo (AI code-auditing for vibe coders) passes the viability gate while Standup Zero (Slack standup digest) scores weak/moderate due to heavy competition and weak differentiation.
- They emphasize LLM outputs as a strong first draft that can say “no,” but warn against treating results as gospel—PMs must review artifacts for credibility and update assumptions with real sources and customer conversations.
- For org rollout, they recommend centralizing shared context (e.g., a maintained Claude.md) and harmonizing skills with company SDLC/artifact standards to avoid uncontrolled forking and inconsistent outputs.
IDEAS WORTH REMEMBERING
5 ideasSpeeding up coding without speeding up product judgment creates a bottleneck.
Oji describes developers accelerating first with AI while PM/business decision-making stays slow; the skills system aims to compress business, product, and engineering thinking into one workflow so teams can move at “engineering speed” end-to-end.
Treat LLMs as an orchestrated process, not a chat buddy.
The scaffolding skill chains structured steps—context questions, viability gate, market research, brief/PRD artifacts, architecture and quality setup—so the model follows a repeatable product-building playbook rather than generic encouragement.
A good “viability gate” must be willing to kill ideas.
They highlight that default LLM behavior is overly positive; their gate uses a scorecard (e.g., revenue potential, feasibility, differentiation, competition, target user clarity, urgency) and can recommend stopping if weak signals stack up.
Market research from LLMs is useful—if you audit it.
Oji suggests LLMs can get you ~60–70% of the way quickly, but you must sanity-check recency and relevance (e.g., outdated competitors or incorrect landscape claims) before trusting conclusions.
Artifacts matter because they make judgment reviewable.
The workflow outputs a viability doc, market research package, and a product brief; PMs then “PRD-review” these documents for internal consistency, missing personas, and whether the value proposition truly matches the problem.
WORDS WORTH SAVING
5 quotesI've been a product manager for twenty-five 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 era of mono-skilled professionals is dead.
— Unknown
People build, and then there's no customer for it. There's nobody for it.
— Oji Udezue
We are seeing people essentially collapse the separation of tasks of PM live in Notion, uh, designers live in Figma, and collapsing it into one GitHub repo with everything.
— Oji Udezue
High quality AI-generated summary created from speaker-labeled transcript.
