skills.rest
Alteriom
AlteriomOFFICIAL
Explore all skills by this author →
WebsiteGitHub

requirements-analysis

Analyze and document software requirements using IEEE 830 and BABOK standards.

Updated Apr 14, 2026
Search Tags:#documentation#requirements#analysis#traceability#stakeholders#ieee-830#babok
One-click install
npx skills add https://github.com/Alteriom/ai-dev-skills --skill requirements-analysis-alteriom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/Alteriom/ai-dev-skills/tree/main/skills/requirements-analysis
Command: npx skills add https://github.com/Alteriom/ai-dev-skills --skill requirements-analysis-alteriom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gather, analyze, and validate software requirements using structured methodologies (IEEE 830 and BABOK), ensuring clear, complete specifications.

Core Features & Use Cases

  • Structured elicitation templates and stakeholder analysis guidance to surface needs.
  • IEEE 830 / BABOK-aligned documentation of functional and non-functional requirements, with acceptance criteria and traceability.
  • User story mapping and traceability patterns to align requirements with releases and design.

Quick Start

Draft a complete IEEE 830 and BABOK-compliant Software Requirements Specification from initial stakeholder notes.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema
How do I write a software requirements specification using IEEE 830?▼

Apply IEEE 830 and BABOK standards to structure your software requirements specification, covering functional, non-functional, and stakeholder requirements with acceptance criteria.

What is requirements traceability and how does it work in software analysis?▼

Requirements traceability tracks requirements across projects and teams by mapping user stories to releases and design artifacts, ensuring alignment throughout the software lifecycle.

How do I document non-functional requirements with acceptance criteria?▼

Document non-functional requirements by applying BABOK-aligned templates that specify acceptance criteria and traceability artifacts, ensuring validation against stakeholder needs.

Can I use BABOK elicitation techniques for stakeholder analysis?▼

Yes, you can use BABOK elicitation templates and stakeholder analysis guidance to surface needs, prioritize requirements, and align them with project releases and design.

What's the best way to map user stories to software requirements?▼

The best way to map user stories is applying user story mapping and traceability patterns that align stakeholder needs with releases, design, and acceptance criteria.

Does requirements analysis work for cross-team software projects?▼

Yes, requirements analysis applies elicitation, prioritization, documentation, and traceability techniques across projects and teams to maintain reliable software specifications.

Related Skills

Explore More Product & Management Skills→
noelserdnanoelserdna

requirements-engineer

Document and validate software requirements into a structured REQUIREMENTS.md using SWEBOK v4 and EARS-style statements.

Community
Basic
DangQuangSEDangQuangSE
19

sr-validate

Validate SRS files for IEEE 830-1998 compliance with automatic error correction.

Community
Advanced
shwilliamsonshwilliamson

github-issues

Create structured GitHub issues with acceptance criteria, dependencies, and milestones.

Community
Basic
DangQuangSEDangQuangSE
19

cl:srs

Generates IEEE 830 SRS documents from raw software requirements via a 7-step pipeline.

Community
Advanced