decision-readiness

Evaluates whether product evidence is sufficient for a build decision.

14|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/sparkline-ventures/product-eval --skill decision-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-readiness
Source: https://github.com/sparkline-ventures/product-eval/tree/main/skills/decision-readiness
Command: npx skills add https://github.com/sparkline-ventures/product-eval --skill decision-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you decide whether a product bet has enough credible evidence to justify commitment, or whether you should pause for more proof. It turns scattered signals into a clear verdict so you do not overcommit on weak data or miss a strong opportunity.

Core Features & Use Cases

  • Evidence sufficiency check: Verifies whether the evidence meets the minimum gate for a build decision.
  • Confidence-based verdicts: Produces one of three outcomes: Decide now, Run a research sprint, or Do not commit yet.
  • Evidence weighting and deduplication: Rates and combines evidence by strength, recency, independence, and contradiction handling.
  • Gap identification: Flags exactly what is missing and where to look to close the confidence gap.
  • Use case: A PM asks whether a roadmap item is ready to ship; this Skill reviews support tickets, analytics, interviews, and related sources to judge readiness.

Quick Start

Ask the decision-readiness skill whether there is enough evidence to commit to this bet and tell it which sources or scope to evaluate.

Frequently Asked Questions about decision-readiness

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

FAQPage Schema
How do I know if I have enough product evidence to commit to a build decision?

Product evidence sufficiency is evaluated by applying confidence scoring and evidence weighting to support tickets, analytics, and interviews. This process deduplicates signals and applies a readiness gate to determine if you have enough credible proof to commit to a build decision.

What is evidence weighting and how does it work for product management?

Evidence weighting for product management is a method of rating and combining scattered signals by strength, recency, and independence. It handles contradictions across support and sales sources to deduplicate inputs and generate a reliable confidence score for roadmap planning.

How do I run a research sprint to close confidence gaps on a product bet?

To run a research sprint for a product bet, you must first identify the specific missing data points and where to find them. This gap analysis outputs a targeted research plan that gathers the necessary proof to elevate your confidence score above the readiness gate.

Can I use support tickets and sales data to evaluate decision readiness for a roadmap item?

Yes, you can use support tickets and sales data to evaluate decision readiness. The evaluation combines these sources with analytics and interviews, applying evidence weighting and contradiction handling to deduplicate inputs and verify if the combined signals meet the minimum gate for a build decision.

What is the best way to decide whether to ship a roadmap item or wait for more proof?

The best way to decide whether to ship a roadmap item is to apply a readiness gate that yields one of three confidence-based verdicts: decide now, run a research sprint, or do not commit yet. This prevents overcommitting on weak data while ensuring strong opportunities are captured.

When should I not use confidence scoring for a product build commitment?

You should not rely solely on confidence scoring for a product build commitment when your evidence sources lack independence or are heavily contradictory. In such cases, the readiness gate will flag explicit gaps, indicating you should pause and run a targeted research sprint rather than proceeding to a decision memo.