report-intent-interview

Interviews report requesters to capture dashboard intent as an approved report-intent.yaml artifact.

2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Kemetra/Seshat-BI --skill report-intent-interview-kemetra
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: report-intent-interview
Source: https://github.com/Kemetra/Seshat-BI/tree/main/.claude/skills/report-intent-interview
Command: npx skills add https://github.com/Kemetra/Seshat-BI --skill report-intent-interview-kemetra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Dashboard projects often start from vague requests like "build an executive dashboard," leaving audience, purpose, and business questions unrecorded and downstream design work untraceable. This Skill converts a plain-language report request into a committed, reviewable Report Intent artifact with a named-human approval before any blueprint or visual spec is authored. ## Core Features & Use Cases - Structured intent capture: Interviews the requester on audience, purpose, supported decision, review cadence, business questions, metric roles, comparisons, filters, drill paths, and accessibility needs, then writes report-intent.yaml per the project template. - Governed approval flow: Batches low-risk items for one owner confirmation while asking critical decisions individually, recording a report_intent_approval decision from a named human of authority class report_owner. - Metric contract discipline: References outcome, driver, and guardrail metrics by name against approved contracts only; missing contracts are recorded as gaps that leave the intent blocked rather than invented. - Use Case: A stakeholder says "I need a weekly report for branch managers to spot underperforming branches." The Skill interviews them, masks PII-adjacent filters, records the intent, and blocks downstream dashboard design until the owner approves. ## Quick Start Interview me to capture the intent for a weekly branch performance report and record it as a report intent artifact.

Frequently Asked Questions about report-intent-interview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture dashboard requirements before designing a Power BI report?▼

Run a structured intent interview that records audience, purpose, supported decision, business questions, and metric roles into a report-intent.yaml artifact. Downstream blueprint and composition stages stay blocked until a named report owner approves the intent.

What is a report intent artifact in a BI workflow?▼

It is a committed YAML file recording why a report exists: audience, purpose, review cadence, business questions, and metric roles referenced by name. Every downstream artifact such as blueprints and visual specs traces back to it.

Can the interview define new metrics for my dashboard?▼

No. Metrics are referenced by name only against approved metric contracts. If a needed metric has no approved contract, the gap is recorded, routed upstream to metric-contract definition, and the intent stays blocked on that metric.

What happens if the report request is too vague?▼

Vague requests like "build an executive dashboard" trigger disambiguating questions. The intent is not committed until audience, purpose, and at least one primary business question are resolved.

How is PII handled during the report intent interview?▼

Suspected PII in dimensions or filters is masked by default and never displayed or committed raw. Unmasking requires an explicit owner instruction recorded as a pii_handling decision.

When should I not use a report intent interview?▼

Skip it only when an approved intent already exists, in which case it is loaded for confirmation or supersession. It also cannot run without approved metric contracts and a ready semantic model; those prerequisites must be satisfied first.