product-requirements

Convert user requirements into professional PRDs with a 100-point quality score.

Updated Aug 23, 2026

Search Tags:#documentation #requirements #PRD #product-management #quality-score #interactive-dialogue

Ready to run

npx skills add https://github.com/wscffaa/claude-gh-skills --skill product-requirements-wscffaa

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform scattered user needs into organized, testable Product Requirements Documents (PRDs) through interactive dialogue and a 100-point quality scoring system.

Core Features & Use Cases

Interactive requirements gathering: elicits context, constraints, and acceptance criteria from stakeholders.
Quality scoring: performs a 100-point assessment across business value, functional requirements, UX, technical constraints, and scope.
PRD generation: outputs a professional PRD saved to .claude/specs/prd/{feature-name}.md, with an executive summary, user stories, and technical details.
Iterative refinement: prompts for clarifications until a 90+ quality score is reached.

Quick Start

Provide a feature brief and allow the assistant to ask clarifying questions, then proceed to generate a PRD. For example: "Help me write a PRD for a new analytics dashboard feature."

Frequently Asked Questions about product-requirements

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

FAQPage Schema

How do I write a PRD from a feature brief?▼

To write a PRD from a feature brief, provide your initial requirements to start an interactive dialogue. The assistant gathers context, applies a 100-point quality score, and iteratively refines the document until it reaches a 90+ passing score.

How does the interactive requirements gathering process work for software products?▼

Interactive requirements gathering works by prompting targeted clarifications about constraints and acceptance criteria. This mechanism ensures scattered user needs are transformed into organized, testable product requirements documents through iterative dialogue.

Can I generate a product requirements document without providing all the technical details upfront?▼

Yes, you can generate a PRD without upfront technical details. The assistant elicits necessary context, business value, and technical constraints during the interactive dialogue, prompting for clarifications until the requirements meet the quality threshold.

What is the 100-point quality score in product management documentation?▼

The 100-point quality score is an assessment mechanism evaluating business value, functional requirements, UX, technical constraints, and scope. It measures PRD completeness, triggering targeted clarifications until the document achieves a 90+ passing score.

Where are the generated PRD files saved in my project directory?▼

Generated PRD files are saved directly to your project directory at `.claude/specs/prd/{feature-name}.md`. This output includes an executive summary, user stories, and technical details formatted as a professional markdown document.

What's the best way to turn scattered user needs into testable acceptance criteria?▼

The best way to turn scattered user needs into testable acceptance criteria is using an iterative quality assessment workflow. This approach evaluates functional requirements and scope, prompting for targeted clarifications to refine constraints into a professional PRD.