skills.rest
Ocean326
Ocean326COMMUNITY
Explore all skills by this author →
GitHub

product-requirements

Convert feature ideas into PRDs with interactive gathering and quality scoring.

Updated Apr 23, 2026
Search Tags:#documentation#requirements#stakeholder-alignment#product-owner#prd-generation#interactive-dialogue#quality-scoring
One-click install
npx skills add https://github.com/Ocean326/Agents --skill product-requirements-ocean326
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-requirements
Source: https://github.com/Ocean326/Agents/tree/main/skills/global/product-requirements
Command: npx skills add https://github.com/Ocean326/Agents --skill product-requirements-ocean326

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to convert vague feature ideas into clear, testable requirements and formal PRDs; this skill provides a structured, interactive process to produce high-quality documentation.

Core Features & Use Cases

  • Interactive requirements gathering: elicits context, assumptions, success criteria, and edge cases from stakeholders.
  • Quality scoring: evaluates requirements across business value, functionality, UX, technical constraints, and scope, triggering PRD generation at 90+.
  • PRD generation: outputs a professional PRD saved to docs/{feature-name}-prd.md, including executive summary, user stories, acceptance criteria, MVP scope, risks, and dependencies.

Quick Start

Start a requirements-gathering session to turn a feature idea into a polished PRD.

Frequently Asked Questions about product-requirements

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

FAQPage Schema
How do I turn vague feature ideas into a professional PRD?▼

PRD generation is triggered once the interactive requirements gathering process achieves a 90+ score on a 100-point quality rubric, evaluating business value, functionality, UX, and technical constraints to ensure testable requirements.

How do I structure product requirements with user stories and acceptance criteria?▼

You can structure product requirements by using this skill to output a PRD saved to docs/{feature-name}-prd.md, which explicitly includes an executive summary, user stories, acceptance criteria, MVP scope, risks, and dependencies.

Can I use interactive dialogue to align stakeholders on product requirements?▼

Yes, you can use interactive dialogue to align stakeholders on product requirements by iteratively answering targeted questions that extract success criteria and edge cases, dynamically scoring requirement quality before finalizing the PRD.

What is the best way to evaluate the quality of gathered product requirements?▼

The best way to evaluate gathered product requirements is applying a 100-point quality scoring rubric across business value, functionality, UX, technical constraints, and scope to measure completeness before PRD generation.

Does PRD generation work with existing project files for context?▼

Yes, PRD generation works with existing project files by guiding contextual reading of those files alongside iterative clarification to ensure the final output accurately reflects project constraints and milestones.

Related Skills

Explore More Product & Management Skills→
NagyViktNagyVikt
2

brainstorming

Transform abstract project ideas into validated design specifications through iterative dialogue.

Community
Advanced
ripabakripabak

breakdown-feature-prd

Generate structured PRD documents from Epic summaries for engineering teams.

Community
Advanced
kelleysd-appskelleysd-apps
1

sdd-specification

Create detailed feature specifications with user stories and acceptance criteria.

Community
Basic
hangeaiagenthangeaiagent

agentpit-prd

Draft AgentPit PRD workflows through interactive dialogue and update state.json.

Community
Advanced