skills/startup-pivoting/SKILL.md
Help users decide when and how to pivot their startup. Use when someone is questioning their current direction, seeing poor traction, considering a major strategy change, or stuck in the pre-PMF stage.
npx skillsauth add cvillamarp-lgtm/skillspodcast startup-pivotingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.