prd

Generate a structured PRD document from a feature prompt.

3|Updated Aug 18, 2025

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

Ready to run

npx skills add https://github.com/rileyseaburg/codetether --skill prd-rileyseaburg

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating vague feature ideas into a comprehensive, actionable PRD is time-consuming and prone to misalignment between teams, leading to delays and rework.

Core Features & Use Cases

Generate goals, scope, and success criteria for a feature.
Create structured User Stories with descriptions and verifiable acceptance criteria.
Produce a complete set of Functional Requirements, Non-Goals, design considerations, and technical considerations.
Use-case: A product manager drafts a feature prompt; the skill outputs a full PRD ready for review.

Quick Start

Provide a clear feature prompt and ask the skill to generate a complete PRD in the prescribed structure.

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 prompt?▼

To generate a PRD, provide a feature prompt and the skill outputs a production-ready PRD document with goals, user stories, functional requirements, and success metrics. It guides you by asking clarifying questions to ensure alignment.

What should be included in a product requirements document?▼

A product requirements document should include Introduction, Goals, User Stories, Functional Requirements, Non-Goals, Design, Technical Considerations, Success Metrics, and Open Questions. The skill automatically structures these sections from your feature prompt.

How do I write user stories with verifiable acceptance criteria?▼

To write user stories with verifiable acceptance criteria, the skill guides junior developers through clarifying questions, ensuring each story has a clear description and testable acceptance criteria before formatting the final PRD output.

Can I save a PRD to markdown for downstream automation?▼

Yes, you can save a PRD to markdown for downstream automation. The skill formats the final output as a human-readable markdown file saved to tasks/prd-[feature-name].md, designed to be easily parsed by downstream automation tools.

What is the best way to define non-goals and success metrics for feature planning?▼

The best way to define non-goals and success metrics for feature planning is to translate vague feature ideas into structured PRD sections. The skill automatically generates these boundaries and criteria to prevent scope creep and misalignment.