prd-v03-outcome-definition_skill

This skill defines measurable KPIs for product types, sets targets, and links metrics to go/no-go decisions and downstream processes.
  • Python

17

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill mattgierhart/prd-driven-context-engineering --skill prd-v03-outcome-definition

  • SKILL.md5.3 KB

Overview

This skill defines measurable success metrics (KPIs) tied to a product type during PRD v0.3 Commercial Model. It translates the v0.2 Product Type Classification into prioritized Tier 1–3 metrics, sets evidence-based targets, and links each KPI to downstream gates. Outputs are KPI- entries with definitions, targets, evidence sources, measurement cadence, and decision linkages.

How this skill works

On request, the skill consumes the Product Type Classification from v0.2 and selects metrics aligned to that type using the Metric Quality Hierarchy. It recommends both leading and lagging indicators, proposes evidence-based targets (benchmarks, competitor data, or internal baselines), and formats each result as KPI- entries with thresholds, evidence sources, measurement method, and downstream gate linkages. It flags anti-patterns and ensures at least one Tier 1 metric is present.

When to use it

  • Defining success criteria during PRD v0.3 Commercial Model
  • When asked “how do we measure success?” or “what metrics matter?”
  • Setting KPI targets and go/no-go thresholds for a product initiative
  • Translating product type classification into measurable outcomes
  • Preparing KPI inputs for v0.5 Red Team or v0.9 GTM dashboards

Best practices

  • Always include at least one Tier 1 (revenue/churn/LTV:CAC) metric
  • Pair leading indicators (weekly) with lagging indicators (monthly) for early course correction
  • Set targets from evidence: benchmarks, competitor data, or empirical baselines—avoid arbitrary round numbers
  • Map each KPI to a downstream decision gate (e.g., v0.5 Red Team kill criteria)
  • Avoid Tier 3 vanity metrics unless correlated to Tier 1/2 outcomes

Example use cases

  • Clone product: produce KPI- entries for feature parity, time-to-first-value vs leader, and price delta targets
  • Undercut strategy: define price-per-unit targets, niche conversion rate, and CAC thresholds tied to target segment
  • Wrapper/integration: set KPI for time saved per workflow, integration adoption rate, and API reliability with measurement methods
  • Innovation play: define education→activation conversion, behavioral change rate, and reference-customer targets for early validation
  • GTM prep: export KPI-entries into launch dashboard and v0.5 Red Team kill rules

FAQ

Use internal baselines or conservative industry proxies, document the evidence source as internal CFD/BR reference, and set short evaluation windows to iterate.

Can we use engagement metrics as primary KPIs?

Only if they correlate to Tier 1/2 outcomes. Engagement alone is often a vanity metric—ensure a clear causal path to revenue or retention.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational