Imported from majiayu000/claude-skill-registry (skills/product/pm-organization-prd-reorganization/SKILL.md). Install upstream with npx skills add majiayu000/claude-skill-registry --skill pm-organization-prd-reorganization. Copyright stays with the author.

PRD Reorganization

The PM must translate Game Design Document updates and retrospective findings into actionable PRD tasks. This skill defines the systematic process for PRD reorganization.

When to Use

Use this skill during the prd_analysis phase, which occurs after the retrospective synthesis but before skill research:

passed → in_retrospective → prd_analysis → skill_research → completed

Trigger Conditions

PRD reorganization is triggered by:

GDD Update - Game Designer sends gdd_ready or gdd_update message
Retrospective Findings - Implementation gaps or deviations discovered
Technical Debt - Debt items identified that need dedicated tasks
Process Improvements - Workflow changes requiring new tasks

PRD Backlog Architecture (v3.1.0+)

Since v3.1.0, tasks are split between two files:

File	Contains	Size
`prd.json`	Top 5 active queue	~5 tasks
`prd_backlog.json`	Remaining backlog	~70 tasks

When reorganizing:

Read both files for complete PRD picture
High-priority tasks (TIER_0, TIER_1) go to prd.json items array
Lower priority tasks go to prd_backlog.json backlogItems array
Maintain max 5 tasks in prd.json.items (move lower priority to backlog if needed)

GDD-to-PRD Task Extraction

Step 1: Read the GDD

# Always read the latest GDD
READ docs/design/gdd.md

# Note the gddVersion for tracking

Step 2: Parse GDD Sections

For each GDD section, extract implementation requirements:

| GDD Section | What to Extract                          | Task Category           |
|-------------|------------------------------------------|-------------------------|
| Gameplay    | Core mechanics, player actions           | architectural           |
| UI/UX       | Interface elements, interactions         | feature                 |
| Multiplayer | Networking, synchronization              | architectural           |
| Audio       | Sound effects, music, spatial audio      | feature                 |
| Visuals     | Shaders, effects, post-processing        | feature                 |
| Performance | FPS targets, optimization requirements   | technical_debt          |

Step 3: Check Existing PRD Coverage

For each extracted requirement, check if PRD already covers it:

# Load both PRD files (v3.1.0+)
READ prd.json
READ prd.backlogFile (or "prd_backlog.json")

# Combine items from both files
$allItems = @($prd.items) + @($backlog.backlogItems)

# For each GDD requirement:
1. Search for related existing task by keyword in $allItems
2. Check if existing task's acceptanceCriteria covers requirement
3. Mark requirement as: COVERED / PARTIALLY_COVERED / NOT_COVERED

Step 4: Create Missing Tasks

For each NOT_COVERED or PARTIALLY_COVERED requirement, create a new task:

{
  "id": "design-001",
  "title": "Implement core gameplay loop from GDD",
  "description": "Implement the core gameplay loop as specified in GDD section 2, including player movement, jumping, and physics interaction.",
  "category": "architectural",
  "priority": "high",
  "status": "pending",
  "passes": false,
  "agent": "developer",
  "dependencies": [],
  "gddReference": "docs/design/gdd.md#2",
  "gddVersion": "1.2.0",
  "acceptanceCriteria": [
    "Player can move with WASD keys",
    "Player can jump with Space key",
    "Gravity physics matches GDD specification (-9.8 m/s²)",
    "Collision detection works with terrain",
    "Frame rate maintains 60fps during gameplay"
  ]
}

Task ID Pattern: Use design-NNN format for GDD-derived tasks to distinguish from user-created tasks.

Step 5: Update Task Priorities

Re-evaluate priorities based on GDD vision:

| Priority | Criteria                                      |
|----------|-----------------------------------------------|
| high     | Core gameplay, blockers, architectural        |
| medium   | Features, polish, UI                          |
| low      | Nice-to-have, optimizations, extras           |

Retrospective-to-PRD Task Creation

Step 1: Analyze Retrospective Findings

Extract actionable items from retrospective.txt:

| Finding Type              | Action Required                          |
|---------------------------|------------------------------------------|
| Implementation gap        | Create task to complete missing work     |
| Design deviation          | Create task to align with GDD            |
| Technical debt identified | Create task with category: technical_debt |
| Process issue             | Update AGENT.md, no PRD task needed       |
| Bug found                 | Create task with category: bug_fix       |

Step 2: Create Tasks for Findings

For each actionable finding, create a PRD task:

{
  "id": "retro-001",
  "title": "Fix physics integration issues identified in retrospective",
  "description": "Address physics inconsistencies reported by Developer during retrospective. Rapier integration not working as expected.",
  "category": "bug_fix",
  "priority": "high",
  "status": "pending",
  "passes": false,
  "agent": "developer",
  "dependencies": [],
  "retrospectiveReference": ".claude/session/retrospective.txt#L15-L25",
  "acceptanceCriteria": [
    "Physics bodies spawn at correct positions",
    "Collision events fire consistently",
    "No physics-related console errors"
  ]
}

Task ID Pattern: Use retro-NNN format for retrospective-derived tasks.

Step 3: Reorganize Existing Tasks

Based on retrospective findings, you may need to:

# Update existing tasks
1. Mark validated tasks: status = "completed"
2. Update blocked tasks: add dependencies
3. Reprioritize based on new information
4. Combine related tasks for efficiency
5. Split oversized tasks into smaller chunks