Product Requirements

Draft Product Requirements Documents through structured inquiry and templated outputs.

Updated Mar 7, 2026

Search Tags:#product management #discovery #feature specification #requirements gathering #prd #product requirements

Ready to run

npx skills add https://github.com/ntluong95/agent-skills-statistics --skill product-requirements-ntluong95

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Product Requirements
Source: https://github.com/ntluong95/agent-skills-statistics/tree/main/.github/skills/common/product-requirements
Command: npx skills add https://github.com/ntluong95/agent-skills-statistics --skill product-requirements-ntluong95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of gathering requirements and drafting Product Requirements Documents (PRDs), ensuring clarity and completeness before development begins.

Core Features & Use Cases

Iterative Discovery: Guides users through a structured questioning process to uncover all necessary details.
PRD Drafting: Utilizes templates to generate well-formatted PRDs.
Verification: Includes checklists to ensure all functional, non-functional, and technical aspects are covered.
Use Case: When starting a new feature, use this Skill to systematically define its purpose, scope, user stories, and technical constraints, resulting in a comprehensive PRD.

Quick Start

Use the Product Requirements skill to start drafting a PRD for a new user authentication feature.

Frequently Asked Questions about Product Requirements

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

FAQPage Schema

How do I draft a PRD for a new feature without missing technical constraints?▼

To draft a PRD without missing constraints, use iterative discovery to define project scope, user stories, acceptance criteria, and technical limitations through structured inquiry and templated outputs.

What is the best way to gather requirements for a feature specification?▼

The best way to gather requirements for a feature specification is using a structured questioning process that uncovers functional, non-functional, and technical aspects to ensure clarity and completeness before development.

How do I structure user stories and acceptance criteria for product management?▼

Structure user stories and acceptance criteria by employing iterative discovery and templated PRD generation, which systematically defines project scope and technical constraints for product management tasks.

Can I use this product requirements approach for any new project scope?▼

Yes, you can use this product requirements approach for any new project scope, as it supports product managers and engineers in defining purpose, user stories, and technical constraints for comprehensive PRD drafting.

Does iterative discovery ensure all functional and non-functional requirements are covered?▼

Yes, iterative discovery ensures functional and non-functional requirements are covered by using verification checklists during the PRD drafting process to validate completeness across all project aspects.