to-prd

name	to-prd
description	Convert conversation, idea, or feature request into a concise product requirements document. Use when user asks for PRD, spec, requirements, scope, acceptance criteria, or product plan.

Skill: To PRD

Use this skill to turn ambiguous product intent into implementable requirements.

PRD Shape

• Problem: user pain and why now.
• Goal: measurable outcome.
• Non-goals: explicit exclusions.
• Users: primary actors.
• Scope: must-have behavior only.
• Acceptance criteria: testable bullets.
• Risks: technical, product, security, migration.
• Open questions: only blockers to execution.

Rules

• Do not invent business facts.
• Keep PRD short enough to become an issue.
• Separate product requirements from implementation guesses.
• If user wants execution, convert PRD into vertical slices next.