skills.rest
joekhosbayar
joekhosbayarCOMMUNITY
Explore all skills by this author →
GitHub

gds-create-prd

Convert a Game Design Document into a structured Product Requirements Document.

Updated Dec 23, 2025
Search Tags:#workflow#documentation#collaboration#elicitation#prd#product-management#gdd
One-click install
npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-create-prd-joekhosbayar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-create-prd
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/gds-create-prd
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-create-prd-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning a Game Design Document (GDD) and related project materials into a complete, ready-to-use Product Requirements Document (PRD) using a structured, collaborative workflow.

Core Features & Use Cases

  • GDD-to-PRD conversion: transforms a GDD into formal PRD sections with consistent language.
  • From GDD or From Scratch mode: supports starting from a GDD or building PRD from scratch with guided discovery.
  • Step-based workflow: progressive steps (discovery, vision, success criteria, journeys, domain, FRs, NFRs, polish) to ensure completeness and traceability.
  • Collaborative facilitation: PM facilitator role facilitates discussions, reuses input documents (briefs, research, brainstorming) and loads them into PRD context.
  • Input document loading & traceability: tracks and references input documents and decision points for auditability.

Quick Start

Create a PRD from the GDD and project documents using the guided workflow.

Frequently Asked Questions about gds-create-prd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a Game Design Document into a Product Requirements Document?▼

Yes, you can build a PRD from scratch using a guided discovery workflow. This approach facilitates collaborative discussions to define the vision, success criteria, and requirements progressively, without needing an existing Game Design Document.

How do I structure a PRD for a game development project?▼

Structuring a PRD for a game project involves progressive steps covering discovery, vision, success criteria, journeys, domain, Functional Requirements (FRs), Non-Functional Requirements (NFRs), and final polish. This ensures completeness and delivers a ready-to-use document with an Executive Summary.

Can I incorporate existing brainstorming briefs and research into a PRD workflow?▼

Yes, a collaborative PRD workflow can load and reference existing input documents such as briefs, research, and brainstorming notes. This reuses your project context directly and tracks decision points for full auditability.

What is the best way to facilitate collaborative PRD creation for a development team?▼

A step-based PRD workflow requires progressive completion of discovery, vision, success criteria, journeys, domain, FRs, NFRs, and polish. Skipping these structured stages risks incomplete requirements and loses the traceability needed for project auditability.

Related Skills

Explore More Product & Management Skills→
skyoxuskyoxu

gds-create-gdd

Coordinate a step-based workflow to generate a living gdd.md design document.

Community
Advanced
ArvorCoArvorCo
96

prd

Generate a structured PRD with goals, user stories, and acceptance criteria.

Community
Basic
jordi-murgojordi-murgo

lesson-builder

Create course outlines and presentations through collaborative discussions.

Community
Intermediate
mrcsXndrmrcsXndr

prd

Generate Draft PRDs from domain templates with pre-filled author and date.

Community
Advanced