Skip to content
Aakash GuptaAakash Gupta

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 ↗

At a glance

WHAT IT’S REALLY ABOUT

Product judgment skills in Claude Code for builder PM workflows

  1. 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.
  2. He demos a New Project Scaffolding skill that runs an 11-step process: viability gate, market research, product brief/PRD artifacts, architecture decisions, repo structure, testing, CI/CD, and security hygiene.
  3. The viability gate is positioned as a rare LLM behavior that can explicitly recommend “don’t build this,” using structured PM frameworks rather than generic encouragement.
  4. A second demo idea (“Standup Zero”) scores weak/moderate due to shallow urgency, unclear target user, heavy competition, and weak differentiation—illustrating how the system saves time by killing ideas early.
  5. After an idea passes, the workflow shifts to product layer execution—interaction model questions, rapid UI prototypes, and a customer discovery plan that includes scripts, survey, synthesis templates, and recruiting gates.

IDEAS WORTH REMEMBERING

5 ideas

Speeding up engineering forces PMs to upgrade their “judgment throughput.”

Udezue describes developers accelerating with AI while PM discovery and decision-making lags, making PMs the constraint unless they adopt structured, repeatable LLM-assisted workflows.

Treat product, business, and code as a single workflow—not separate tools and teams.

The scaffolding approach collapses typical separation (Notion PRDs, Figma, dev repos) into one GitHub repo that contains artifacts, context, and production-ready engineering scaffolds.

A viability gate is valuable because it can say “no” early and explicitly.

The skill scores dimensions like problem clarity/urgency, target user, competition, differentiation, feasibility, and revenue potential, and will recommend stopping when weaknesses stack up—countering LLM optimism bias.

LLM market research can be 60–70% helpful, but must be audited for credibility.

They recommend a “PRD review” mindset: check whether competitors and trends are current, whether the differentiation map makes sense, and whether the brief matches what you know about the space.

A strong scaffold includes quality systems, not just starter code.

Beyond generating docs, the skill creates CLAUDE.md tailored to the project, a self-organizing folder structure, tests, CI templates, security/secret-handling guidance, and bug/learning practices—common gaps for vibe coders.

WORDS WORTH SAVING

5 quotes

The 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

People build, and then there's no customer for it. There's nobody for it. In fact, it's super puzzling right now because it feels like GitHub is the only place that people can express themselves when they have Claude Code. They just build anything, put it on GitHub, and just languish with zero stars, if that makes any sense.

Oji Udezue

The plan itself is complete and executable. Every script, the survey, the synthesis template, and the weeks time budgeted below. What is missing is the one input the skill will not let a plan proceed. A confirmed list of recruitable people with real target cohorts, um, not adjacent contacts from the founder's network.

Oji Udezue

Builder PM and end of mono-skilled rolesPMs as the new bottleneckClaude Code skill orchestrationViability gate and sharp problem testMarket research and product brief generationRepo scaffolding: CLAUDE.md, folder structure, CI/CD, securityPrototyping and customer discovery week planThree-speed problem (why/build/distribute)Enterprise rollout governance and shared contextOpen-source ProductMind skills library (Vet a Feature, Vibe Memo, etc.)

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

High quality summaries for YouTube videos. Accurate transcripts to search & find moments. Powered by ChatGPT & Claude AI.