prd

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

420|65|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/CoWork-OS/CoWork-OS --skill prd-cowork-os
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd
Source: https://github.com/CoWork-OS/CoWork-OS/tree/main/resources/skills/prd
Command: npx skills add https://github.com/CoWork-OS/CoWork-OS --skill prd-cowork-os

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates structured PRDs from feature ideas, clarifying scope, objectives, and handoff details for teams.

Core Features & Use Cases

  • Structured PRD generation: Converts a feature prompt into a comprehensive PRD with goals, user stories, acceptance criteria, and technical considerations.
  • Clarifying questions: Interactively asks 3-5 essential questions to resolve ambiguity before writing.
  • Output ready for handoff: Produces a ready-to-save PRD at tasks/prd-[feature-name].md.

Quick Start

Provide a feature prompt and the skill will generate a complete 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 idea?

To write a product requirements document (PRD), provide a feature prompt and the skill will generate a structured PRD. It interactively asks 3-5 clarifying questions to resolve ambiguity before outputting a ready-to-save document at tasks/prd-[feature-name].md.

What sections should be included in a standard PRD for user stories and acceptance criteria?

A standard PRD includes Introduction, Goals, User Stories with acceptance criteria, Functional Requirements, Non-Goals, Design/Technical Considerations, Success Metrics, and Open Questions. This structure guides cross-functional teams through feature planning and requirement clarifications.

Can I generate a PRD automatically for new product initiatives?

Yes, you can automatically generate a PRD for new product initiatives by providing a feature description. The skill converts your prompt into a comprehensive document with goals, user stories, acceptance criteria, and technical considerations for team handoff.

What is the best way to clarify scope and objectives before writing a PRD?

The best way to clarify scope and objectives before writing a PRD is through interactive clarifying questions. The skill asks 3-5 essential questions about your feature idea to resolve ambiguity, ensuring the final document accurately captures the intended functionality and handoff details.

How to define functional requirements and non-goals for a feature planning document?

To define functional requirements and non-goals for feature planning, input your feature description and the skill will structure them into the PRD. It separates what needs to be built from out-of-scope items, alongside success metrics and technical considerations.