skills.rest
lync-cyber
lync-cyberCOMMUNITY
Explore all skills by this author →
GitHub

req-analysis

Break down raw product requirements into structured feature lists and user stories.

133|9|Updated Mar 26, 2026
Search Tags:#requirements#acceptance criteria#prioritization#user stories#prd#product discovery#non-functional requirements
One-click install
npx skills add https://github.com/lync-cyber/CataForge --skill req-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: req-analysis
Source: https://github.com/lync-cyber/CataForge/tree/main/.cataforge/skills/req-analysis
Command: npx skills add https://github.com/lync-cyber/CataForge --skill req-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert vague product ideas or existing PRDs into structured, testable requirements, so teams can align on what to build and how success will be measured.

Core Features & Use Cases

  • Requirement Clarification: Break down ambiguous requests into concrete functional needs and prioritized user stories.
  • Acceptance Criteria Definition: Write verifiable ACs and non-functional requirements for downstream design, engineering, and QA.
  • PRD Structuring: Organize background, goals, constraints, assumptions, and terminology into a complete requirements document.
  • Use Case: A product manager shares a new feature idea and the Skill produces a layered requirements draft with priorities, acceptance criteria, and assumptions for review.

Quick Start

Ask the skill to analyze your product idea and produce a prioritized requirements breakdown with user stories and acceptance criteria.

Frequently Asked Questions about req-analysis

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

FAQPage Schema
How do I turn vague product ideas into structured user stories and acceptance criteria?▼

Writing verifiable acceptance criteria requires breaking down product requests into specific functional needs and non-functional requirements, ensuring the output is testable by downstream design, engineering, and QA teams.

What is the best way to structure a PRD for early-stage product discovery?▼

The best way to structure a PRD for early-stage product discovery is to organize the document into background, goals, constraints, assumptions, and terminology, while producing a layered requirements draft with clear priorities.

How do I define non-functional requirements during scope clarification?▼

Defining non-functional requirements during scope clarification involves translating raw product constraints and assumptions into verifiable conditions that align engineering and QA teams on measurable success criteria.

Does requirement analysis support Chinese-language product discovery workflows?▼

Yes, requirement analysis supports Chinese-language product discovery workflows, allowing teams to validate scope, draft PRDs, and analyze requirement changes in Chinese for downstream engineering and QA teams.

How to analyze requirement changes and align teams on what to build?▼

Analyzing requirement changes involves converting existing PRDs or updated ideas into structured feature lists with prioritized user stories and assumptions, ensuring all teams align on what to build and how success will be measured.

Related Skills

Explore More Product & Management Skills→
avav25avav25
2

feature-design

Convert raw feature ideas into structured PRDs with goals, user stories, and acceptance criteria.

Community
Intermediate
cuiosscuioss
1

cui-requirements

Generate structured requirements documents and technical specifications.

Community
Basic
jikig-aijikig-ai
12

spec-flow-analyzer

Analyze product specs to map user flows, permutations, and gaps.

Official
Advanced
fabio-barbozafabio-barboza
28

do-create-prd

Generate standardized PRDs from feature requests into a PRD directory structure.

Community
Advanced