Forge-Product-Evaluation

Evaluates delivered product outcomes against objectives and success measures defined at Specify.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-product-evaluation-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Product-Evaluation
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/01-Product/Forge-Product-Evaluation
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-product-evaluation-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often ship features without ever checking whether the delivered product achieved the objectives set during planning, leaving decisions driven by opinion rather than evidence. This Skill closes that loop by comparing actual usage, value, and stakeholder satisfaction against the original success measures and converting findings into evidence-based product decisions. ## Core Features & Use Cases - Outcome-Gap Analysis: Recovers objectives from the Project Definition and compares intended outcomes against observed usage, operational, and support data. - Evidence-Based Recommendations: Formulates continue, adjust, or retire options with trade-offs, routed to Roadmap Planning and Prioritisation. - Structured Seven-Step Method: Guides evaluation from objective recovery through evidence selection, collection, analysis, gap diagnosis, recommendation, and routing. - Use Case: After a feature has been live for a quarter, use this Skill during the Improve phase to check whether adoption targets were met, diagnose whether gaps stem from understanding, implementation, adoption, or measurement, and feed recommendations into the next planning cycle. ## Quick Start Ask the AI to evaluate whether the recently released feature achieved the objectives and success measures recorded in the Project Definition, using current usage and support data.

Frequently Asked Questions about Forge-Product-Evaluation

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

FAQPage Schema
How do I evaluate whether a product feature met its objectives?▼

Recover the original objectives and success measures from the Project Definition, select evidence that could falsify success for each objective, then compare observed usage and outcome data against them. The result is an outcome-gap analysis with continue, adjust, or retire recommendations.

What is an outcome-gap analysis in product evaluation?▼

An outcome-gap analysis documents what was intended, what is actually observed, and why they differ. For each gap, it diagnoses whether the cause is understanding, implementation, adoption, or measurement, so recommendations address the real problem.

When should a product evaluation be performed?▼

Run it during the Improve phase once a feature has been live long enough to produce signal, before major new investment in an existing capability, or when stakeholder opinion conflicts with observed data. Do not use it for release-gate quality verdicts.

Can I evaluate a product if no success measures were recorded?▼

No. If objectives or success measures were never recorded, establish them first through scope definition, then evaluate. Evaluation without a baseline produces opinion rather than evidence.

What is the difference between product evaluation and technical debt assessment?▼

Product evaluation assesses external outcomes such as usage, value, and stakeholder satisfaction against objectives. Technical debt assessment examines internal code and architecture quality. The two views complement each other but answer different questions.