benefit-metric

To define metrics for discovery outcomes, provide the approved discovery artefact and problem statement, then trigger the /definition workflow to generate a benefit-metric artefact conforming to templates/benefit-metric.md.

Meta-benefits cover pilot situations, tooling tests, or process experiments, whereas product metrics quantify direct feature outcomes. This Skill detects meta-benefit situations and separates them from standard product metrics in the generated artefact.

Yes, you need an approved discovery artefact. The Skill enforces entry checks against artefacts/[feature]/discovery.md and optionally evaluates reference materials and product context to validate alignment before generating metrics.

Yes, the Skill optionally aligns metrics with product context by reading .github/product/mission.md and .github/product/roadmap.md if present, ensuring generated benefit-metric artefacts reflect broader product objectives.

To add compliance or risk-mitigation metrics, ensure the discovery artefact requires them. The Skill supports Tier 3 metrics specifically for compliance or risk-mitigation purposes when dictated by the approved discovery documentation.

When stakeholders request success measurement for an approved discovery, trigger the /definition workflow. The Skill produces a benefit-metric artefact that clarifies meta-benefits and product metrics, though it does not write stories.