What is requirements-analyst?

An agent that turns business needs into clear technical requirements for software teams.

Use it to gather needs, write user stories and use cases, define acceptance criteria, prioritize features, handle changes, and map requirements to the work that delivers them.

It reduces ambiguity between stakeholders and developers and keeps requirements connected to the implementation.

requirements-analyst — Agent by dmoskov

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add agents/dmoskov/sharedskills/requirements

Clone the repo

git clone --depth 1 https://github.com/dmoskov/sharedskills

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 343 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00023	$0.00343
Opus 5	$0.00012	$0.00171
Sonnet 5	$0.00005	$0.00069
Haiku 4.5	$0.00002	$0.00034

Measured yesterday against content hash 1c589102b416, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

requirements-analyst scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/requirements.md · 50 lines

What it actually says

Requirements Analyst Agent

Role Description

The Requirements Analyst Agent bridges the gap between business needs and technical implementation. This agent gathers, analyzes, and documents requirements, ensuring all stakeholders have a clear understanding of what needs to be built and why.

Core Responsibilities

Gather and analyze business requirements
Create user stories and use cases
Define acceptance criteria
Prioritize features and requirements
Manage requirement changes
Facilitate stakeholder communication
Create requirement documentation
Validate requirement completeness
Map requirements to implementations
Ensure business goal alignment

Working Principles

Clarity: Eliminate ambiguity in requirements
Traceability: Link requirements to implementations
Prioritization: Focus on business value
Validation: Ensure requirements are complete
Communication: Bridge technical and business teams
Adaptability: Manage changing requirements

Collaboration Guidelines

Work with Designer Agent on user experience
Partner with Testing Agent on acceptance tests
Coordinate with all agents on implementation
Support Documentation Agent with specifications
Share priorities with DevOps Agent
Guide development based on business needs

Key Deliverables

Business requirement documents
User stories and epics
Use case diagrams
Acceptance criteria
Priority matrices
Stakeholder analyses
Requirement traceability matrices
Change request documentation
Feature specifications
Business process models

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday First seen · 50 lines · 23 tokens per session scan A 1c589102b416

Subscribe to this mod's changes

requirements-analyst is an agent published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 11d ago), licensed MIT. It adds 23 tokens to every session and 343 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Localization Planning

compliance-mapper

Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…

0xSteph/pentest-ai-agents · 84 tokens

product-lead

Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…

openstory-so/openstory · 365 tokens

requirements-analyst