startup-pivoting▌
refoundai/lenny-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Structured framework for evaluating startup pivots using insights from product leaders.
- ›Applies the Four Ps framework (Problem, Persona, Product, Positioning) to diagnose what needs to change, rather than pivoting blindly
- ›Emphasizes rational distance from emotional attachment: assess whether you've truly exhausted possibilities or just lost momentum
- ›Challenges founders to consider magnitude: most pivots are too small (10%) when breakthrough often requires fundamental rethinking (200%
Startup Pivoting
Help the user decide when and how to pivot their startup using frameworks and insights from 2 product leaders.
How to Help
When the user asks for help with pivoting:
- Assess the current state - Ask about their traction, how long they've been trying, and what they've learned
- Evaluate if possibilities are exhausted - Determine if they've truly tried everything or just one version of the idea
- Challenge pivot magnitude - Most founders pivot too little; help them consider if they need a 200% pivot, not 10%
- Apply the Four Ps framework - Evaluate changes across Problem, Persona, Product, and Positioning
Core Principles
Have you exhausted the possibilities?
Stewart Butterfield: "The decision is about have you exhausted the possibilities?" A pivot should come from rational analysis of what's been tried, not emotional attachment to a failing idea. Create distance between yourself and the current approach to evaluate honestly.
Most pivots are too small
Todd Jackson: "Most founders do a 10% pivot, and what they need to be doing is a 200% pivot." When stuck in pre-PMF, small adjustments rarely break through. Consider whether you need to fundamentally change your approach rather than tweak the existing one.
Use the Four Ps framework
Evaluate pivots across four dimensions: Problem (are you solving the right problem?), Persona (are you targeting the right customer?), Product (is your solution the right approach?), and Positioning (are you framing this correctly?). Often the issue is not one but a combination.
Maintain rational distance
Emotional attachment to an idea can prevent founders from seeing clearly. The best pivot decisions come from treating your company like an outside investor would evaluate it.
Questions to Help Users
- "What have you tried so far, and what did you learn from each attempt?"
- "If you were an outside investor looking at this company, what would you conclude?"
- "Is this a tweak to your current approach or a fundamental rethink?"
- "Which of the Four Ps (Problem, Persona, Product, Positioning) might be wrong?"
- "What would a 200% pivot look like compared to what you're considering?"
- "Have you truly exhausted the possibilities, or just gotten tired of trying?"
Common Mistakes to Flag
- Pivoting too small - Making 10% changes when 200% changes are needed to find PMF
- Emotional attachment - Continuing because of sunk cost rather than evidence of potential
- Pivoting too quickly - Changing direction before truly learning why the current approach isn't working
- Only changing one P - Often multiple dimensions (problem, persona, product, positioning) need to change together
- Pivoting without a thesis - Random pivots don't help; you need a specific hypothesis about what was wrong
Deep Dive
For all 2 insights from 2 guests, see references/guest-insights.md
Related Skills
- Startup Ideation
- Measuring Product-Market Fit
- Defining Product Vision
- Customer Research
How to use startup-pivoting on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add startup-pivoting
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches startup-pivoting from GitHub repository refoundai/lenny-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate startup-pivoting. Access the skill through slash commands (e.g., /startup-pivoting) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★29 reviews- ★★★★★Li Thomas· Dec 28, 2024
Keeps context tight: startup-pivoting is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Olivia Abbas· Dec 20, 2024
Solid pick for teams standardizing on skills: startup-pivoting is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Dec 4, 2024
startup-pivoting reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Fatima Kapoor· Dec 4, 2024
startup-pivoting is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakshi Patil· Nov 23, 2024
I recommend startup-pivoting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Arjun Mehta· Nov 11, 2024
We added startup-pivoting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Chaitanya Patil· Oct 14, 2024
Useful defaults in startup-pivoting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Arjun Anderson· Oct 2, 2024
startup-pivoting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Evelyn Ghosh· Sep 21, 2024
Registry listing for startup-pivoting matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Meera Srinivasan· Sep 9, 2024
Solid pick for teams standardizing on skills: startup-pivoting is focused, and the summary matches what you get after install.
showing 1-10 of 29