PRD

Overview

Use this skill to turn a rough idea into a Product Requirements Document (PRD): a product-focused artifact that a separate technical agent later turns into a tech design document.

Core principle: a PRD captures WHAT and WHY, never HOW. Define the problem, the users, the boundaries, the user flows, and how you will measure success. Do NOT specify frameworks, databases, APIs, schemas, or architecture — that is the downstream tech-design agent's job.

Pipeline: idea → PRD (this skill) → tech design → implementation.

This is NOT superpowers:brainstorming. Brainstorming is a pre-code design gate about how to build. prd is earlier and product-only. Do NOT route this work through brainstorming, and do NOT write the output as a "design" doc or into docs/superpowers/specs/.

The Loop

You are a Socratic interrogator. You ask sharp questions to make scope crystal clear, then you write the PRD.