create-prd

To draft a PRD for a new feature, you need to define the scope, user stories, acceptance criteria, and verification plans. Structured templates help capture all necessary details while ensuring the feature scope remains well-defined and manageable.

Feature slicing is the process of breaking down large features into smaller, implementable PRDs based on a defined rubric. You should use it when starting a new feature to ensure the resulting product requirements remain thin, focused, and immediately implementable.

Structuring user stories and acceptance criteria in a PRD involves integrating shaping inputs like briefs, risk registers, and spike investigations without information loss. This ensures all essential sections are captured and the scope is clearly defined for implementation.

Yes, you can integrate risk registers, investigation briefs, and shaping inputs directly into your PRD drafting process. This ensures comprehensive documentation by capturing scope, user stories, and acceptance criteria without losing critical contextual information.

The best way to break down large agile features is by applying a feature slicing rubric to create thin PRDs. This method structures the product requirements into manageable units, incorporating scope, user stories, and verification plans for each slice.