PRD Writing

Purpose

Creates lightweight, actionable Product Requirements Documents that bridge product and engineering, focusing on user value rather than implementation details.

When NOT to Use This Skill

• Technical implementation planning (use sparc-planning instead)
• API documentation (use api-doc-writer instead)
• Bug fixes or minor enhancements (no PRD needed)
• Already have detailed PRD, need review (use prd-reviewing instead)
• Single feature detail with edge cases (use feature-spec-writing instead)

Workflow

Step 1: Context Gathering

Invoke check-history to understand project context, then ask clarifying questions: