prd

Name: prd
Availability: InStock
Author: Suwandre

Generate a structured Product Requirements Document from a feature concept.

Updated Apr 26, 2026

Search Tags:#planning #templates #documentation #requirements #prd #product-management #clarifying-questions

Ready to run

npx skills add https://github.com/suwandre/my-opencode-config --skill prd-suwandre

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD generation helps product teams convert vague feature ideas into concrete, testable requirements, reducing ambiguity and aligning stakeholders across disciplines.

Core Features & Use Cases

Generate a complete PRD with structured sections such as Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics.
Ask clarifying questions to resolve ambiguities and capture decisions early in the process.
Save the generated PRD to tasks/prd-[feature-name].md for easy tracking and versioning.
Applicable scenarios: planning a new feature, scoping a project, or aligning teams on expectations and acceptance criteria.

Quick Start

Provide a feature prompt and the skill will generate a structured PRD 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 write a product requirements document from a feature concept?▼

To write a product requirements document from a feature concept, provide a feature prompt and the skill generates a structured PRD with goals, user stories, functional requirements, success metrics, and testable acceptance criteria.

What sections should be included in a PRD for software development?▼

A PRD for software development should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design considerations, Technical Considerations, Success Metrics, and Open Questions to ensure actionable and testable requirements.

How do I define testable acceptance criteria for user stories?▼

To define testable acceptance criteria for user stories, the generated PRD applies clarifying questions to resolve ambiguities early, ensuring each user story has clearly defined and actionable acceptance criteria for stakeholder alignment.

What is the best way to document non-goals and success metrics for a new feature?▼

The best way to document non-goals and success metrics for a new feature is to use a structured PRD template, which explicitly separates Non-Goals from Success Metrics to align teams on project scope and measurable expectations.

Can I save a generated PRD as a markdown file for version control tracking?▼

Yes, you can save a generated PRD as a markdown file for version control tracking. The skill automatically saves the document to tasks/prd-[feature-name].md for easy tracking and stakeholder alignment.