product-requirements

Gather product requirements interactively and generate Markdown PRD documents.

2.7k|308|Updated Jul 17, 2025

Search Tags:#documentation #product management #PRD #feature specification #requirements gathering #product requirements

Ready to run

npx skills add https://github.com/stellarlinkco/myclaude --skill product-requirements-stellarlinkco

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: product-requirements
Source: https://github.com/stellarlinkco/myclaude/tree/main/skills/product-requirements
Command: npx skills add https://github.com/stellarlinkco/myclaude --skill product-requirements-stellarlinkco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of gathering, analyzing, and documenting product requirements, ensuring clarity and completeness before development begins.

Core Features & Use Cases

Interactive Requirements Gathering: Engages users in a dialogue to elicit detailed feature specifications.
Quality Scoring: Assesses requirements against business value, functionality, UX, and technical constraints using a 100-point system.
Iterative Refinement: Guides users to improve requirements until a quality threshold (90+) is met.
PRD Generation: Produces professional Product Requirements Documents (PRDs) in Markdown format.
Use Case: A product manager needs to define a new feature for a mobile app. They use this Skill to interactively flesh out user stories, acceptance criteria, and technical considerations, resulting in a well-structured PRD.

Quick Start

Use the product-requirements skill to generate 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 generate a PRD for a new feature specification?▼

To generate a PRD for a new feature specification, engage in an interactive dialogue that gathers detailed requirements and outputs a professional Markdown document. This process systematically evaluates business value, functionality, UX, and technical constraints.

What is the best way to gather product requirements systematically?▼

The best way to gather product requirements systematically is through a structured, quality-scored dialogue that evaluates business value and functional completeness. This ensures requirements are clear, testable, and actionable before development begins.

How does quality scoring work for product requirements?▼

Quality scoring for product requirements works by assessing business value, functional completeness, user experience, and technical constraints using a 100-point system. This iterative refinement guides improvements until the requirement meets a 90+ quality threshold.

Do I need technical knowledge to define clear product requirements?▼

You need basic technical knowledge to define clear product requirements, as the process evaluates technical constraints alongside business value and user experience. The interactive dialogue guides you to flesh out technical considerations and acceptance criteria.

Can I use this to create user stories and acceptance criteria?▼

Yes, you can use this interactive requirements gathering process to create user stories and acceptance criteria. It helps product managers flesh out these details for new features, resulting in a well-structured product requirements document.

What format are product requirements documents output in?▼

Product requirements documents are output in Markdown format. This ensures the generated PRDs are professional, easily readable, and portable for development teams to use directly in their documentation systems.