pm-organization-prd-reorganization

You translate GDD updates and retrospective findings into PRD tasks by extracting requirements and action items, then placing them into prd.json for top priorities or prd_backlog.json for longer-term backlog items.

Managing a PRD backlog from game design documents involves maintaining prd.json with a maximum of five active priority tasks and a separate prd_backlog.json for longer-term items to ensure deterministic backlog management.

Deterministic backlog management works by reorganizing extracted PRD tasks into structured formats, ensuring traceability across GDD changes and retrospectives while maintaining acceptance criteria and task placement across prd.json and prd_backlog.json.

Yes, PRD tasks can be assigned to agents including developers, PMs, and game designers. The system provides guidance and templates for task creation, prioritization, and reassignment to support coordinated execution.

You need to reorganize PRD tasks from retrospectives when translating process improvements, design debt, and game design changes into actionable backlog items during the prd_analysis phase to maintain alignment and traceability.

Yes, PRD reorganization satisfies requirements for structured PRD task creation by generating acceptance criteria and ensuring proper task placement across both prd.json and prd_backlog.json files.