skills.rest
AZANIR
AZANIRCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-requirements-generator

Extract and normalize software requirements into ISO/IEC/IEEE 29148-compliant SRS documents.

2|2|Updated Mar 7, 2026
Search Tags:#code analysis#documentation#specification#requirements#user stories#Figma#ISO 29148
One-click install
npx skills add https://github.com/AZANIR/qa-skills --skill qa-requirements-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-requirements-generator
Source: https://github.com/AZANIR/qa-skills/tree/main/.cursor/skills/qa-requirements-generator
Command: npx skills add https://github.com/AZANIR/qa-skills --skill qa-requirements-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the extraction and normalization of requirements from diverse sources, ensuring structured and compliant documentation.

Core Features & Use Cases

  • Multi-Source Extraction: Gathers requirements from URLs, Figma designs, codebases, or plain text descriptions.
  • ISO 29148 Compliance: Generates documents adhering to the ISO/IEC/IEEE 29148 standard for Software Requirements Specifications.
  • Use Case: Kickstart a new project by feeding the Skill a link to the product's Figma designs and a brief description, receiving a fully structured SRS document ready for review.

Quick Start

Use the qa-requirements-generator skill to extract requirements from the provided URL.

Frequently Asked Questions about qa-requirements-generator

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

FAQPage Schema
How do I generate software requirements from Figma designs?▼

Generate an ISO 29148 compliant Software Requirements Specification (SRS) by processing input sources like URLs, Figma designs, codebases, or text descriptions through the extraction tool. It structures diverse inputs into formal documentation with IDs, priorities, and acceptance criteria.

Can I extract user stories directly from a code repository?▼

Yes, the generator supports multi-source extraction, allowing you to pull and normalize requirements directly from code repositories. It analyzes the codebase to produce formal user stories and software requirements structured with IDs and acceptance criteria.

What is the best way to structure requirements using the ISO 29148 standard?▼

Structure requirements using the ISO 29148 standard by processing raw inputs through an automated normalization tool that outputs a compliant SRS document. This ensures every extracted requirement includes standardized IDs, priority rankings, and verifiable acceptance criteria.

Does the requirements generator work with natural language descriptions?▼

Yes, the requirements generator works with natural language descriptions by parsing plain text inputs to extract and formalize software requirements. This sub-mode translates unstructured briefs into a structured SRS document complete with IDs and acceptance criteria.

How do I extract specifications from a URL for a new project?▼

Extract specifications from a URL by feeding the link to the requirements generator, which analyzes the web source and outputs a structured SRS document. This process normalizes online content into formal software requirements with IDs, priorities, and acceptance criteria.

Related Skills

Explore More Product & Management Skills→
hoshiyar-singh8hoshiyar-singh8

figma-analysis

Parses Figma URLs and generates design-context diffs with token mappings and ASCII layouts.

Community
Intermediate
TykoDevTykoDev
9

researcher

Convert raw user input into an RFC 2119-prioritized SRS with acceptance criteria.

Community
Advanced
ggombeeggombee
13

start

Automate code development workflows from requirements analysis to deployment.

Community
Advanced
aberrantCodeaberrantCode
1

reinit

Archive legacy plans and tasks while normalizing feature specifications to a standard template.

Community
Intermediate