passed → in_retrospective → prd_analysis → skill_research → completed

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

# Note the gddVersion for tracking

| 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          |

# 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

{
  "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"
  ]
}

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

| 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       |

{
  "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"
  ]
}

# 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

# During prd_analysis phase:

1. READ docs/design/gdd.md (if GDD updated)
2. READ .claude/session/retrospective.txt
3. READ prd.json
4. READ prd.backlogFile (or "prd_backlog.json")

5. EXTRACT requirements from GDD
6. EXTRACT action items from retrospective

7. FOR each requirement/action item:
   a. Check if covered by existing PRD task (check both files)
   b. If NOT covered: CREATE new task
   c. If partially covered: UPDATE existing task

8. REORGANIZE task priorities and dependencies

9. DETERMINE task placement:
   a. TIER_0_BLOCKER, TIER_1_FOUNDATION → prd.json.items
   b. TIER_2_ECONOMY and below → prd_backlog.json.backlogItems
   c. If prd.json.items.length > 5, move lowest priority to backlog

10. WRITE both updated files:
    WRITE prd.json
    WRITE prd_backlog.json

11. COMMIT with message:
    "Retrospective [N]: Reorganized PRD with [X] new tasks from GDD/retrospective"

12. SEND prd_reorganized message to workers:
    {
      "type": "prd_reorganized",
      "from": "pm",
      "timestamp": "<ISO timestamp>",
      "summary": {
        "newTasks": 3,
        "updatedTasks": 2,
        "gddVersion": "1.2.0"
      }
    }

{
  "type": "prd_reorganized",
  "from": "pm",
  "timestamp": "2025-01-21T10:30:00Z",
  "summary": {
    "newTasks": 3,
    "updatedTasks": 2,
    "gddVersion": "1.2.0",
    "newTaskIds": ["design-001", "design-002", "retro-001"]
  }
}

# DO: Break down large features
✓ "Implement player movement system" →
  - design-001: "Implement WASD movement"
  - design-002: "Implement jump mechanics"
  - design-003: "Implement sprint mechanics"

# DON'T: Create monolithic tasks
✗ "Implement all player movement and combat"

# GOOD: Specific and testable
✓ "Player velocity matches input direction within 0.1s"
✓ "Jump height reaches 2 meters when space pressed"

# BAD: Vague and untestable
✗ "Movement feels good"
✗ "Make jumping work better"

| Task Type                    | Agent         |
|------------------------------|---------------|
| Gameplay implementation      | developer     |
| Tests and validation         | qa            |
| Design specs, GDD updates    | gamedesigner  |
| Architecture, coordination   | pm            |

{
  "id": "{original-id}-002",
  "title": "Professional UI/UX Redesign - {Feature Name}",
  "description": "Complete UI/UX redesign based on playtest findings. Current implementation is functionally complete but visually inadequate. Implement a professional design system inspired by {reference titles}. Full specification in {spec-file}.",
  "category": "visual",
  "priority": "high",
  "tier": "TIER_0_BLOCKER",
  "status": "pending",
  "passes": false,
  "agent": "techartist",
  "dependencies": [],
  "gddReference": "{spec-file}",
  "gddVersion": "1.0",
  "specificationFile": "{spec-file}",
  "acceptanceCriteria": [
    "All UI screens enforce 16:9 aspect ratio",
    "UI scales proportionally at any window size",
    "Design system tokens implemented",
    "{Specific visual requirements from spec}"
  ]
}