When should I use the Pivot Analysis skill?

You should use this skill whenever a project hits a significant blocker—such as technical limitations, legal risks, or excessive complexity—to determine the most efficient path forward.

How does the skill compare different pivot options?

It generates a comparison matrix that weighs factors such as implementation effort, risk of new blockers, preservation of invested time, and overall market viability.

Is this skill part of a larger workflow?

Yes, it is designed to work within the mcp-opportunity-pipeline, often triggered by the pivot command or following a project critique that results in a 'PIVOT' decision.

What are the three types of pivots the skill analyzes?

The skill evaluates 'new_idea' (starting a new project), 'new_approach' (changing the solution for the same problem), and 'new_scope' (simplifying the existing idea).

Pivot Analysis

Name: Pivot Analysis
Author: JesseHenson

byJesseHenson

Productivity & Workflow

Evaluates project blockers and provides weighted recommendations for strategic pivots within an opportunity pipeline.

About

The Pivot Analysis skill enables Claude to perform structured strategic evaluations when a development project hits a roadblock. By categorizing blockers into technical, legal, economic, or scope-related categories, the skill systematically compares three primary pivot strategies: starting fresh with a new idea, pivoting to a new technical approach, or reducing scope to a minimum viable product. It helps developers and product managers move past sunk cost fallacies by providing data-driven comparisons of effort, risk, and market viability for each potential path forward.

Key Features

Automated integration with MCP opportunity pipeline commands
Comparison matrix for New Idea, New Approach, and New Scope strategies
0 GitHub stars
Actionable recommendations with concrete implementation steps
Effort and risk assessment for each potential pivot path
Structured blocker categorization for technical, legal, and economic hurdles

Use Cases

Deciding whether to replace a deprecated API or move to a different project entirely
Downsizing a complex project spec to a manageable MVP when development stalls
Determining the most viable alternative when a project faces unexpected legal or TOS risks

About

Key Features

Automated integration with MCP opportunity pipeline commands
Comparison matrix for New Idea, New Approach, and New Scope strategies
0 GitHub stars
Actionable recommendations with concrete implementation steps
Effort and risk assessment for each potential pivot path
Structured blocker categorization for technical, legal, and economic hurdles

Use Cases

Deciding whether to replace a deprecated API or move to a different project entirely
Downsizing a complex project spec to a manageable MVP when development stalls
Determining the most viable alternative when a project faces unexpected legal or TOS risks