mcpField
S
stakeholder-requirements-gathering

stakeholder-requirements-gathering

github.com/nimrodfisherData & databases504214 installsUpdated 5w ago
Repository

About stakeholder-requirements-gathering

A skill for turning vague or consequential analysis requests into agreed requirements and an analysis brief. It guides analysts through stakeholder interviews, decision classification, ambiguity resolution, and sign-off before work begins.

Key features

  1. 01Stakeholder intake interview
  2. 02Decision-type classification
  3. 03Requirements documentation
  4. 04Ambiguity resolution techniques
  5. 05Approval and analysis brief

Use cases

  1. 01Scoping a vague analysis request
  2. 02Aligning multiple stakeholders before analysis
  3. 03Agreeing success criteria and project scope

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nimrodfisher/data-analytics-skills --skill stakeholder-requirements-gathering

After installing, type/stakeholder-requirements-gatheringin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

assets/
analysis_brief_template.md
interview_guide.md
requirements_doc_template.md
references/
decision_maker_framework.md
elicitation_techniques.md

Details

From the project README

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

  1. Run the intake interview — use the question guide in assets/interview_guide.md to surface: the business decision being made, who the audience is, what "done" looks like, and what constraints exist.
  2. Identify the decision type — apply references/decision_maker_framework.md to classify the decision (strategic / operational / tactical) and calibrate the required rigour and format.
  3. Document requirements — fill in assets/requirements_doc_template.md covering: business question, success criteria, scope inclusions/exclusions, data sources, and timeline.
  4. Resolve ambiguities — use the elicitation techniques in references/elicitation_techniques.md for any requirement still unclear after the interview (5-whys, scenario walkthrough, MoSCoW prioritisation).
  5. Get explicit sign-off — send the requirements doc to the requestor for confirmation before starting work; update based on feedback.
  6. 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)

Comments

Markdown supported