What problem does it solve? Game teams often need a formal Product Requirements Document with functional requirements, player journeys, success metrics, and scope boundaries, but writing one from scratch is unstructured and error-prone. This Skill facilitates the authoring, revision, and validation of a PRD that builds on an existing GDD rather than relitigating design decisions. ## Core Features & Use Cases - Three intent modes: Create a new PRD through guided discovery, Update an existing PRD against a change signal with conflict surfacing against prior decisions, or Validate a PRD against a structured checklist with a rendered HTML/Markdown report. - Facilitated discovery posture: Brain-dump intake, four-dimension situational reading (stakes, audience, existing inputs, downstream depth), and a choice between Express and Facilitative working modes, with decisions logged in real time to decision-log.md. - Structured artifacts: Ships a menu-style PRD template with an essential spine and adapt-in clusters, a validation checklist, a validation report HTML template, and headless-mode JSON schemas for non-interactive runs. - Use Case: A game studio with a finished GDD needs a PRD for external-tool integration; the Skill extracts the GDD via subagents, pre-populates the PRD draft, flags gaps, and produces prd.md plus a decision log. ## Quick Start Ask the assistant to create a PRD for your game project based on your existing GDD, and it will begin a facilitated discovery session.