KPI Definition & Metric Contract Architect

The problem

Vague business metrics lead to data pipeline drift, conflicting reports, and lack of accountability. Generic brainstorming tools fail to address the technical nuances like cohort leakage, late-arriving data, or specific exclusion rules.

What it does

• Transforms ambiguous business requirements into auditable metric contracts with formal definitions.
• Builds an evidence ledger that maps every formula component to specific source IDs and locators.
• Identifies technical pitfalls including double counting, timezone grain mismatches, and population boundary errors.
• Generates comprehensive validation suites and conflict memos when source materials disagree.
• Distinguishes between verified facts, model inferences, and human-reserved decisions.

Why this beats prompting it yourself

Standard LLM prompts often "hallucinate" missing data or smooth over conflicting definitions to appear helpful. This skill enforces a strict traceability gate, ensuring that unknown variables are flagged as risks rather than hidden behind generic assumptions.

Use cases

• Converting messy stakeholder interview notes into technical SQL specifications.
• Auditing existing KPI definitions for logic gaps or cohort leakage.
• Creating a source-of-truth metric registry for a centralized data platform.
• Reconciling conflicting metric definitions between finance and operations departments.

Known limitations

Does not perform external data fetching or API calls. Requires provided source materials to establish the evidence ledger.