design-analysis

To translate a vague business question into a structured analytics brief, you define the unit of analysis, pin the time window, and ground the data sources. This interrogation-driven process produces a formal brief for downstream query-writing.

The best way to scope a data analysis brief for a metric change is to apply interrogation-driven planning that pins the unit of analysis, time window, and data sources, yielding an actionable set of queries for downstream tasks.

Yes, you can use this skill to plan queries for relationship testing. It accepts questions like whether there is a relationship between A and B and outputs a grounded, actionable brief for downstream query-writing skills.

Yes, you need Narrative MCP to anchor schema grounding. The skill uses this connection to interrogate your analytical question and pin the exact data sources required for the formal analytics brief.

You prepare an actionable set of queries from an ambiguous analytics request by applying phase-guided planning. This translates the request into a grounded brief that specifies the unit of analysis and time window for downstream implementation.

Generating an analytics brief without pinning the unit of analysis causes ungrounded results and downstream rework. The skill mitigates this by formally interrogating your question to lock the time window and data sources before query generation.