impact-sizing

Apply a four-step framework to forecast feature engagement, revenue, and profitability.

Updated Mar 11, 2026

Search Tags:#planning #product-management #driver-tree #confidence-levels #impact-sizing #feature-value

Ready to run

npx skills add https://github.com/pisithrps/yapzee --skill impact-sizing-pisithrps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impact-sizing
Source: https://github.com/pisithrps/yapzee/tree/main/.claude/skills/impact-sizing
Command: npx skills add https://github.com/pisithrps/yapzee --skill impact-sizing-pisithrps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quantify the potential impact of a feature early in planning with a structured, repeatable approach so decisions are data-informed rather than guesswork.

Core Features & Use Cases

Stepwise 4-step sizing framework to estimate usage, impact, de-risk assumptions, and define takeaways.
Driver-tree mapping that links feature to engagement, revenue, and profit metrics.
Output-ready sizing artifacts and integration guidance for PRDs and strategy docs.

Quick Start

Provide the feature name and any relevant context to start sizing its impact with the 4-step framework.

Frequently Asked Questions about impact-sizing

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

FAQPage Schema

How do I quantify feature value for a product requirements document?▼

To quantify feature value for a product requirements document, apply a four-step impact sizing framework that estimates usage, maps driver-trees to revenue, and de-risks assumptions to produce defensible impact estimates.

What is the best way to estimate feature impact during product planning?▼

The best way to estimate feature impact during product planning is using a structured driver-tree mapping approach that links features directly to engagement, revenue, and profit metrics for data-informed decision making.

How do I forecast engagement and revenue for a new feature?▼

Forecast engagement and revenue for a new feature by mapping driver-trees that connect the feature to historical metrics and business information, applying confidence levels to de-risk your assumptions.

Can I use driver-tree mapping for strategy reviews without historical metrics?▼

Driver-tree mapping for strategy reviews relies heavily on historical metrics and user research context. Without this data, computing defensible impact estimates becomes guesswork rather than data-informed planning.

Why does impact sizing require de-risking assumptions?▼

Impact sizing requires de-risking assumptions because forecasting feature value involves uncertainty. The framework applies confidence levels to assumptions, ensuring engagement and profitability estimates remain defensible during strategy reviews.

What context do I need to start impact sizing a feature?▼

To start impact sizing a feature, you need context from PRDs, user research, business information, and historical metrics. This data feeds the four-step framework to forecast engagement, revenue, and profitability accurately.