PRD

Generate structured Product Requirements Documents with goals, user stories, and acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kurko/ai-company-os --skill prd-kurko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: PRD
Source: https://github.com/kurko/ai-company-os/tree/main/skills/prd
Command: npx skills add https://github.com/kurko/ai-company-os --skill prd-kurko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRD provides a structured, repeatable way to convert a product vision into clear, testable requirements, reducing ambiguity and rework.

Core Features & Use Cases

  • Structured templates: Predefined sections for context, goals, user stories, acceptance criteria, risks, and success metrics.
  • Traceability: Links to vision and related documents to maintain alignment across teams.
  • Collaborative drafting: Supports iterative reviews with stakeholders and versioned updates.

Quick Start

Fill out the PRD template with your feature name, goals, and acceptance criteria to start the documentation.

Frequently Asked Questions about PRD

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

FAQPage Schema
How do I create a product requirements document from a feature vision?

To create a product requirements document, you translate your feature vision into structured sections including goals, user stories, acceptance criteria, and success metrics, reducing ambiguity and rework across teams.

What is the best way to structure user stories and acceptance criteria for product planning?

The best way to structure user stories and acceptance criteria is using a predefined PRD template that organizes requirements alongside context, risks, and milestones for clear traceability.

Can I draft requirements collaboratively and still maintain alignment with related documents?

Yes, you can collaboratively draft requirements by linking the PRD to vision and related documents, which maintains alignment across teams during iterative stakeholder reviews and versioned updates.

Do I need a predefined template to capture feature goals and success metrics?

You need a predefined template to capture feature goals and success metrics because it ensures your product requirements document includes necessary context, constraints, and milestones for testable specifications.

When do I need to generate a PRD during the product management lifecycle?

You need to generate a PRD during feature discovery and planning phases to translate your product vision into clear, actionable specifications before development begins.