report-intent-interviewlisted

Given approved metric contracts and a ready semantic model, interview the report requester to capture what a dashboard report is FOR -- audience, purpose, supported decision, review cadence, primary business questions, outcome/driver/guardrail metrics (referenced by name only, never defined), comparisons, dimensions/filters, expected actions/exceptions, pages/drill paths, and mobile/accessibility/language/RTL needs -- and record the result as a committed Report Intent artifact plus a named-human `report_intent_approval` decision. Use when someone describes a report they need in plain language, before any page blueprint, visual spec, or report composition is authored. It asks obvious low-risk items as one batch and critical items individually with explicit named-human approval; it masks PII by default; it records the intent and STOPS. It does NOT define metric meaning, does NOT self-grant any approval, and does NOT emit a confidence score.
Kemetra/Seshat-BI · ★ 2 · Data & Documents · score 68

Install: claude install-skill Kemetra/Seshat-BI

# report-intent-interview The Report Intent Interview is the missing front end of the dashboard intelligence journey (spec 123, US1). It converts a conversational report request into a committed, reviewable `report-intent.yaml` so every downstream artifact (blueprint, composition, preview, audit, PBIR) traces back to a clear, approved report purpose instead of an unrecorded assumption. This skill mirrors `.claude/skills/business-knowledge-interview/SKILL.md` structurally (load-existing-first, batch/critical question grouping, PII masking, record + STOP, never self-grant) but does NOT extend it: the `required_inputs` and `focus` differ. Behavior is governed by the contract `contracts/interview/report-intent-interview.yaml`; the shape of the produced artifact is `templates/report-intent.yaml`. The static rule DL9 (`seshat check`) verifies the recorded artifact's SHAPE, not the conversation. ## When to use - Someone describes a report they need in plain language ("I need a weekly report for branch managers to spot underperforming branches"). - Before `dashboard-design`, the dashboard coordinator, page blueprints, visual specs, or report composition -- those stages trace their `business_question` back to a question declared here (FR-002a) and are blocked until this intent's own `report_intent_approval` decision is approved. ## Preconditions (stop if unmet) - Approved metric contracts exist for the subject area (`readiness.status: pass`). **No approved contract for