skills.rest
gil0mendes
gil0mendesCOMMUNITY
Explore all skills by this author →
Website𝕏@gil0mendesGitHub

prd

Generates structured, markdown-formatted Product Requirements Documents for feature planning.

Updated Nov 3, 2019
Search Tags:#documentation#technical writing#feature definition#prd#rfc#product requirements
One-click install
npx skills add https://github.com/gil0mendes/dotfiles --skill prd-gil0mendes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/gil0mendes/dotfiles/tree/main/configs/opencode/skill/prd
Command: npx skills add https://github.com/gil0mendes/dotfiles --skill prd-gil0mendes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of comprehensive Product Requirements Documents (PRDs) that clearly define the desired end-state of a feature, ensuring alignment and clarity for engineering, design, and product teams.

Core Features & Use Cases

  • Structured PRD Generation: Creates markdown-formatted PRDs covering problem statements, proposed solutions, end states, success metrics, acceptance criteria, technical context, risks, and alternatives.
  • RFC Readiness: Produces documents suitable for review by Principal Engineers, Designers, and Product Owners.
  • Use Case: When planning a new user authentication system, use this Skill to generate a PRD that details the problem of current login issues, proposes a solution with user flows, defines success metrics like reduced login errors, and outlines technical considerations and risks.

Quick Start

Load the prd skill and create a PRD for the new user profile editing feature.

Frequently Asked Questions about prd

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

FAQPage Schema
How do I create a structured PRD for a feature migration?▼

A PRD for feature planning defines the desired end-state of a feature by detailing the problem statement, proposed solution, success metrics, acceptance criteria, technical context, risks, and alternatives to ensure team alignment.

What sections should be included in a product requirements document for engineering review?▼

A product requirements document for engineering review should include sections for the problem statement, proposed solution, end state, success metrics, acceptance criteria, technical context, risks, and alternatives to facilitate RFC review by stakeholders.

When do I need an RFC format document instead of standard technical writing?▼

You need an RFC format document when planning complex refactors or new features that require formal review by Principal Engineers, Designers, and Product Owners to validate technical context, risks, and proposed alternatives.

How do I define success metrics and acceptance criteria for a new feature definition?▼

Defining success metrics and acceptance criteria for a feature definition involves specifying measurable goals and boundary conditions within the PRD, detailing the exact end state and technical considerations required for stakeholder validation.

Can I use a PRD template for both new feature planning and system refactors?▼

Yes, you can use a PRD template for both new feature planning and system refactors because it structures the problem statement, proposed solution, and technical context to clearly define the desired end state for any engineering migration.

Related Skills

Explore More Product & Management Skills→
korchasakorchasa

write-prd

Generate a Product Requirements Document through a structured question and answer process.

Community
Intermediate
Q00Q00
5.4k

pm

Generate a Product Requirements Document through a guided PM-focused interview.

Community
Advanced
dralgorhythmdralgorhythm
111

writing-prds

Generate Product Requirements Documents with user stories and Given/When/Then acceptance criteria.

Community
Intermediate
HermeticOrmusHermeticOrmus

Proposal Writing Patterns

Generate markdown templates for technical proposal writing with success metrics.

Community
Intermediate