Product Requirements Document (PRD) Workflow

Start of the Workflow/Process.

Create a new entry in the 'Product Requirements' data model to start the document lifecycle.

Assign a task to the Product Manager to define the problem statement and goals.

Assign a task to the Product Manager to write detailed user stories and acceptance criteria.

Update the status field of the PRD entry to indicate that the drafting phase has begun.

Retrieve all relevant stakeholders from the 'Users' or 'Stakeholders' data model for review assignment.

Create tasks for the retrieved stakeholders to review the draft requirements.

Get all feedback entries linked to the current PRD via the 'Comments' data model.

Aggregate review comments to count the number of 'High Priority' blockers identified.

Execute a formula based on estimated development hours and number of required features to determine project complexity.

Update the PRD entry with the aggregated count of blockers and the calculated complexity score.

Create a high-priority task for the Product Manager to resolve all 'High' severity feedback items.

Update the PRD entry status to 'Approved' once all blockers are resolved.

Send an email to the Engineering Lead containing the link to the approved PRD.

Create a new entry in the 'Epics' data model, automatically populated with data from the PRD.

Create a report summarizing the timeline from drafting to approval for historical tracking.

End of the Workflow/Process.