skills.rest
Mte90
Mte90COMMUNITY
Explore all skills by this author →
Website𝕏@mte90netGitHub

Product Requirements

Draft Product Requirements Documents through a structured Q&A process.

51|6|Updated Mar 28, 2019
Search Tags:#documentation#requirements#product management#discovery#feature specification#prd
One-click install
npx skills add https://github.com/Mte90/dotfiles --skill product-requirements-mte90
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Product Requirements
Source: https://github.com/Mte90/dotfiles/tree/main/.config/opencode/skills/common/product-requirements
Command: npx skills add https://github.com/Mte90/dotfiles --skill product-requirements-mte90

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 all necessary information is captured before development begins.

Core Features & Use Cases

  • Iterative Discovery: Engages in a question-and-answer process to uncover all necessary details.
  • PRD Drafting: Utilizes a template to generate a structured PRD.
  • Verification: Includes a checklist to ensure the PRD meets all critical criteria.
  • Use Case: A product manager needs to define a new feature. They use this Skill to ask clarifying questions, identify gaps, and then generate a formal PRD based on the gathered information.

Quick Start

Use the product requirements skill to create a new PRD for the user profile 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 critical requirements?▼

A Product Requirements Document captures feature specifications, technical constraints, and functional requirements. It is needed when defining new features to ensure all stakeholders understand the scope and constraints before development begins.

How do I gather product management requirements through an iterative discovery process?▼

Start drafting your PRD by engaging in a structured Q&A process to iteratively discover necessary details. The Skill guides you through clarifying questions to identify gaps, then generates a formal document using predefined templates and verification checklists.

Can I use a template to ensure my product requirements documentation meets verification criteria?▼

No specific technical prerequisites are needed to gather requirements. The Skill facilitates the iterative discovery process directly, guiding you through structured Q&A to define feature specifications and identify technical constraints.

What is the best way to identify technical constraints when writing feature specifications?▼

Unlike standard blank-page drafting, this approach uses iterative Q&A to actively uncover missing details and identify technical constraints. It then applies predefined templates and verification checklists to ensure comprehensive output.

Does product requirements discovery work for both functional and non-functional requirements?▼

If your PRD lacks critical details, use the built-in verification checklist to validate completeness. The iterative Q&A process also helps identify gaps in feature specifications before generating the final document.

Related Skills

Explore More Product & Management Skills→
AcendasAcendas
2

ship-discuss

Guides feature discovery conversations from vague ideas to structured plans and specs.

Official
Advanced
Ni-BuNi-Bu
4

prd-to-slices

Break PRDs into ordered vertical slices with linked Obsidian notes.

Community
Advanced
hdtinh57hdtinh57
1

planning

Coordinate backlog planning and architecture decisions across product and technical domains.

Community
Advanced
nschneblenschneble

refine-specification

Refine draft feature specifications through targeted clarifying questions.

Community
Advanced