pressure-test

Critique plans, roadmaps, PRDs, bets, or strategies for evidence and scope gaps.

14|Updated Jun 29, 2026

Search Tags:#roadmap #strategy #evidence #prd #critique #pressure test

Ready to run

npx skills add https://github.com/sparkline-ventures/product-eval --skill pressure-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pressure-test
Source: https://github.com/sparkline-ventures/product-eval/tree/main/skills/pressure-test
Command: npx skills add https://github.com/sparkline-ventures/product-eval --skill pressure-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you challenge an existing plan, roadmap, PRD, bet, or strategy before committing resources, so weak assumptions and hidden risks are exposed early.

Core Features & Use Cases

Adversarial review: Critiques an already-defined artifact rather than generating new ideas.
Evidence and consistency checks: Verifies that the problem, solution, metrics, and scope line up with the supporting evidence and decision log.
Blocking issue detection: Flags missing evidence, vague requirements, missing acceptance criteria, weak metrics, scope drift, and other readiness gaps.
Use case: A product manager can pressure-test a Q3 roadmap to find what will fail, what needs more proof, and whether the scope should be expanded, held, or reduced.

Quick Start

Ask the assistant to pressure-test your existing plan or PRD and call out the blocking issues, suggestions, strengths, scope mode, and readiness verdict.

Frequently Asked Questions about pressure-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I stress-test a product roadmap before committing resources?▼

To stress-test a product roadmap, you need an adversarial review that checks evidence, validates scope, and tests assumptions. This process exposes weak assumptions and flags blocking issues like missing acceptance criteria or scope drift before execution begins.

What is adversarial review for a PRD and when do I need it?▼

Adversarial review for a PRD is a critique of an already-defined plan that verifies problem-solution alignment and cross-stage consistency. You need it before execution to detect hidden risks, vague requirements, and weak metrics that could cause the strategy to fail.

Can I use this to check if my strategy scope should be expanded or reduced?▼

Yes, you can critique your strategy to receive a scope-mode recommendation. The evaluation tests assumptions and checks readiness, outputting a verdict on whether your scope should be held, expanded, or reduced based on supporting evidence.

What is the best way to find blocking issues in a Q3 roadmap?▼

The best way to find blocking issues in a Q3 roadmap is applying multi-lens evaluation to flag missing evidence and weak metrics. This readiness check highlights what will fail, what needs more proof, and validates decision artifacts.

How do I validate assumptions and evidence in a product strategy?▼

You validate assumptions in a product strategy by running consistency checks across problem, solution, metrics, and scope against the supporting evidence. This flags readiness gaps and scope drift, ensuring your decision log aligns with your planned bets.