Structured framework for evaluating startup pivots using insights from product leaders.
Works with
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%
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstartup-pivotingExecute the skills CLI command in your project's root directory to begin installation:
Fetches startup-pivoting from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate startup-pivoting. Access via /startup-pivoting in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user decide when and how to pivot their startup using frameworks and insights from 2 product leaders.
When the user asks for help with pivoting:
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.
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.
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.
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.
For all 2 insights from 2 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: startup-pivoting is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: startup-pivoting is focused, and the summary matches what you get after install.
startup-pivoting reduced setup friction for our internal harness; good balance of opinion and flexibility.
startup-pivoting is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend startup-pivoting for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added startup-pivoting from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in startup-pivoting — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
startup-pivoting fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for startup-pivoting matched our evaluation — installs cleanly and behaves as described in the markdown.
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