agentleFS
KemetraKemetra/Seshat-BI/.claude/skills/business-knowledge-interview/SKILL.md

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.

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
  1. Very specific:

    After retail-onboard-table has produced a committed discovery profile (or an equivalent committed profile exists).

    line 31
  2. Distinctive:

    Before KPI contracts, Silver/Gold planning, DAX, dashboard blueprint, or PBIP readiness -- those stages are blocked until their critical …

    line 33
  3. Very specific:

    Never self-grant an approval (Principle V.

    line 97
  4. Distinctive:

    Never advance a readiness stage.

    line 98
  5. Very specific:

    Never emit a numeric confidence score (never_fabricate_a_confidence_score).

    line 99
  6. Distinctive:

    Never display raw suspected-PII values by default, and never commit them.

    line 100
  7. Distinctive:

    Never define a metric contract or DAX (that is the retail-kpi / DAX layers).

    line 101

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 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 pending question.
  3. 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-authority contract). Route any KPI-meaning question to retail-kpi-knowledge; never invent meaning here.
  4. 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-knowledge skill and ask the cards in its ## Owner questions section 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 critical pending decision, 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 the decision_type its 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 recorded pending/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: the kpi_contracts gate blocks on kpi_definition, policy_ruling and missing_value_rule only, so a pending data_exclusion or table_grain card 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.
  5. Mask suspected PII by default. Show shape-preserving masks, cite the suspicion source. Unmasking requires an explicit owner instruction, recorded as a pii_handling decision scoped to the affected columns. Never write a raw suspected-PII value into a committed store file.
  6. 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).

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.