prd

Name: prd
Availability: InStock
Author: rogvid

Generate structured PRDs from feature descriptions and save them to specs/prds.

Updated Mar 9, 2023

Search Tags:#planning #documentation #requirements #prd #product-management #user-stories #acceptance-criteria

Ready to run

npx skills add https://github.com/rogvid/dotfiles --skill prd-rogvid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/rogvid/dotfiles/tree/main/opencode/.config/opencode/skill/prd
Command: npx skills add https://github.com/rogvid/dotfiles --skill prd-rogvid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and scoping for new features can be vague and error-prone. This Skill generates structured, actionable Product Requirements Documents (PRDs) from a feature description to align teams and reduce rework.

Core Features & Use Cases

Collects a feature description and asks clarifying questions to resolve ambiguity.
Produces a complete PRD with sections such as Introduction, Goals, User Stories (with Acceptance Criteria), Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.
Saves the final PRD to specs/prds in kebab-case format: [seq]-[status]-[feature-name].md.

Quick Start

Provide a feature description and it will generate and save a complete PRD to specs/prds/[seq]-[status]-[feature-name].md.

Frequently Asked Questions about prd

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

FAQPage Schema

How do I generate a PRD from a feature description?▼

To generate a PRD, provide a feature description. The Skill asks clarifying questions to resolve ambiguity, then produces a complete document with goals, user stories, and acceptance criteria, saving it to specs/prds.

What sections are included in a structured product requirements document?▼

A structured product requirements document includes Introduction, Goals, User Stories with Acceptance Criteria, Functional Requirements, Non-Goals, Design and Technical Considerations, Success Metrics, and Open Questions.

How do I write user stories with acceptance criteria for feature scoping?▼

Writing user stories with acceptance criteria is handled by providing a feature description. The Skill scopes the feature by generating structured user stories and mapping specific acceptance criteria to each requirement.

Can I automate product launch documentation and save it as a markdown file?▼

Yes, you can automate product launch documentation. The Skill generates the PRD and saves the output automatically as a markdown file in specs/prds using a kebab-case naming convention.

Does this PRD generator ask clarifying questions before writing the document?▼

Yes, the PRD generator asks clarifying questions after receiving the initial feature description. This resolves ambiguity and ensures the final product requirements document aligns with team expectations.

What is the best way to document non-goals and open questions for product planning?▼

The best way to document non-goals and open questions is to generate a structured PRD. This confines project scope by explicitly listing non-goals and tracking open questions for product planning alignment.