requirements-analyst

Convert stakeholder needs into testable requirements and SRS documentation.

Updated Jan 10, 2026

Search Tags:#requirements #user stories #traceability #SRS #EARS

Ready to run

npx skills add https://github.com/Eigo-Mt-Fuji/portfolio-2026 --skill requirements-analyst-eigo-mt-fuji

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-analyst
Source: https://github.com/Eigo-Mt-Fuji/portfolio-2026/tree/main/.claude/skills/requirements-analyst
Command: npx skills add https://github.com/Eigo-Mt-Fuji/portfolio-2026 --skill requirements-analyst-eigo-mt-fuji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Requirements Analyst AI helps teams convert stakeholder needs into precise, testable requirements, and to systematically draft SRS, user stories, and acceptance criteria while maintaining traceability across the project lifecycle.

Core Features & Use Cases

Requirements Elicitation & Definition: Extract stakeholder needs, define functional and non-functional requirements, and produce SRS and acceptance criteria.
EARS-Driven Documentation: Generate requirements in EARS formats (WHEN, WHILE, IF...THEN) for clarity and verifiability.
Document Generation: Automatically generate SRS, functional/non-functional specifications, and user stories with traceability mappings.
Use Case Scenarios: Create and refine user stories and acceptance criteria with Given/When/Then examples.
Steering Guidance: Align outputs with steering files for architecture, tech stack, and business goals.

Quick Start

Run the Requirements Analyst AI to initiate elicitation and generate initial SRS drafts for your project.

Frequently Asked Questions about requirements-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I convert stakeholder needs into testable requirements and SRS documentation?▼

Requirements analysis converts stakeholder needs into precise, testable requirements by extracting functional and non-functional specs, then systematically documenting them in SRS format with traceability mappings. This ensures alignment across elicitation, specification, and documentation phases.

What is EARS format and when should I use it for requirements writing?▼

EARS (Easy Approach to Requirements Syntax) uses structured templates like WHEN, WHILE, and IF...THEN to write requirements with clarity and verifiability. Use EARS when you need unambiguous, testable specifications that reduce interpretation errors across teams.

How do I create user stories and acceptance criteria with traceability?▼

Generate user stories by structuring stakeholder needs as Given/When/Then scenarios paired with acceptance criteria, then map each back to parent requirements and SRS sections. This creates an auditable chain linking business goals to testable outcomes.

Can I align requirements documentation with project architecture and tech stack decisions?▼

Yes, requirements analysis incorporates steering guidance—files defining architecture, tech stack, and business constraints—to ensure SRS, user stories, and acceptance criteria align with project direction and technical feasibility.

What's the difference between functional and non-functional requirements in SRS?▼

Functional requirements specify what the system does (features, behaviors, outputs); non-functional requirements define how it performs (speed, security, scalability, compliance). A complete SRS documents both to ensure the system meets user needs and operational constraints.

Do I need to manually map requirements to user stories or can this be automated?▼

Requirements analysis automates traceability mapping between SRS, user stories, and acceptance criteria, reducing manual documentation work and maintaining consistency. This enables fast iteration while preserving audit trails across the project lifecycle.