business-knowledge-interviewlisted

After a database is discovered and profiled, interview the business owner to capture the meaning-critical decisions the rest of the Database-to-PBIP flow depends on -- KPI meaning, PII handling, table grain, primary keys, relationships, missing-value rules, and ambiguous financial/quantity/date columns -- and record every outcome in the project Decision Store. Use when someone asks to run the interview, capture business knowledge, or resolve the business questions behind a model in the Seshat BI repo. It asks obvious low-risk items as one batch and critical items individually with explicit named-human approval; it uses masked samples and never shows raw suspected PII by default; it records decisions and STOPS. It does NOT define metric contracts or DAX, does NOT self-grant any approval, and does NOT emit a confidence score.
Kemetra/Seshat-BI · ★ 2 · API & Backend · score 68

Install: claude install-skill Kemetra/Seshat-BI

# business-knowledge-interview The interview is the front door of the Database-to-PBIP flow's decision layer (spec 121). It converts a discovery profile into recorded, approvable business decisions so that every downstream stage consumes governed answers instead of unrecorded assumptions. Behavior is governed by the `business-knowledge-interview` contract and its recorded interview protocol. The static rules DS1-DS5 (`seshat check`) verify the recorded outcome, not the conversation. ## When to use - After `retail-onboard-table` has produced a committed discovery profile (or an equivalent committed profile exists). - Before KPI contracts, Silver/Gold planning, DAX, dashboard blueprint, or PBIP readiness -- those stages are blocked until their critical decisions are approved. ## Preconditions (stop if unmet) - A committed discovery profile exists. **No profile => do not start**; report the gate as blocked naming the missing profile. - Load the existing Decision Store first. Existing decisions are presented for confirmation or supersession -- **never overwritten**. ## How it runs 1. **Ground every question in the profile** (profile summaries, candidate grains, column types). Do not walk every column one-by-one unless the owner asks or an ambiguity requires it. Concentrate on: KPI inputs, PII, table grain, keys, relationships, missing-value rules, and ambiguous financial/quantity/date columns. 2. **Batch the obvious low-risk items** into one owner co