mentat-prd

To generate a PRD from conversation context, use the /generate-prd command which converts the current discussion and codebase knowledge into a structured Product Requirements Document. The Skill uses a standardized template to ensure comprehensive PRD structure and publishes it directly to the issue tracker.

Yes, you can publish a Product Requirements Document directly to your project issue tracker. This Skill takes the current conversation context, converts it into a PRD using a standardized template, and posts it to the issue tracker for immediate review and collaboration.

The best way to create a PRD from ongoing feature discussions is to leverage context-aware generation. This approach uses the existing conversation context and your codebase vocabulary to automatically outline the scope of a new feature or improvement into a structured document.

No, you do not need user interviews to create a PRD using this approach. The generation process leverages pre-existing knowledge from the current conversation context and codebase understanding, explicitly excluding user interviews from its scope.

Yes, PRD generation from conversation context requires access to the codebase. Understanding the codebase vocabulary is necessary to accurately convert ongoing discussions and pre-existing knowledge into a relevant Product Requirements Document.