prd

Generate a structured Product Requirements Document and save it to /tasks/prd-[feature-name].md.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/davzucky/iceberg-explorer --skill prd-davzucky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/davzucky/iceberg-explorer/tree/main/.opencode/skill/prd
Command: npx skills add https://github.com/davzucky/iceberg-explorer --skill prd-davzucky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate detailed, actionable Product Requirements Documents that align teams and accelerate feature delivery.

Core Features & Use Cases

  • Automated PRD structure with sections for Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design/Technical considerations, Success Metrics, and Open Questions.
  • Guided interview-style clarifications to resolve ambiguity and produce precise acceptance criteria.
  • Save the generated PRD to /tasks/prd-[feature-name].md for traceability and handoff.

Quick Start

Describe a feature and run the PRD generator to produce a complete document saved 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 for a new feature?

To generate a product requirements document, describe your feature and the tool guides you through goals, user stories, and acceptance criteria, saving the final output to /tasks/prd-[feature-name].md.

What sections should a feature definition PRD include for engineering alignment?

A feature definition PRD should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design and Technical Considerations, and Success Metrics to align product and engineering teams.

How do I write precise user stories and acceptance criteria for project kickoffs?

To write precise user stories and acceptance criteria, use a guided interview-style clarification process that resolves ambiguity and translates stakeholder goals into actionable project kickoff requirements.

Can I explicitly define non-goals and scope boundaries in my product management planning?

Yes, you can explicitly define non-goals and scope boundaries in product management planning by structuring your feature proposal with dedicated Non-Goals and Functional Requirements sections.

What is the best way to document success metrics and design considerations for feature proposals?

The best way to document success metrics and design considerations is to use a structured PRD template that separates these sections, ensuring clear traceability and actionable handoff for design teams.