All skills
nimrodfisher avatar

/stakeholder-requirements-gathering

@e4e97c5

Structured requirements elicitation for analysis requests. Use when scoping new analysis projects, clarifying ambiguous business questions, or documenting analysis acceptance criteria with stakeholders.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/stakeholder-requirements-gathering

This session only. Nothing lands on disk.

assetsrequirements_doc_template.md

≈634 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Analysis Requirements Document

Project / request name: [short descriptive title]
Requestor: [name and team]
Primary analyst: [name]
Date created: [YYYY-MM-DD]
Target delivery date: [YYYY-MM-DD]
Status: Draft / Under review / Approved


Business Question

[The single most important question this analysis will answer. Write it as a question, not a task.]

Example: "Which customer segments are at highest risk of churning in the next 90 days, and what is the estimated revenue impact?"


Decision This Informs

Decision type: Strategic / Operational / Tactical
Decider: [name and role]
Decision deadline: [date by which the decision must be made]
What happens if this analysis isn't available: [impact of delay]


Success Criteria

What does "done well" look like? The requestor will accept the output if:

  1. [Criterion 1 — e.g. "Shows churn risk score for each customer in the enterprise tier"]
  2. [Criterion 2 — e.g. "Includes a recommended action for the top 50 at-risk accounts"]
  3. [Criterion 3 — e.g. "Can be exported to CSV for upload into Salesforce"]

Scope

In scope:

  • [What is explicitly included]
  • [Time period, geography, segments, products]

Out of scope:

  • [What is explicitly excluded and why]

Data Sources

Source Table / system Availability confirmed?
[e.g. Customer events] [prod.events] Yes / No / TBC
[e.g. CRM data] [Salesforce export] Yes / No / TBC

Known data quality issues: [any known gaps or reliability concerns]


Output Format

Format: Table / Chart / Dashboard / Report / Slide deck / Email / Number
Delivery channel: [email / Slack / Confluence / presentation]
Audience for the output: [names or roles]
Level of detail required: Executive summary / Business analyst detail / Full technical


Assumptions and Constraints

  • [Any assumption the requestor has already made that the analysis should accept]
  • [Any constraint that affects the approach: timeline, data access, system limitations]

Open Questions

# Question Owner Status
1 [Question that needs resolution before analysis starts] [name] Open

Sign-off

Requestor confirms this document accurately describes the requirement:

Signature: ______________________ Date: __________

Analyst confirms feasibility given current constraints:

Signature: ______________________ Date: __________

Source: SKILL.md on GitHub

No alerts16d4 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    This skill is a collection of static Markdown templates and process documentation for requirements gathering. It contains no executable code, network operations, or automation commands.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at e4e97c5. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 5 days ago.

Activeupdated 5 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/stakeholder-requirements-gathering