skills.rest
crsiebler
crsieblerCOMMUNITY
Explore all skills by this author →
Website𝕏@CorySieblerGitHub

prd

Generate a structured PRD from a feature idea with clarifying questions.

1|Updated Jul 11, 2019
Search Tags:#planning#templates#documentation#requirements#prd#product-management
One-click install
npx skills add https://github.com/crsiebler/dotfiles --skill prd-crsiebler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/crsiebler/dotfiles/tree/main/ai/opencode/skills/prd
Command: npx skills add https://github.com/crsiebler/dotfiles --skill prd-crsiebler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document features quickly by generating a structured PRD from a feature idea, reducing ambiguity and miscommunication in product development.

Core Features & Use Cases

  • Clarifying Questions Workflow: The skill asks 3-5 targeted clarifying questions to disambiguate goals, success criteria, scope, and constraints before drafting the PRD.
  • PRD Structure Generation: Produces a structured PRD with sections like Introduction/Overview, Goals, User Stories (with Acceptance Criteria), Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions.
  • Auto-Save & Versioning: Saves the generated PRD to tasks/prd-[feature-name].md for easy handoff and revision tracking.
  • Reusable Templates: Ensures PRDs follow a consistent, copy-paste friendly template for quick reuse.

Quick Start

Provide a feature description to generate a PRD, and the skill will produce a structured document and save it to tasks/prd-[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 product requirements document from a feature idea?▼

Generating a product requirements document involves providing a feature idea, answering targeted clarifying questions to disambiguate scope, and automatically drafting a structured PRD template with user stories and success metrics.

What sections are included in a standard PRD template for development handoffs?▼

A standard PRD template includes Introduction, Goals, User Stories with Acceptance Criteria, Functional Requirements, Non-Goals, Design Considerations, Technical Considerations, Success Metrics, and Open Questions for clear development handoffs.

Can I use this to create user stories with acceptance criteria for project planning?▼

Yes, you can use this for project planning to create user stories with acceptance criteria, as the generated PRD explicitly includes these sections to reduce ambiguity and miscommunication in product development.

How does the skill handle scope and constraints before drafting the PRD?▼

Before drafting the PRD, the skill asks 3-5 targeted clarifying questions to disambiguate goals, success criteria, scope, and constraints, ensuring the final product requirements document accurately reflects the intended feature.

Where is the generated PRD saved for revision tracking and team access?▼

The generated PRD is auto-saved to tasks/prd-[feature-name].md, providing a markdown file format for easy team access, copy-paste friendly reuse, and straightforward revision tracking.

Related Skills

Explore More Product & Management Skills→
lucidlabs-hqlucidlabs-hq
2

brainstorm

Generate a brainstorm document with questions and options for feature planning.

Official
Advanced
memyselfandmmemyselfandm
8

workshopping-prds

Guide cross-functional teams through multi-phase PRD workshops to produce structured product requirements documents.

Community
Advanced
suwandresuwandre

prd

Generate a structured Product Requirements Document from a feature concept.

Community
Advanced
I-OnlabsI-Onlabs
3

product-manager-toolkit

Prioritize features with RICE scoring and generate PRDs from customer interviews.

Community
Intermediate