PRD Writer

$1.99Official

Use when a rough feature idea or request needs to become a complete, testable PRD with scoped requirements, success metrics, and open questions.

productprdrequirementsproduct-managementspecificationplanningdocumentationยท by SkillingMain

What you get

  • โœ“10-step procedure
  • โœ“1 ready-to-run code block
  • โœ“9-point quality checklist
  • โœ“8 pitfalls to avoid
  • โœ“Installs into 6 tools
Version
v1 โ†’
Last updated
today
Length
5 min read
Requires
Works with any modern AI assistant

Works in: Claude Code, Codex, Cline, opencode, OpenClaw, Hermes

Preview

When to use

Use this skill when the user provides a rough product idea, feature request, or problem statement and needs a complete product requirements document. Trigger on requests like 'write a PRD for...', 'spec this out', 'turn this idea into requirements', or when the user pastes meeting notes or a chat thread describing a feature to build.

Do not use for pure technical design docs (architecture, schema design) or for trivial changes that need only a ticket. If the scope is under roughly three requirements, offer a lightweight ticket instead.

Inputs to gather

Collect these before drafting. Ask for missing items in one batched message, maximum five questions. If the user cannot

โ€ฆ

๐Ÿ”’ Buy once ($1.99) to unlock the full playbook, download it, and install it in every tool you use.