kpi-derivelisted
Install: claude install-skill nolte/claude-shared
# KPI Derive
Determine and define the project-specific KPIs of a business application: which handful of indicators are the *key* ones for this application, and how each is defined. The output is a single human-readable artifact at `project/kpis/<slug>.md` that a reader can follow and challenge. This skill determines and defines KPIs — it never instruments, collects, computes, stores, or displays them.
Implements `spec/project/kpi-definition-process/` — the spec defines the GQM-based determination process, the per-KPI definition contract, the SMART gate, the KPI-vs-metric selection rule, the leading/lagging classification, the requirements soft-gate, and the hard measurement boundary. This skill binds those rules to the on-disk procedure and owns the interactive selection, the definition, and the write.
## German trigger phrases
This skill also triggers on equivalent German-language requests, including:
- "KPIs ableiten" / "die KPIs für diese App bestimmen"
- "unsere Schlüsselkennzahlen definieren"
- "KPIs aus den Anforderungen herleiten"
- "die KPIs nach der Zieländerung neu ableiten" (→ `revisit`)
## User-language policy
Detect the user's language from their message and conduct the interview in it — KPI selection is a dialogue. The written artifact uses the surrounding repository's primary language (English by default; follow the precedent of the existing `project/` docs). The per-KPI contract field keys (`id`, `name`, `definition`, `formula-intent`, `unit`, `target`,