Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add product-on-purpose/pm-skills --skill iterate-pivot-decisiongit clone --depth 1 https://github.com/product-on-purpose/pm-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/product-on-purpose/pm-skills/iterate-pivot-decision)<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/iterate-pivot-decision"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/iterate-pivot-decision/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/product-on-purpose/pm-skills/iterate-pivot-decision"><img src="https://agentmods.dev/badge/skills/product-on-purpose/pm-skills/iterate-pivot-decision.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00043 | $0.00814 |
| Opus 5 | $0.00022 | $0.00407 |
| Sonnet 5 | $0.00009 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
iterate-pivot-decision scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pivot Decision
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 to Use
- After significant validated learning suggests the current direction may not work
- At planned pivot-or-persevere checkpoints (e.g., after MVP launch)
- When key hypotheses have been invalidated by market feedback
- During strategy reviews when considering major direction changes
- When stakeholders are debating whether to change course
When NOT to Use
- You are reporting experiment results without a direction decision attached -> use
measure-experiment-results - The decision is technical or architectural rather than directional -> use
develop-adr - You want to explore candidate directions before deciding anything -> use
define-opportunity-tree - The team needs the period-end reflection ceremony -> use
iterate-retrospective; a pivot call is a decision document, not a retro - The product is not built yet, and the question is whether to build a new idea, feature, or scope change at all (a build / validate / cut verdict) -> use
foundation-build-risk-review; a pivot call weighs market feedback on something already shipped
Instructions
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?
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 9d ago First seen · 77 lines · 43 tokens per session scan A 19b6d94d36fd
iterate-pivot-decision is a skill published in the GitHub repository product-on-purpose/pm-skills (663 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 814 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
status-update-writer
Use when the user asks to write a status update, weekly or monthly update, stakeholder update, project update, standup, status report, or QBR. Do NOT use for writing a PRD or a retro doc — those need different structures.
stakeholder-update
Translate the same underlying project status into audience-appropriate versions (exec-brief, engineering-detail, customer-facing) without changing the underlying facts. Use when a PM needs to write a status update, especially when the same update needs to go to multiple different audiences. Pairs with…
scope-cut
Decision framework for what to cut when a spec, sprint, or launch is too big for the time or team available. Use whenever a PM says a scope needs to shrink, a deadline is fixed and the work isn't, or someone asks "what can we cut" or "what's the MVP version of this." Also trigger when reviewing a spec that feels…
escalation-judgment
Decision framework for whether a blocker, risk, or conflict is actually worth escalating to leadership versus resolving at the working level. Use when a PM is unsure whether to "loop in" a director/VP, when a team is stuck and someone suggests escalating, or when reviewing whether a past escalation was warranted. Also…
okrs
Use when asked to "set OKRs", "objectives and key results", "quarterly OKR planning", "align objectives", "measure OKR progress", or "focus priorities with OKRs". Helps teams focus on what matters most and create a cadence of progress. The OKR framework (originated by Andy Grove at Intel, popularized by John Doerr at…
shape-up
Use when asked to "shape up", "run a shaping session", "set an appetite", "scope a project without estimates", "betting table", or "ship in fixed cycles". Helps teams escape estimate-driven development and Scrum fatigue. The Shape Up method (created by Ryan Singer at Basecamp/37signals) uses fixed time boxes, variable…