What problem does it solve? Turning a game idea or existing GDD into a rigorous Product Requirements Document is hard: requirements drift into implementation detail, scope silently expands, and assumptions go unrecorded. This Skill facilitates the authoring of a PRD with stable FR/UJ IDs, explicit non-goals, tagged assumptions, and a decision log, so downstream UX, architecture, and story workflows have a reliable source. ## 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, or Validate a PRD against a structured checklist with a rendered HTML/Markdown report. - GDD-aware brownfield path: When a Game Design Document exists, a subagent extracts its sections and pre-populates the PRD, flagging gaps the GDD does not cover. - Discipline enforcement: Capabilities-not-implementation FRs, glossary integrity, assumptions index, counter-metrics, and explicit non-goals, validated by a checklist-driven subagent. - Use Case: A solo developer with a finished GDD asks for a PRD to feed an external planning tool; the skill extracts the GDD, drafts a right-sized PRD with FRs and user journeys, logs every decision, and produces a validation report before handoff. ## 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.
