| name | cy-create-prd |
| description | Creates a Product Requirements Document through interactive brainstorming with parallel codebase and web research. Use when starting a new feature or product, building a PRD, or brainstorming requirements. Do not use for technical specifications, task breakdowns, or code implementation. |
| argument-hint | [feature-name-or-idea] [idea-file] |
Create PRD
Create a business-focused Product Requirements Document through structured brainstorming.
Do NOT skip the research phase — every PRD MUST be enriched with codebase and market context.
Do NOT skip the clarifying questions — the user MUST participate in shaping the PRD before it is written.
Do NOT present multiple approaches for selection or a draft for approval. Once the clarifying questions are answered and the ADRs are recorded, write the PRD file directly. The user reviews the generated file and requests changes afterward if needed.
This applies to EVERY PRD regardless of perceived simplicity.
Asking Questions
When this skill instructs you to ask the user a question, you MUST use your runtime's dedicated interactive question tool — the tool or function that presents a question to the user and pauses execution until the user responds. Do not output questions as plain assistant text and continue generating; always use the mechanism that blocks until the user has answered.
If your runtime does not provide such a tool, present the question as your complete message and stop generating. Do not answer your own question or proceed without user input.
Anti-Pattern: "This Feature Is Too Simple For Full Brainstorming"
Every PRD goes through the full brainstorming process. A single button, a minor workflow tweak, a configuration option — all of them. "Simple" features are where unexamined business assumptions cause the most rework. The brainstorming can be brief for genuinely simple features, but you MUST ask clarifying questions before writing the artifact.
