product-requirements

Gather, analyze, and document product requirements into PRD files.

3|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/xingranya/CervixDetectAI --skill product-requirements-xingranya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-requirements
Source: https://github.com/xingranya/CervixDetectAI/tree/main/.agent/skills/product-requirements
Command: npx skills add https://github.com/xingranya/CervixDetectAI --skill product-requirements-xingranya

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill transforms vague user requests into clear, actionable Product Requirements Documents (PRDs) by guiding users through a structured, quality-driven process.

Core Features & Use Cases

  • Interactive Requirements Gathering: Engages in dialogue to understand project context and feature needs.
  • Quality Scoring: Assesses requirements against business value, functionality, UX, technical constraints, and scope using a 100-point system.
  • Iterative Refinement: Asks targeted questions to improve requirements until a 90+ quality score is achieved.
  • PRD Generation: Creates professional PRD documents saved to docs/{feature-name}-prd.md.
  • Use Case: A startup founder has a new app idea but struggles to articulate it for developers. They use this Skill to define user stories, acceptance criteria, and technical specifications, resulting in a comprehensive PRD.

Quick Start

Use the product-requirements skill to help define requirements 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 create a PRD from a vague app idea?

The Skill generates a professional PRD by engaging in interactive dialogue to gather context, defining user stories, acceptance criteria, and technical specifications. It iteratively refines product requirements through targeted questions until achieving a 90+ quality score.

What is the best way to write testable feature specifications?

Writing testable feature specifications requires a 100-point quality assessment system evaluating business value, functionality, UX, technical constraints, and scope. This Skill iteratively refines product requirements through targeted questions until achieving a 90+ quality score.

Can I use this for agile requirements gathering as a product owner?

Yes, product owners can use this for agile requirements gathering. It supports interactive dialogue to capture project context and feature needs, producing clear, testable product requirements documents suitable for agile development workflows.

How does interactive dialogue improve product requirements documents?

Interactive dialogue improves product requirements documents by asking targeted questions to clarify vague requests and refine feature specifications. This iterative process continues until the PRD achieves a 90+ quality score on the 100-point assessment system.

What format are the generated product requirements documents saved in?

Generated product requirements documents are saved as markdown files. The Skill outputs finalized feature specifications to a local file path named docs/{feature-name}-prd.md, ensuring professional PRD documents are properly organized and accessible.