requirements-analysis

Name: requirements-analysis
Availability: InStock
Author: xmx0632

Analyze business requirements and create a software requirements specification.

1|Updated Jan 26, 2026

Search Tags:#documentation #requirements #analysis #user-stories #acceptance-criteria #stakeholders

Ready to run

npx skills add https://github.com/xmx0632/claude-code-demo --skill requirements-analysis-xmx0632

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/xmx0632/claude-code-demo/tree/main/SDLC-Framework/01-requirements-analysis
Command: npx skills add https://github.com/xmx0632/claude-code-demo --skill requirements-analysis-xmx0632

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill guides teams through collecting, analyzing, and documenting requirements to ensure clarity, completeness, and verifiability for successful outcomes.

Core Features & Use Cases

Structured requirements gathering and stakeholder mapping.
Documentation of user stories, acceptance criteria, and traceability templates.
Templates and guidance to support SDLC-aligned analysis across project lifecycles.

Quick Start

Provide a complete requirements analysis for a new project by outlining business goals, stakeholders, and acceptance criteria.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema

What is requirements analysis and when do I need to document user stories and acceptance criteria?▼

To write acceptance criteria for a software requirements specification, document functional and non-functional needs alongside stakeholder mapping and user stories. This ensures completeness and verifiability for successful project outcomes.

How do I map stakeholders and capture business goals during requirements gathering?▼

You can use this Skill to guide requirements gathering and stakeholder mapping, capturing business goals and functional needs to produce a comprehensive software requirements specification with traceability templates.

Does this requirements analysis approach work for both new projects and feature additions?▼

Yes, this approach supports SDLC-aligned analysis across project lifecycles, guiding requirements gathering and documentation for new projects, feature additions, and requirement changes to maintain clarity and verifiability.

What's the best way to structure a software requirements specification with traceability templates?▼

The best way is to use SDLC-aligned templates that capture functional and non-functional needs, user stories, acceptance criteria, and traceability, ensuring your software requirements specification remains clear and verifiable across the project lifecycle.

What limitations exist when documenting non-functional requirements and validation templates?▼

Limitations include relying on accurate stakeholder input and business goals during discovery. Without complete stakeholder mapping, the validation templates and traceability documentation may not fully capture functional and non-functional requirements.