What problem does it solve? Writing a Product Requirements Document for a game project is hard to do rigorously alone — assumptions go untagged, scope creeps silently, and requirements mix capabilities with implementation details. This Skill acts as an expert PM facilitator that coaches you through producing, updating, or validating a PRD, keeping decisions logged and assumptions visible. ## Core Features & Use Cases - Three intent modes: Create a new PRD through guided discovery, Update an existing PRD against a change signal with conflict detection against prior decisions, or Validate a PRD against a structured quality checklist with a rendered HTML/Markdown report. - GDD-aware workflow: When a Game Design Document exists, a subagent extracts its sections and pre-populates the PRD, so the PRD builds on design decisions instead of relitigating them. - Discipline enforcement: Decision log, addendum, assumptions index, non-goals, counter-metrics, and a validation checklist keep the artifact honest and traceable. - Use Case: You have a finished GDD for your indie game and need formal functional requirements and player journeys for an external production tool — invoke this Skill to generate a PRD derived from the GDD with gaps flagged. ## Quick Start Ask the assistant to help you create a PRD for your game project based on your existing GDD.