Product Prd

Use to write or refine a PRD after product demand is reasonably understood and before acceptance criteria, design handoff, engineering breakdown, or implementation planning. Use when the user asks for a PRD, product requirements document, scope definition, engineering-ready requirements, requirements handoff, goals and success metrics, functional requirements, non-functional needs, dependencies, risks, milestones, or open questions.

Orkas-AI Updated 9.4k repo stars

File contents

orkas-ai/orkas-awesome-agentskills commit fb1e555b96

Frequently asked questions

npx get-skill add orkas-ai/product-prd