business-knowledge-interview
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
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.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- approval-consoleSkill
- approval-evidence-packSkill
- capabilitiesSkill
- consumer-data-dictionarySkill
- cross-table-lineageSkill
- dagster-orchestration-adapterSkill
- dashboard-designSkill
- dashboard-intelligenceSkill
- dbt-transformation-adapterSkill
- evidence-pack-generatorSkill
- first-hour-compassSkill
- friendly-pr-reviewerSkill
- grain-confidence-reviewerSkill
- kpi-contract-builderSkill
- pbi-mcp-write-adapterSkill
- pbip-workflowSkill
- pbip-xraySkill
- pbir-authoring-adapterSkill
- portfolio-watchSkill
- powerbi-dashboard-designSkill
- pr-readiness-reviewerSkill
- readiness-viewerSkill
- release-notes-generatorSkill
- report-intent-interviewSkill
- retail-build-warehouseSkill
- retail-control-roomSkill
- retail-discover-portfolioSkill
- retail-governSkill
- retail-initSkill
- retail-onboard-tableSkill
- retail-orchestrateSkill
- retail-scaffoldSkill
- retail-semantic-checkSkill
- retail-validateSkill
- run-next-readinessSkill
- seshat-studioSkill
- showcase-buildSkill
- source-mappingSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- bi-analyst-knowledgeSkill
- bi-bigdata-knowledgeSkill
- bi-dax-knowledgeSkill
- bi-python-knowledgeSkill
- bi-sql-knowledgeSkill
- retail-kpi-knowledgeSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 31
After retail-onboard-table has produced a committed discovery profile (or an equivalent committed profile exists).
- Distinctive: line 33
Before KPI contracts, Silver/Gold planning, DAX, dashboard blueprint, or PBIP readiness -- those stages are blocked until their critical …
- Very specific: line 97
Never self-grant an approval (Principle V.
- Distinctive: line 98
Never advance a readiness stage.
- Very specific: line 99
Never emit a numeric confidence score (never_fabricate_a_confidence_score).
- Distinctive: line 100
Never display raw suspected-PII values by default, and never commit them.
- Distinctive: line 101
Never define a metric contract or DAX (that is the retail-kpi / DAX layers).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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-tablehas 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
- 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.
- Batch the obvious low-risk items into one owner confirmation. Critical
decision types are never in a batch. The owner may exclude any item; the
remainder is approved in one action and each excluded item becomes an
individual
pendingquestion. - Ask critical decisions individually with an explicit per-decision approval
by a named human whose authority class is eligible for the decision type
(as recorded in the
approval-authoritycontract). Route any KPI-meaning question toretail-kpi-knowledge; never invent meaning here. - Ask the domain's owner questions -- only those the scoped KPIs depend on. For
each retail KPI domain the table feeds, open that domain pack in the
retail-kpi-knowledgeskill and ask the cards in its## Owner questionssection that bear on a KPI actually in scope. Do not ask a card no scoped KPI depends on: an unanswered card is recorded as a criticalpendingdecision, and the decision gate filters by decision type, not by KPI, so an out-of-scope card blocks the whole stage (asking for Net Sales by Branch must not leave a same-store ruling pending). If scope later widens, ask the cards it newly depends on then. Each card names thedecision_typeits answer records under. A card's stated layer default is CONTEXT shown to the owner -- never record it as their ruling. An unanswered in-scope card is recordedpending/needs_user_input; this layer never invents a policy to make a number appear (that layer's ambiguity Resolution rule). Not every card type blocks: thekpi_contractsgate blocks onkpi_definition,policy_rulingandmissing_value_ruleonly, so a pendingdata_exclusionortable_graincard is recorded but does NOT stop contract authoring. Report those to the owner explicitly as open-but-not-blocking rather than implying the gate will catch them -- the gate's category list is the authority, not this step. This step supplies the KPI-meaning questions step 3 routes out; it does not define a metric or a contract. - Mask suspected PII by default. Show shape-preserving masks, cite the
suspicion source. Unmasking requires an explicit owner instruction, recorded
as a
pii_handlingdecision scoped to the affected columns. Never write a raw suspected-PII value into a committed store file. - Record every outcome in the Decision Store
(
.seshat/semantic-decisions.yaml,.seshat/kpi-contracts.yaml,.seshat/cleaning-rules.yaml) -- answered =>proposed/approved; refused =>rejected/deferred; unanswered =>pending/needs_user_input; sample needed but unavailable =>needs_sample. Confidence (low/medium/high) is the agent's proposal confidence only; it is never approval and never a readiness signal.
Exit
Regenerate evidence/business-interview-review.md from the store and report the
current gate verdict for the next requested stage.
Hard stops (never)
- Never self-grant an approval (Principle V;
never_self_grant_approval). - Never advance a readiness stage.
- Never emit a numeric confidence score (
never_fabricate_a_confidence_score). - Never display raw suspected-PII values by default, and never commit them.
- Never define a metric contract or DAX (that is the retail-kpi / DAX layers).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

