What problem does it solve? Game teams often need a formal Product Requirements Document with functional requirements, player journeys, success metrics, and scope boundaries — especially when integrating with external tools that expect PRD format — but drafting one from scratch or deriving it from an existing GDD is unstructured and error-prone. ## Core Features & Use Cases - Three intent modes: Create a new PRD through facilitated discovery, Update an existing PRD against a change signal with conflict surfacing, or Validate a PRD against a structured 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 design decisions are referenced rather than relitigated. - Discipline enforcement: Decision logging, assumption tagging, non-goal callouts, and a validation checklist keep the PRD honest about scope and traceable for downstream workflows. - Use Case: A producer with a finished GDD needs a PRD for a publisher review. The skill extracts the GDD, drafts a PRD with FRs, user journeys, and success metrics, then runs a validation pass and renders a graded report. ## Quick Start Ask the assistant to create a PRD for your game project based on your existing GDD, and it will guide you through discovery and produce the document.
