requirements-analysis

Convert vague product ideas into structured requirements documents with acceptance criteria.

23|2|Updated May 27, 2026

Search Tags:#scoping #requirements #discovery #edge-cases #acceptance-criteria #feature-requests #product-ideas

Ready to run

npx skills add https://github.com/zhouguoqing/QianYuan.AIAgenticFramework --skill requirements-analysis-zhouguoqing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/zhouguoqing/QianYuan.AIAgenticFramework/tree/main/samples/skills/requirements-analysis
Command: npx skills add https://github.com/zhouguoqing/QianYuan.AIAgenticFramework --skill requirements-analysis-zhouguoqing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague product ideas into precise, actionable requirements, ensuring alignment between stakeholders and the development team, reducing rework and delays.

Core Features & Use Cases

Converts input into structured requirements documents with goals, success criteria, assumptions, dependencies, and non-goals.
Generates acceptance criteria that are testable and traceable to user stories.
Supports discovery-to-handoff workflows, including scoping, risk identification, and explicit exclusions.

Quick Start

Turn a vague product idea into a clear requirements, acceptance criteria, and edge cases for a specific feature request.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema

How do I turn vague product ideas into clear, testable requirements?▼

You can turn vague product ideas into testable requirements by generating a formal document that captures goals, success metrics, acceptance criteria, edge cases, risks, dependencies, and explicit non-goals.

How do I write testable acceptance criteria for ambiguous business needs?▼

Writing testable acceptance criteria for ambiguous business needs involves scoping the request to identify edge cases and trace user stories, ensuring alignment between stakeholders and the development team to reduce rework.

What is scoping in product discovery and how does it handle edge cases?▼

Scoping in product discovery is the process of framing ambiguous business needs to define explicit non-goals and identify edge cases, producing a structured requirements document for the development team.

Can I use this to generate a formal requirements document from feature requests?▼

Yes, you can generate a formal requirements document from feature requests by applying discovery and framing workflows to produce goals, success metrics, assumptions, dependencies, and testable acceptance criteria.

What is the best way to identify risks and assumptions for product ideas?▼

The best way to identify risks and assumptions for product ideas is through structured scoping workflows that transform vague inputs into a formal requirements document detailing explicit dependencies and non-goals.