do-create-prd

To generate a PRD from a feature request, you can use an automated workflow that formalizes requirements into a standardized template. It collects necessary clarifications and outputs a ready-to-use document in a structured directory.

The best way to structure product requirements documentation is by enforcing a standardized directory pattern like ./prds/prd-[feature-slug]/prd.md. This ensures all PRDs are organized consistently for easy review and sharing.

A clarification-driven workflow helps product planning by collecting specific requirements and resolving ambiguities before drafting begins. This ensures the generated PRD accurately maps features to actionable development tasks.

Yes, you can use a template to formalize requirements for your product management team. The Skill applies a standardized PRD template that outputs a consistent document, reducing ambiguity and speeding up planning.

No specific external dependencies are required to automate PRD creation. The Skill operates independently to validate directories, generate the PRD file from a template, and guide the user clarification process.

If your PRD generation workflow is interrupted, the Skill provides guidance for user clarification and resumption. This allows you to continue the requirements gathering and drafting process without losing prior context.