Report requirements translator

Skill nicholashidalgo/claude-skillforge/data-engineering/report-requirements-translator

Install

npx -y skills add nicholashidalgo/claude-skillforge --skill report-requirements-translator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Convert messy business requests into a clean implementation-ready report specification with grain, measures, filters, assumptions, and open questions.

SKILL.md

1.8 KB, as published. Nobody here has run it

Runtime Configuration

version: "1.0.0"
gotcha_pack: "sql-data-gotcha-pack"
gotcha_pack_version: "1.0.0"
gotcha_enforcement: "block_on_high"

Purpose

Convert a stakeholder request into a build-ready report spec.

Capture

business objective
intended audience
report grain
measures
dimensions
filters and prompts
date logic
output format
assumptions
unresolved questions
delivery priority

Rules

Surface ambiguity early.
Distinguish must-have from optional scope.
Push for concrete KPI definitions.
Document exclusions and edge cases.

Output format

Objective
Audience
Grain
Measures and definitions
Dimensions and filters
Layout or delivery notes
Assumptions
Open questions

Gotcha Enforcement

A spec that leaves these HIGH-risk areas unresolved is not build-ready. Resolve each HIGH item or escalate it as a blocking open question. Flag MEDIUM items in Implementation notes.

ID	Sev	Check
G006	HIGH	If the spec mixes measures from different grains, call it out as a blocking ambiguity
G008	HIGH	Every KPI in the spec must have explicit inclusions AND exclusions documented
G009	MEDIUM	If a column is listed as a measure, note that null rate must be checked before build
G013	LOW	Any top-N or ranked output must include tie-break and minimum-record behavior