Define analytics requirements with AI
Turn an open-ended request into an agreed decision, scope and definition of done. Prepare targeted questions for the people who will use the analysis.
Define analytics requirements with AI when someone has asked for a chart but cannot yet say how it will be used. The stakeholder-requirements-gathering skill helps an analyst uncover the decision, the time available and the people who need to agree on the result.
A team asking about repeat customers might be deciding whether to change a loyalty offer or whether a new ordering channel is working. Each decision can call for a different definition of “repeat”, a different comparison group and a different delivery date. Catching that difference before querying the data saves a substantial rewrite.
What it does
- Identify the person who owns the decision and who must review the analysis.
- Clarify the question behind a requested visual or spreadsheet.
- Agree on definitions, time windows, granularity and scope exclusions.
- Plan interview questions that will resolve material disagreements.
- Write a short brief with deadline, deliverable and acceptance criteria.
Install and use
- Install the skill in a compatible agent. Provide the initial request, roles and any constraints already agreed. No separate business intelligence account is required for this stage.
- Ask, “Prepare questions for the sales lead before I build a repeat-customer report. Which definitions could materially change the answer?”
- Turn the replies into a brief and ask the decision owner to confirm the scope before analytical work starts.
FAQ
Source
Made by Nimrod Fisher. Original skill: stakeholder-requirements-gathering, published on GitHub under the MIT licence.
View on GitHub