| name | version_change_probe |
| description | Probe whether product, model, software, game, or platform updates after the old post could trigger a retest. |
| stage | probe |
Skill: version_change_probe
Mission
Investigate whether external version or product changes could affect the old content's reusable claim.
Use When
- The old content depends on an evolving product, model, software, tool, game, or platform feature.
- The old claim may become stale after versions, features, pricing, UI, rules, or behavior changed.
- Comments ask whether the old content still applies.
Do Not Use When
- The old content has no external object.
- The claim is timeless or purely emotional.
- Only copywriting refresh is needed.
Evidence Requirements
Strong evidence:
- official release notes
- official product blog
- changelog
- GitHub release
- app marketplace update
Weak evidence:
- unsourced summaries
- rumor threads
- undated aggregator pages
Critical Guardrail
Version change is a retest trigger. It is not proof that the old conclusion is false.
The old post's posted_at is the baseline for change judgement. Product or model information before posted_at can explain background, but it cannot be counted as a post-publication version-change trigger.
Output Contribution
Contribute external changes, affected old claims, relevance, confidence, and evidence gaps.
