Use these skills to supercharge your claude code setup | Oji Udezue | 3x CPO

Most PMs are installing coding skills into Claude Code and stopping there. This episode shows the layer above that, product judgment and business judgment running as skills inside the same repo your engineers use. Oji Udezue scaffolds two products live, watches one clear the viability gate and one get killed by it, then reviews the output the way you would review a PRD in a room full of PMs. Full Writeup: https://www.news.aakashg.com/p/oji-udezue-claude-skills Transcript: https://www.aakashg.com/product-judgment-skills-in-claude-code-with-oji-udezue/ Product Mind Skills Library: https://github.com/ojiudezue/productmind-skills Timestamps: 0:00 - Intro 1:31 - What you will learn today 2:43 - Why PMs became the bottleneck 4:46 - Scaffolding a new product live in Claude Code 8:34 - The viability gate verdict 13:43 - Ads 15:25 - Inside the scaffolding skill step by step 20:15 - Running the gate on a second idea 24:22 - Vet a Feature for existing products 27:25 - Ads 31:18 - Applying PM judgment to the output 37:02 - Standup Zero fails the gate 39:59 - Prototypes and the customer discovery plan 51:59 - The three speed problem 55:31 - Where to grab the skills 🏆 Thanks to our sponsors: 1. Ariso - Ship AI agents and features faster, with fewer regressions - https://ariso.ai/aakash 2. Bolt - Ship AI-powered products 10x faster - https://bolt.new/solutions/product-manager?utm_source=Promoted&utm_medium=email&utm_campaign=aakash-product-growth 3. Product Faculty - Get $150 off their #1 AI PM Certification with code AAKASH150 4. Customer.io - Send smarter messages using your product data - http://customer.io/productgrowth Key Takeaways: 1. Code skills are becoming commodity - GitHub is full of repos that token-max, token-minimize, and cut costs. Every one of them optimizes the same thin slice. Someone already pulled superhuman skills out of their repo because the models got good enough to make them redundant. 2. A tech company runs on three layers - Software and hardware. Product, which is customers and business model. Business, which is where resources get allocated. Almost every skill library on GitHub only touches the first one. 3. PMs are the new bottleneck - Developers with early adopter habits are speeding up fast. Product judgment and orchestration are not speeding up to match. The imbalance shows up as engineers waiting on decisions instead of waiting on code. 4. The viability gate will tell you no - LLMs almost never refuse an idea. This skill scores six dimensions including problem clarity and urgency, target user definition, competitive landscape, differentiation, technical feasibility, and revenue. Three weak scores and it recommends you stop entirely. 5. Watch a real idea get killed - Standup Zero, a Slack-to-standup digest, came back with three moderate scores, a competitive field so crowded it counted against the idea, and thin differentiation. The verdict was proceed with eyes open. Knowing that before you write code is the whole point. 6. LLM market research gets you 60 to 70 percent - Run it, then go find real sources. The failure mode is taking it as gospel. Read the differentiation map and check whether the tools it names are current or decrepit. That is your first credibility scan. 7. Scaffolding is an orchestrator skill - One master SKILL.md calls subskills for market research, the sharp problem test, architecture, testing, and CI. It fetches new skills if your project type needs them. The whole thing runs as an 11-step workflow from business problem to first commit. 8. You get a repo that organizes itself - The skill writes a CLAUDE.md tuned to that specific project, a folder structure that tells both you and Claude what goes where, a test folder, CI so every check-in gets tested, secrets in gitignore, and a bug log that catalogs failures over time. 9. Vet a Feature is the version for existing products - Most PMs are not starting brand new projects. This skill takes one feature idea, tears it apart for anti-patterns, and scores it against the opportunity cost of everything else sitting in your backlog. 10. Shared context beats forked skills - Boris Cherny's CLAUDE.md runs about six lines and points at a shared one. Centralize the skills, harmonize the artifacts with the SDLC your org already expects, and route innovation back into the middle. Ungoverned rollouts kill the compounding. 👨‍💻 Where to find Oji Udezue: LinkedIn: https://www.linkedin.com/in/ojiudezue/ Product Mind: https://www.productmind.co/ Skills Library: https://github.com/ojiudezue/productmind-skills 👨‍💻 Where to find Aakash: Twitter: https://x.com/aakashgupta LinkedIn: https://www.linkedin.com/in/aagupta/ Newsletter: https://www.news.aakashg.com/ #ProductManagement #AI 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications.

Oji UdezueguestAakash Guptahost

Aug 6, 20261h 4mWatch on YouTube ↗

EPISODE INFO

Released: August 6, 2026
Duration: 1h 4m
Channel: Aakash Gupta
Watch on YouTube: ▶ Open ↗

EPISODE DESCRIPTION

Most PMs are installing coding skills into Claude Code and stopping there. This episode shows the layer above that, product judgment and business judgment running as skills inside the same repo your engineers use. Oji Udezue scaffolds two products live, watches one clear the viability gate and one get killed by it, then reviews the output the way you would review a PRD in a room full of PMs. Full Writeup: https://www.news.aakashg.com/p/oji-udezue-claude-skills Transcript: https://www.aakashg.com/product-judgment-skills-in-claude-code-with-oji-udezue/ Product Mind Skills Library: https://github.com/ojiudezue/productmind-skills Timestamps: 0:00 - Intro 1:31 - What you will learn today 2:43 - Why PMs became the bottleneck 4:46 - Scaffolding a new product live in Claude Code 8:34 - The viability gate verdict 13:43 - Ads 15:25 - Inside the scaffolding skill step by step 20:15 - Running the gate on a second idea 24:22 - Vet a Feature for existing products 27:25 - Ads 31:18 - Applying PM judgment to the output 37:02 - Standup Zero fails the gate 39:59 - Prototypes and the customer discovery plan 51:59 - The three speed problem 55:31 - Where to grab the skills 🏆 Thanks to our sponsors:
Ariso - Ship AI agents and features faster, with fewer regressions - https://ariso.ai/aakash
Bolt - Ship AI-powered products 10x faster - https://bolt.new/solutions/product-manager?utm_source=Promoted&utm_medium=email&utm_campaign=aakash-product-growth
Product Faculty - Get $150 off their #1 AI PM Certification with code AAKASH150
Customer.io - Send smarter messages using your product data - http://customer.io/productgrowth
Key Takeaways:
1. Code skills are becoming commodity - GitHub is full of repos that token-max, token-minimize, and cut costs. Every one of them optimizes the same thin slice. Someone already pulled superhuman skills out of their repo because the models got good enough to make them redundant.
1. A tech company runs on three layers - Software and hardware. Product, which is customers and business model. Business, which is where resources get allocated. Almost every skill library on GitHub only touches the first one.
1. PMs are the new bottleneck - Developers with early adopter habits are speeding up fast. Product judgment and orchestration are not speeding up to match. The imbalance shows up as engineers waiting on decisions instead of waiting on code.
1. The viability gate will tell you no - LLMs almost never refuse an idea. This skill scores six dimensions including problem clarity and urgency, target user definition, competitive landscape, differentiation, technical feasibility, and revenue. Three weak scores and it recommends you stop entirely.
1. Watch a real idea get killed - Standup Zero, a Slack-to-standup digest, came back with three moderate scores, a competitive field so crowded it counted against the idea, and thin differentiation. The verdict was proceed with eyes open. Knowing that before you write code is the whole point.
1. LLM market research gets you 60 to 70 percent - Run it, then go find real sources. The failure mode is taking it as gospel. Read the differentiation map and check whether the tools it names are current or decrepit. That is your first credibility scan.
1. Scaffolding is an orchestrator skill - One master SKILL.md calls subskills for market research, the sharp problem test, architecture, testing, and CI. It fetches new skills if your project type needs them. The whole thing runs as an 11-step workflow from business problem to first commit.
1. You get a repo that organizes itself - The skill writes a CLAUDE.md tuned to that specific project, a folder structure that tells both you and Claude what goes where, a test folder, CI so every check-in gets tested, secrets in gitignore, and a bug log that catalogs failures over time.
1. Vet a Feature is the version for existing products - Most PMs are not starting brand new projects. This skill takes one feature idea, tears it apart for anti-patterns, and scores it against the opportunity cost of everything else sitting in your backlog.
1. Shared context beats forked skills - Boris Cherny's CLAUDE.md runs about six lines and points at a shared one. Centralize the skills, harmonize the artifacts with the SDLC your org already expects, and route innovation back into the middle. Ungoverned rollouts kill the compounding. 👨‍💻 Where to find Oji Udezue: LinkedIn: https://www.linkedin.com/in/ojiudezue/ Product Mind: https://www.productmind.co/ Skills Library: https://github.com/ojiudezue/productmind-skills 👨‍💻 Where to find Aakash: Twitter: https://x.com/aakashgupta LinkedIn: https://www.linkedin.com/in/aagupta/ Newsletter: https://www.news.aakashg.com/ #ProductManagement #AI 🧠 About Product Growth: The world's largest podcast focused solely on product + growth, with over 200K+ listeners. 🔔 Subscribe and turn on notifications.

SPEAKERS

Oji Udezue
guest
Product leader and 3x CPO (Typeform, Calendly, Parsable) and co-founder at ProductMind.
Aakash Gupta
host
Host of Product Growth with Aakash Gupta and product growth educator/interviewer.

EPISODE SUMMARY

In this episode of Aakash Gupta, featuring Oji Udezue and Aakash Gupta, Use these skills to supercharge your claude code setup | Oji Udezue | 3x CPO explores product judgment skills in Claude Code for builder PM workflows Oji Udezue argues PMs are becoming the bottleneck as engineering speed increases, and proposes “multi-skill” Claude Code workflows that compress business, product, and engineering steps into one repo.

RELATED EPISODES