By name: stakeholder-requirements-gathering description: Structured requirements elicitation for analysis requests. Use when scoping new analysis projects, clarifying ambiguous business questions, or documenting analysis acceptance criteria with stakeholders.
When to use
At the start of any non-trivial analysis request, especially when the ask is vague ("can you look into X?"), when multiple stakeholders have a stake in the outcome, or when the result will drive an important decision. Spending 30 minutes on requirements prevents days of rework.
Process
- Run the intake interview — use the question guide in
assets/interview_guide.mdto surface: the business decision being made, who the audience is, what "done" looks like, and what constraints exist. - Identify the decision type — apply
references/decision_maker_framework.mdto classify the decision (strategic / operational / tactical) and calibrate the required rigour and format. - Document requirements — fill in
assets/requirements_doc_template.mdcovering: business question, success criteria, scope inclusions/exclusions, data sources, and timeline. - Resolve ambiguities — use the elicitation techniques in
references/elicitation_techniques.mdfor any requirement still unclear after the interview (5-whys, scenario walkthrough, MoSCoW prioritisation). - Get explicit sign-off — send the requirements doc to the requestor for confirmation before starting work; update based on feedback.
- Produce the analysis brief — convert approved requirements into
assets/analysis_brief_template.md, which becomes the authoritative scope document for the project.
Inputs the skill needs
- Stakeholder's initial request (however vague)
- Name and role of primary requestor and any other stakeholders
- Proposed deadline or urgency level
Output
- Completed requirements doc (
requirements_doc_template.md) - Analysis brief ready to hand to the analyst (
analysis_brief_template.md) - Interview notes (optional, for complex projects)