Documents strategic pivot or persevere decisions for products, features, or strategies with evidence, analysis, and rationale from market feedback.
From pm-skillsnpx claudepluginhub product-on-purpose/pm-skillsThis skill uses the workspace's default tool permissions.
references/EXAMPLE.mdreferences/TEMPLATE.mdGuides AI-assisted editing of real video footage: transcribe/plan cuts with Claude, execute via FFmpeg bash scripts, augment with Remotion/ElevenLabs/fal.ai, polish in Descript/CapCut.
Ingests video/audio from files, URLs, RTSP, desktop; indexes/searches moments with timestamps/clips; transcodes/edits timelines (subtitles/overlays/dubbing); generates assets and live alerts.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
A pivot decision document captures the analysis and rationale behind a strategic direction change—or the decision to stay the course. Based on the Lean Startup concept of "pivot or persevere," this artifact ensures major strategic decisions are made with evidence, communicated clearly, and preserved for organizational learning.
When asked to document a pivot decision, follow these steps:
Summarize Current State Document what you're currently doing, how long you've been doing it, what you've invested, and what results you've achieved. This grounds the decision in reality.
Present the Evidence Compile all relevant data: metrics, user feedback, experiment results, market signals. Be comprehensive—include evidence that supports both staying and changing course.
Review Hypotheses Revisit the original hypotheses that justified the current direction. Which have been validated? Which have been invalidated? Which remain untested?
Define Options Articulate at least three options: persevere (continue current direction), and two or more distinct pivot options. Describe each option concretely—what would change?
Analyze Each Option Evaluate options against key criteria: market opportunity, competitive advantage, team capability, resource requirements, and risk. Use evidence, not opinions.
Make the Decision State the chosen direction clearly. Explain the rationale, acknowledging trade-offs. If the team disagrees, capture dissenting views.
Plan Implementation Outline what happens next: immediate actions, resource needs, success criteria for the new direction, and communication plan.
Use the template in references/TEMPLATE.md to structure the output.
Before finalizing, verify:
See references/EXAMPLE.md for a completed example.