Agent skill

Stakeholder Requirements Gathering

by nimrodfisher in nimrodfisher/data-analytics-skills

Structured requirements elicitation for analysis requests. An agent skill from nimrodfisher/data-analytics-skills.

MITAuto-check passedAgent Workflows

Install Stakeholder Requirements Gathering

skills CLI
$ npx skills add nimrodfisher/data-analytics-skills --skill stakeholder-requirements-gathering -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install nimrodfisher/data-analytics-skills stakeholder-requirements-gathering --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/nimrodfisher/data-analytics-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/05-stakeholder-communication/stakeholder-requirements-gathering .claude/skills/stakeholder-requirements-gathering && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
stakeholder-requirements-gathering
GitHub stars
470
Token cost
~513 tokens
SKILL.md length
223 words
Files
6 (incl. references, assets)
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Structured requirements elicitation for analysis requests. An agent skill from nimrodfisher/data-analytics-skills.

  • Works in 6 steps: Run the intake interview — use the… → Identify the decision type — apply… → Document requirements — fill in… → …
  • Scoping new analysis projects
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Clarifying ambiguous business questions

What it does

Stakeholder Requirements Gathering is an agent skill from nimrodfisher/data-analytics-skills. Structured requirements elicitation for analysis requests. Use when scoping new analysis projects, clarifying ambiguous business questions, or documenting analysis acceptance criteria with stakeholders.

Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `assets/analysis_brief_template.md`, `assets/interview_guide.md` and `assets/requirements_doc_template.md`).

It sits in Agent Workflows, covering Requirements gathering, User stories and Internal communications. The repository describes itself as: A comprehensive list of Claude & Codex skills for a wide range of data analytics tasks. The licence is MIT.

When your agent uses it

  • Scoping new analysis projects
  • Clarifying ambiguous business questions
  • Documenting analysis acceptance criteria with stakeholders

Example prompts

  • “/stakeholder-requirements-gathering”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Run the intake interview — use the question guide in assets/interview_guide.md to surface: the business decision being made, who the…
  2. Identify the decision type — apply references/decision_maker_framework.md to classify the decision (strategic / operational / tactical)…
  3. Document requirements — fill in assets/requirements_doc_template.md covering: business question, success criteria, scope…
  4. Resolve ambiguities — use the elicitation techniques in references/elicitation_techniques.md for any requirement still unclear after the…
  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…

What it can do on your machine

Read from SKILL.md and the folder at commit 9449d36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Stakeholder Requirements Gathering loads about 513 tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 223 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~513
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from nimrodfisher/data-analytics-skills at commit 9449d36, republished under its MIT licence (© nimrodfisher). 223 words, ~513 tokens.

Download SKILL.mdSave it as .claude/skills/stakeholder-requirements-gathering/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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

  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)

© nimrodfisher, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (references, assets) in 05-stakeholder-communication/stakeholder-requirements-gathering of nimrodfisher/data-analytics-skills.

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

Open the folder on GitHubat commit 9449d36

Compare with similar skills

Stakeholder Requirements Gathering next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Stakeholder Requirements Gathering compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stakeholder Requirements Gathering this skillnimrodfisher/data-analytics-skills470—~513Automated safety check: PassMIT
Extracting Requirementsprime-radiant-inc/iterative-development181—~2.7kAutomated safety check: PassApache-2.0
Feature ForgeJeffallan/claude-skills12k—~1.1kAutomated safety check: PassMIT
Specificationcitypaul/.dotfiles740—~2.2kAutomated safety check: PassCustom licence
Find Gapscitypaul/.dotfiles740—~6.6kAutomated safety check: PassCustom licence
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence

Similar skills

  • Extracting Requirements

    prime-radiant-inc/iterative-development

    Reads human-written spec documents and produces per-epic requirement files with proof obligations plus behavior scenarios with stable IDs, using parallel chunked extraction.

    181 GitHub stars~2.7k tokensUpdated 4 mo ago
    Agent WorkflowsAuto-check passed
  • Feature Forge

    Jeffallan/claude-skills

    Runs a structured requirements interview to produce a feature specification with EARS requirements, acceptance criteria and an implementation checklist.

    12k GitHub stars~1.1k tokensUpdated 7 days ago
    Product & Project ManagementAuto-check passed
  • Specification

    citypaul/.dotfiles

    Turn fuzzy intent into shared understanding and acceptance criteria — specification as a conversation, run one question at a time, before any story is split or planned.

    740 GitHub stars~2.2k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Find Gaps

    citypaul/.dotfiles

    Adversarially review an existing written artifact — stories, plans, acceptance criteria, specs, or design mocks — to surface missing states, unhandled edge cases, unstated assumptions, unverifiable…

    740 GitHub stars~6.6k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed
  • PRD Development

    deanpeters/Product-Manager-Skills

    Builds a structured PRD that ties problem, users, solution and success criteria together, turning discovery notes into a document engineers can act on.

    7.2k GitHub starsUsed in 3 repos~6.2k tokens
    Product & Project ManagementAuto-check passed

More from nimrodfisher/data-analytics-skills

All 31 skills in this repo
  • Ab Test Analysis

    nimrodfisher/data-analytics-skills

    Rigorous A/B test statistical analysis. An agent skill from nimrodfisher/data-analytics-skills.

    470 GitHub stars~708 tokensUpdated 16 days ago
    Auto-check passed
  • Analysis Assumptions Log

    nimrodfisher/data-analytics-skills

    Track and document analytical assumptions and decisions. An agent skill from nimrodfisher/data-analytics-skills.

    470 GitHub stars~578 tokensUpdated 16 days ago
    Auto-check passed
  • Analysis QA Checklist

    nimrodfisher/data-analytics-skills

    Pre-delivery quality assurance for analysis work. An agent skill from nimrodfisher/data-analytics-skills.

    470 GitHub stars~470 tokensUpdated 16 days ago
    Auto-check passed
  • Business Metrics Calculator

    nimrodfisher/data-analytics-skills

    Standard business metric calculation with industry benchmarks.

    470 GitHub stars~668 tokensUpdated 16 days ago
    Auto-check passed
  • Cohort Analysis

    nimrodfisher/data-analytics-skills

    Time-based cohort analysis with retention and behaviour tracking.

    470 GitHub stars~660 tokensUpdated 16 days ago
    Auto-check passed
  • Context Packager

    nimrodfisher/data-analytics-skills

    Efficiently package context for AI-assisted analysis. An agent skill from nimrodfisher/data-analytics-skills.

    470 GitHub stars~500 tokensUpdated 16 days ago
    Auto-check passed

Questions about Stakeholder Requirements Gathering

What does Stakeholder Requirements Gathering do?

Structured requirements elicitation for analysis requests. An agent skill from nimrodfisher/data-analytics-skills. Stakeholder Requirements Gathering is an agent skill from nimrodfisher/data-analytics-skills. Structured requirements elicitation for analysis requests.

When should I use Stakeholder Requirements Gathering?

Stakeholder Requirements Gathering fits situations like: scoping new analysis projects; clarifying ambiguous business questions; documenting analysis acceptance criteria with stakeholders.

How do I install Stakeholder Requirements Gathering in Claude Code?

Run `npx skills add nimrodfisher/data-analytics-skills --skill stakeholder-requirements-gathering -a claude-code`. Or copy the skill folder (05-stakeholder-communication/stakeholder-requirements-gathering in nimrodfisher/data-analytics-skills) into .claude/skills/stakeholder-requirements-gathering in your project. Claude Code loads it when a task matches its description.

How do I install Stakeholder Requirements Gathering in Codex?

Run `npx skills add nimrodfisher/data-analytics-skills --skill stakeholder-requirements-gathering -a codex`. Or copy the skill folder (05-stakeholder-communication/stakeholder-requirements-gathering in nimrodfisher/data-analytics-skills) into .agents/skills/stakeholder-requirements-gathering in your project. Codex loads it when a task matches its description.

Can I use Stakeholder Requirements Gathering in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nimrodfisher/data-analytics-skills --skill stakeholder-requirements-gathering -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stakeholder-requirements-gathering, .gemini/skills/stakeholder-requirements-gathering, .github/skills/stakeholder-requirements-gathering and .opencode/skills/stakeholder-requirements-gathering in your project.

What does Stakeholder Requirements Gathering need to run?

SKILL.md names no scripts, command-line tools or credentials: Stakeholder Requirements Gathering is instructions for the agent only.

Does Stakeholder Requirements Gathering access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Stakeholder Requirements Gathering safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Stakeholder Requirements Gathering use?

Stakeholder Requirements Gathering is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Stakeholder Requirements Gathering use?

About 513 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.9k tokens, read only when the agent opens those files.

What are the alternatives to Stakeholder Requirements Gathering?

Skills that share tags, products or a category with Stakeholder Requirements Gathering: Extracting Requirements (prime-radiant-inc/iterative-development, 181 stars), Feature Forge (Jeffallan/claude-skills, 12k stars), Specification (citypaul/.dotfiles, 740 stars) and Find Gaps (citypaul/.dotfiles, 740 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stakeholder Requirements Gathering?

nimrodfisher (a GitHub user) maintains it in nimrodfisher/data-analytics-skills, which has 470 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on September 25, 2026.

Source: nimrodfisher/data-analytics-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.