prd

You can generate a product requirements document by providing a work item brief to the prd skill, which parses the unstructured text and extracts goals, requirements, and user flows into a standardized PRD attached to the work item.

Automating requirements gathering is done by using the prd skill to convert raw work item descriptions into structured PRDs, streamlining the initial phase of product development and speeding up the documentation process.

Automated PRD generation handles missing information by ensuring all required PRD sections are populated, using placeholders where the input work item brief is insufficient for complete data extraction.

You do not need to manually format the output; the skill uses predefined templates and extraction rules to structure the document and attaches the generated PRD as an artifact to the work item.

You can use project conventions files to provide context for PRD generation, as the skill parses these files alongside the work item brief to accurately structure the product requirements document output.

Limitations of using automation for PRD documentation include relying on the input brief's clarity; while it structures data and uses placeholders for gaps, the generated draft still requires human review and refinement.