Sign up
← all tools

cc-skill:pivot-or-kill-framework

Claude Code skill · anthropic · active

0
last 30 days
0 calls
0 of 30 days active
explain like I am new to this
what it does

This skill walks you through a structured decision about whether to shut down or redirect a struggling feature, product, or initiative. It gathers your current data, checks specific signals like growth rate and user engagement, and gives you a clear kill, pivot, or keep recommendation with the reasoning behind it.

who it is for

Founders and product leaders who are stuck deciding whether to end something that's not working or try a different approach.

when it fires

When you ask questions like 'should I kill this product', 'is this feature worth keeping', 'should we shut down this channel', or 'should we pivot this'.

say something like
  • "Should I kill this feature? It's been live 12 weeks with almost no usage."
  • "Is it time to sunset our mobile app or pivot it to something else?"
  • "We're losing money on this channel. Should we shut it down or try a different angle?"
what you might get back
Pivot or Kill Decision: Mobile App. Original hypothesis: Users want offline access. What's actually happening: 2% weekly active users, but the 5 engaged users all use it for note-taking, not offline reading. Kill signals: None checked. Pivot signal: One feature is used heavily, the rest aren't. Decision: PIVOT. Reasoning: The note-taking use case shows real engagement. Rebuild the app as a focused note-taking tool and kill the offline reading features.
how to know it worked

You'll know it worked when you get back a clear KILL, PIVOT, or KEEP decision with specific numbers and reasoning you can defend to your team.

is this skill working for me
never used
cloud runs
0
0 deployments
local fires
0
Claude Code (optional)
posts published
0
from drafts
attributed
$0.00
signups + revenue
Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/pivot-or-kill-framework/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when Jay is considering whether to kill a feature, channel, product, or whole initiative. Triggers on "should I kill", "should I pivot", "is this product dying", "is this worth continuing", "sunset this", "shut down", "cut my losses",

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/pivot-or-kill-framework/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity
never used
2026-04-03today
cost model
unitincluded
capabilities
{
  "source": "global",
  "description": "Use this skill when Jay is considering whether to kill a feature, channel, product, or whole initiative. Triggers on \"should I kill\", \"should I pivot\", \"is this product dying\", \"is this worth continuing\", \"sunset this\", \"shut down\", \"cut my losses\", or any decision about ending an effort. Provides a structured framework for the decision, signals checklist, kill mechanics, and pivot vs full-kill criteria."
}
how it gets called
{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/pivot-or-kill-framework/SKILL.md"
}
This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.