strategy-advisor
Skill16 starsChanged 10 months agoMITView on GitHub
Helps with product and business strategy using proven frameworks. Use when: defining product direction, building strategy documents, diagnosing strategy vs execution problems, prioritizing strategically, or assessing competitive position. Includes: Product Strategy Stack, DHM, Seven Powers, Execution vs Strategy Diagnosis frameworks. Sources: Ravi Mehta, Gibson Biddle, Hamilton Helmer, Shreyas Doshi, Ami Vora.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Tgoldi/claude-skillstheir own version, first seen Oct 13, 2026
- Karanjot786/TermUItheir own version, first seen Oct 9, 2026
- nandanosql/all_in_one_pm_skillstheir own version, first seen Feb 28, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Karanjot786/TermUI★ 238same name
- nandanosql/all_in_one_pm_skills★ 1same name
- Tgoldi/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- decision-makerSkill
- goal-setterSkill
- growth-advisorSkill
- gtm-advisorSkill
- hiring-guideSkill
- leadership-coachSkill
- pm-coachSkill
- sop-librarySkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 15 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 40
Key Insight: If a PM can't decide between option A and B, the root cause is almost always a gap in understanding strategy, not a gap in …
- Distinctive: line 52
Must be rigorous, not aspirational
- Distinctive: line 99
Not just "nice to have"
- Distinctive: line 158
Test: Do we get cheaper as we grow?
- Distinctive: line 163
Test: Does each user make it better for others?
- Distinctive: line 168
Test: Would copying us hurt their existing business?
- Distinctive: line 173
Test: How painful is it to leave us?
- Distinctive: line 178
Test: Can we charge more for same features?
- Distinctive: line 183
Test: Do we have something others can't get?
- Distinctive: line 188
Test: Are our processes better AND hard to copy?
- Distinctive: line 223
When something isn't working, ask: "If we executed this perfectly, would it work?"
- Distinctive: line 266
Not gathering evidence before diagnosing
- Distinctive: line 282
Ask: "If we execute perfectly on this strategy, could we succeed?"
- Distinctive: line 301
Key: If everything is P0, nothing is.
- Distinctive: line 337
Recommend debugging: when appropriate
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Strategy Advisor Skill
Help users develop, refine, and execute product and business strategy.
When This Skill Activates
- "Help me with product strategy"
- "How do I prioritize?"
- "I can't decide between A and B"
- "Is this a strategy or execution problem?"
- "What's our competitive moat?"
- "How do I write a strategy doc?"
- "We're not hitting our goals"
Framework Selection Guide
| Situation | Use This Framework |
| Building product strategy | Product Strategy Stack |
| Consumer product strategy | DHM Framework |
| Assessing competitive position | Seven Powers |
| Diagnosing why things aren't working | Execution vs Strategy |
| Balancing strategy vs execution | Execution Over Strategy |
Framework 1: Product Strategy Stack
Source: Ravi Mehta - Lenny's Podcast Key Insight: If a PM can't decide between option A and B, the root cause is almost always a gap in understanding strategy, not a gap in prioritization skill.
The Five Layers (Top to Bottom)
Layer 1: Company Mission
- The change the company wants to bring to the world
- Qualitative and aspirational
- Example: Tinder: "Make single life more fun"
Layer 2: Company Strategy
- The logical plan to achieve the mission
- Includes: target market, value prop, business model
- Must be rigorous, not aspirational
Layer 3: Product Strategy
- Connective tissue between company strategy and product work
- Defines what the product will be
- Must include wireframes (not just words)
Layer 4: Product Roadmap
- Sequence of work to fulfill strategy
- Time-bound initiatives
- Flows FROM strategy
Layer 5: Product Goals
- Measurable outcomes
- Come AFTER roadmap (contrarian view)
- Measure strategy progress
Key Insight: Wireframes Required
"Strategy docs aren't complete without wireframes. When you talk about strategy in words alone, everyone takes away a different interpretation."
Example: Mobile apps have 4-5 nav items. What are they? Words alone → different interpretations.
Debugging Process (Bottom-Up)
| If... | Check... |
| Goals not being met | Is roadmap aligned? |
| Roadmap isn't working | Is product strategy clear? |
| Product strategy unclear | Do we understand company strategy? |
| Company strategy unclear | Is mission well-defined? |
Pitfalls to Avoid
- Starting with goals (they should come last)
- Strategy in words only (needs visuals)
- Conflating the layers
- Skipping product strategy layer
Framework 2: DHM Framework (Consumer Products)
Source: Gibson Biddle - Lenny's Podcast Key Insight: Great product strategy creates customer delight in hard-to-copy, margin-enhancing ways.
The Three Tests
D - Delight Does this meaningfully improve the customer experience?
- Not just "nice to have"
- Creates emotional response
- Drives word of mouth
H - Hard to Copy Can competitors easily replicate this? Hard-to-copy advantages:
- Brand
- Network effects
- Unique technology
- Economies of scale
- Switching costs
M - Margin-Enhancing Does this improve unit economics over time?
- Reduces costs
- Increases willingness to pay
- Improves retention
- Enables pricing power
Applying DHM
Step 1: Generate Strategy Ideas List potential strategic moves
Step 2: Score Each on D, H, M
| Strategy | Delight | Hard to Copy | Margin |
| Idea A | High | Low | Medium |
| Idea B | Medium | High | High |
Step 3: Prioritize DHM Winners Best strategies score high on all three. Watch out for:
- High D, Low H = Easily copied
- High H, Low D = Doesn't matter
- High M, Low D = Race to bottom
Netflix Examples
- Personalization: High D (finds shows for you), High H (data + algorithms), High M (better retention)
- Original content: High D (exclusive shows), High H (can't copy), Medium M (expensive but drives subs)
Pitfalls to Avoid
- Optimizing only for Delight (copycats catch up)
- Building Hard to Copy that doesn't Delight
- Ignoring Margin implications
Framework 3: Seven Powers (Competitive Moats)
Source: Hamilton Helmer - Lenny's Podcast Key Insight: Strategy is a route to continuing Power in significant markets.
The Seven Powers
1. Scale Economies Unit costs decline as volume increases.
- Example: Netflix content cost per subscriber
- Test: Do we get cheaper as we grow?
2. Network Effects Product improves as more people use it.
- Example: LinkedIn's value grows with users
- Test: Does each user make it better for others?
3. Counter-Positioning New business model incumbent can't adopt.
- Example: Netflix streaming vs Blockbuster stores
- Test: Would copying us hurt their existing business?
4. Switching Costs Cost to switch to competitor is high.
- Example: Salesforce data + workflow lock-in
- Test: How painful is it to leave us?
5. Branding Higher perceived value enabling price premium.
- Example: Apple's brand commands premium
- Test: Can we charge more for same features?
6. Cornered Resource Exclusive access to valuable asset.
- Example: Exclusive content deals
- Test: Do we have something others can't get?
7. Process Power Superior processes embedded in organization.
- Example: Toyota Production System
- Test: Are our processes better AND hard to copy?
Power Assessment
Step 1: Identify Potential Powers Which powers could apply to your business?
Step 2: Assess Current Strength
| Power | Have It? | Strength (1-5) |
| Scale Economies | Yes/No | |
| Network Effects | Yes/No | |
| Counter-Positioning | Yes/No | |
| Switching Costs | Yes/No | |
| Branding | Yes/No | |
| Cornered Resource | Yes/No | |
| Process Power | Yes/No |
Step 3: Identify Power-Building Opportunities What actions would strengthen or create powers?
Pitfalls to Avoid
- Claiming powers you don't have
- Confusing competitive advantage with power
- Ignoring market size (power in small market = limited value)
- Building moat without product-market fit first
Framework 4: Execution vs Strategy Diagnosis
Source: Shreyas Doshi - Lenny's Podcast Key Insight: Most problems blamed on strategy are actually execution problems, and vice versa.
The Diagnostic Question
When something isn't working, ask: "If we executed this perfectly, would it work?"
- Yes → Execution problem (fix how you're doing it)
- No → Strategy problem (fix what you're doing)
Common Misdiagnosis
Strategy blamed, Execution at fault:
- "Our positioning is wrong" → Actually: messaging is confusing
- "Wrong market" → Actually: wrong go-to-market motion
- "Product doesn't fit" → Actually: onboarding is broken
Execution blamed, Strategy at fault:
- "Team isn't executing" → Actually: strategy is unclear
- "We need better PMs" → Actually: priorities are wrong
- "Engineering is slow" → Actually: building wrong things
Diagnosis Process
Step 1: Describe the Problem What specific outcome isn't being achieved?
Step 2: Apply the Test "If a team of A+ executors took this strategy, would it work?"
Step 3: Look for Evidence
| Evidence Type | Points To |
| Competitors winning with similar strategy | Execution |
| No one winning in this space | Strategy |
| Team confused about priorities | Strategy |
| Team aligned but slow | Execution |
| Metrics improving slowly | Execution |
| Metrics not moving at all | Strategy |
Step 4: Address Root Cause
- Execution fix: Better processes, skills, resources
- Strategy fix: Revisit positioning, market, approach
Pitfalls to Avoid
- Defaulting to strategy change (easier than hard execution work)
- Defaulting to execution blame (avoids strategic questions)
- Not gathering evidence before diagnosing
- Changing both at once (can't learn which was wrong)
Framework 5: Execution Over Strategy (80/20)
Source: Ami Vora - Lenny's Podcast Key Insight: For most products, success is about 20% strategy and 80% execution.
The Reality
- Most product advice focuses on strategy
- Execution is where products succeed or fail
- Great strategy with poor execution loses to good strategy with great execution
"Good Enough" Strategy Test
Ask: "If we execute perfectly on this strategy, could we succeed?"
- Yes → Execute
- No → Refine strategy (but set a deadline)
Ruthless Prioritization Principles
- One thing at a time - Focus team energy
- Finish before starting - Complete current work
- Sequence, don't parallel - Fewer balls in air
- Kill zombies - End projects going nowhere
- Protect the team - Shield from distractions
The Priority Stack
| Level | What Belongs |
| P0 | Must do this quarter to succeed (2-3 things) |
| P1 | Important but can wait |
| P2 | Nice to have |
| P3 | Probably never |
Key: If everything is P0, nothing is.
Ship-Learn Cycle
- Ship smallest valuable increment
- Measure impact immediately
- Learn from results
- Adjust execution (rarely strategy)
- Ship next increment
When to Actually Change Strategy
- Fundamental assumption proven wrong
- Market shifted dramatically
- Multiple execution attempts failed
- New information changes everything
Pitfalls to Avoid
- Over-strategizing (waiting for perfect plan)
- Under-prioritizing (everything is P0)
- Mistaking motion for execution
- Abandoning strategy too early
- Cutting quality for speed
How to Apply This Skill
- Identify the strategic question
- Building strategy → Product Strategy Stack + DHM
- Assessing competition → Seven Powers
- Something not working → Execution vs Strategy
- Prioritization → Execution Over Strategy
- Walk through the selected framework systematically
- Push for specifics (strategy without specifics = useless)
- Recommend debugging when appropriate
Related Skills
/decision-maker- For specific strategic decisions/goal-setter- For goal-setting tied to strategy/growth-advisor- For growth strategy specifically
Full SOPs (Deep Dives)
Product Strategy
- Product Strategy Stack
- DHM Framework
- Seven Powers
- Execution vs Strategy
- Execution Over Strategy
- Differentiation vs Table Stakes
- Ship to Learn
- Swinging the Pendulum
AI Strategy
- AI Eval-Driven Development
- AI Platform Strategy
- AI Product Strategy Assessment
- AI Product Differentiation
- Consumer AI Metrics
- Product Team Scaling AI Era
- AI-First Product Transformation
Startup Strategy
- Startup Idea Validation
- Founder-Market Fit
- Avoiding Tarpit Ideas
- Fall in Love with Problem
- PMF Iteration Journey
- Crisis Management
Pivot & Positioning
- Pivot Decision Framework
- Bottom-Up Enterprise
- Utility Curve Investment
- Customer Value First
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

