authoring-prd — SKILL.md

Variant: standard · When to use: producing (or amending) a comprehensive PRD from a product idea, to a quality bar the downstream build can be planned from.

Overview

This skill is the how-to of writing a strong, comprehensive Product Requirements Document — the judgment a producer applies, not the section list. It assumes two collaborators: a PRD template tool that supplies the section structure, and a deep-research capability to ground each section in evidence. The producer is handed a product idea (and any upstream context documents) and must elaborate it into a PRD — never emit generic boilerplate. The bar to clear: the finished PRD is plannable — an engineer can derive milestones and tasks from it. The skill is single-sourced with reviewing-prd: the Step-5 self-check IS the reviewer's 12-condition bar, so author and reviewer do not drift.

When to activate

• Authoring a new PRD from a product idea or brief.
• Expanding a thin idea into a comprehensive requirements doc (product or substantial feature).
• Amending an existing PRD as a versioned delta (a new/changed requirement, a scope shift) — see Step 6.
• Filling a PRD template with researched, decision-complete content.

Do NOT activate when: