cy-create-prd

To create a product requirements document from a feature idea, use an interactive brainstorming workflow that combines codebase discovery and market research to define user needs, goals, and phased rollout plans.

Writing a business-focused PRD without technical drift requires an interactive workflow that enforces parallel context gathering, producing an MVP-oriented document with clear goals, user stories, and success metrics.

Yes, you can generate user stories and rollout plans by running parallel codebase exploration alongside web research, grounding the product requirements in actual project architecture and market needs.

Interactive brainstorming for product requirements guides you through decision points sequentially, gathering context and generating a full draft for your review, then iterating until you explicitly approve the final artifact.

You need ADR decision records in a PRD when outlining a multi-phase workflow, as they provide referenced architectural context that aligns business goals with technical constraints before implementation begins.

A limitation when generating a PRD is that the workflow requires user approval before saving the final artifact, and the output is strictly an English document following a canonical template with required sections.