Skip to main content
skill CX Codex

defining-product-strategy — Claude Code skill: product strategy

A skill that walks you through product strategy: find the real obstacle, pick where to compete, and state how you win there.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add RefoundAI/lenny-skills --skill defining-product-strategy -a claude-code
Open on GitHub

What defining-product-strategy does

The skill runs four steps. First it helps you name the high-stakes obstacle holding the product back. Then it walks the choice cascade: where you compete and how you win in that space. Next it distills a complex direction into a simple why plus a few memorable pillars. The last step stress-tests the plan for blind spots and weak defensibility.

Inside are principles drawn from 27 guests across Lenny's Podcast and Newsletter. There is a set of questions the skill asks you, and a list of common mistakes it flags: goals mistaken for strategy, speed treated as a moat, solving one problem for everyone at once. All 50 sourced insights sit in references/guest-insights.md.

It is a text-only skill. No scripts, no external services, no metric crunching. That means it will not build a financial model or size a market for you. And if you cannot yet describe the problem your product is fighting, the work stalls at step one, because the diagnosis is the part everything else hangs on.

What it helps with

  • name the obstacle that is actually holding the product back
  • choose which market and segment you can win
  • compress a complex direction into one clear why
  • stress-test a plan for blind spots and weak defensibility
  • tell a strategy apart from a list of ambitious targets

Example prompts for the agent

  • help me define the product strategy for our service
  • walk me through the choice cascade: where we compete and how we win
  • stress-test my strategy plan for blind spots

How to install defining-product-strategy

1Skills CLI (Vercel)

npx skills add RefoundAI/lenny-skills --skill defining-product-strategy -a claude-code

2Manually: put the files in place

~/.claude/skills/defining-product-strategy/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/defining-product-strategy/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about defining-product-strategy

How do I install defining-product-strategy in Claude?

Run npx skills add RefoundAI/lenny-skills --skill defining-product-strategy -a claude-code. The skill file lands at ~/.claude/skills/defining-product-strategy/SKILL.md.

What does defining-product-strategy do?

It guides you through diagnosing the main obstacle, choosing where to compete, and stating the strategy, then checks the plan for weak spots. The principles come from Lenny's Podcast and Newsletter.

Does the skill need any extra tools?

No. It is a text skill that asks questions and works through your answers. There are no scripts or external services inside.

Source text

SKILL.md · MIT
---
name: defining-product-strategy
description: Help users move beyond ambitious goal-setting to create a rigorous diagnosis of challenges and a clear, actionable plan for winning in their specific market.
---

# Defining Product Strategy

Transform vision into a concrete plan of action by making hard choices that drive customer behavior.

Help the user with defining product strategy using insights from 27 guests and posts across Lenny's Podcast and Newsletter.

## How to Help

1. **Diagnose the crux** - Help the user identify the primary obstacle or high-stakes challenge that is currently holding the product back.
2. **Guide the choice cascade** - Walk the user through defining where they will compete and how they will uniquely win in that space.
3. **Structure the narrative** - Assist in distilling complex directions into a simple 'why' and a set of memorable strategic pillars.
4. **Stress-test the plan** - Use AI or external critiques to identify blind spots, common consensus thinking, or lack of defensibility.

## Core Principles

### Distill to a simple 'why'
Anneka Gupta: "When people say, 'I want someone that's strategic,' what they're really saying is, 'I want someone that can come up with and articulate a compelling and simple why behind the decisions and the direction of the company and product.' So that's number one. And the second piece is, 'I want someone that's going to champion and be a change agent to do things that may be hard but actually best for the long-term interest of the product or company, even though those things are not going to be easy to execute on.'"

True leadership requires the ability to take complex company directions and compress them into a single, compelling narrative that provides clear purpose for the team.

### Strategy as an integrated set of choices
Annie Pearl: "Strategy is really just an integrated set of choices that outline how you're going to win in whatever marketplace you choose. And so, a good product strategy is going to answer questions like what's your winning aspiration? But maybe more importantly, where are you going to play?"

Avoid lists of goals by defining exactly where the company will compete and the specific mechanisms it will use to win in that marketplace.

### Challenge conventional wisdom
Dharmesh Shah: "Some of the best startup advice I've heard is startups should focus on one thing and be really, really exceptionally world-class at that one thing. And one of our early zigs is we are going to do exactly the opposite of that."

Significant success often comes from making high-conviction bets that intentionally diverge from standard industry advice regarding product scope.

### Prioritize clarity over perfection
Jag Duggal: "We may not be right, but at least we are clear. Even if your strategy isn't right, you have a very clear idea of what was supposed to be happening."

Being clear about the intended path is more valuable than being certain of the outcome because it allows for faster learning when expectations and reality diverge.

### Diagnosis, policy, and action
Richard Rumelt: "Well, a strategy is a design for overcoming a high-stakes challenge. It's a mixture of policy and action designed to deal with a challenge."

A legitimate strategy defines the high-stakes challenge through a diagnosis, sets a guiding policy for dealing with it, and outlines coherent actions to take.

## Questions to Help Users

- "What is the specific, high-stakes challenge or obstacle that is holding your product back from its next level of growth?"
- "Which customer segments or market opportunities are you intentionally choosing to ignore to maintain focus?"
- "How will your product be 10x better or uniquely defensible compared to the nearest competitor?"
- "Can you summarize your strategy in a single, simple sentence that a new hire could use to make an independent trade-off?"
- "What are the foundational megatrends or shifts in technology that make this specific strategy viable right now?"
- "If you had to pick just one 'crux' problem to solve this quarter, what would it be?"

## Common Mistakes to Flag

- **Mistaking goals for strategy** - Listing ambitious performance targets without identifying the actual obstacles or explaining how to overcome them creates planning theater.
- **Relying on speed as power** - Operational excellence and 'moving fast' are necessary for survival but do not provide the structural barriers required for a durable strategy.
- **Solving for everyone at once** - Horizontal products often fail by trying to solve one problem for everyone rather than deeply capturing the workflow of a specific audience.
- **Lack of high-stakes diagnosis** - Teams often skip the hard work of diagnosing the reality of their situation, leading to strategies that address symptoms rather than root causes.

## Deep Dive

For all 50 sourced insights from 27 guests, see `references/guest-insights.md`

## Related Skills

- Product Vision
- Positioning
- Pricing Strategy
- North Star Metrics

© RefoundAI · MIT · RefoundAI/lenny-skills

Similar skills

Everything for Notes, tasks and projects →

From the same set76

defining-icp A skill that narrows your audience to one tight segment where the product wins, then checks the pick against cold outreach data. CX Codex +1 450installs naming-and-branding Walks you through naming a product and building its brand, from strategy to a scored shortlist. Useful early, before the name is locked in. CX Codex +1 449installs goal-setting-okrs Translates company vision into measurable quarterly OKRs without bloated goal lists. Grounded in 31 insights from Lenny's Podcast and Newsletter. CX Codex +1 442installs first-b2b-customers Guides founders through finding and closing their first ten paying B2B customers using network outreach, cold messaging, and design partner frameworks. CX Codex +1 443installs user-onboarding-activation Guides user onboarding design to bring signups to core product value faster. Built on insights from 15 Lenny's Podcast and Newsletter contributors. CX Codex +1 439installs roadmap-prioritization Turns a messy backlog into an ROI-based plan: RICE or DRICE scoring, portfolio balance, and a roadmap draft. Useful when feature requests pile up faster than you can rank them. CX Codex +1 419installs measuring-pmf Walks you through judging where your product sits on the product-market fit spectrum using feedback, retention and organic growth. Useful when you can't tell whether to scale yet. CX Codex +1 417installs planning-cadence A skill that sets up planning across annual, quarterly and weekly horizons. Useful when strategy exists but plans keep slipping. CX Codex +1 411installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor