gds-prd

Create, update, and validate game project PRDs through facilitated discovery workflows.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-prd-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-prd
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/gds-prd
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill gds-prd-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

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.

Frequently Asked Questions about gds-prd

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

FAQPage Schema
How do I create a PRD from an existing game design document?

Invoke the skill with your GDD present and choose the From GDD path during discovery. A subagent extracts the GDD's sections, maps them onto the PRD structure, pre-populates the draft, and flags gaps the GDD does not cover.

What is the difference between a GDD and a PRD for a game project?

The GDD is the primary design document holding mechanics, levels, art, audio, and progression. The PRD captures formal functional and non-functional requirements, player journeys, success metrics, and scope boundaries, referencing GDD decisions rather than duplicating them.

How do I validate an existing PRD against a checklist?

Use the Validate intent by pointing the skill at an existing PRD. It spawns a validator subagent that runs the validation checklist against prd.md, writes structured findings, and renders an HTML and Markdown validation report with a derived grade.

Can the PRD workflow run headless without an interactive user?

Yes. In headless mode the skill follows references/headless.md, completes the detected intent without prompting, and ends with a JSON status payload listing artifacts, assumptions, and open questions. Ambiguous intent returns a blocked status with a reason.

When should I not use a PRD for game planning?

Skip the PRD when the work is pure game design, which belongs in the GDD skill, or when you want to build immediately without a planning chain, which fits a quick-dev workflow. Small one-to-two story scopes can use the all-inclusive PRD variant with inline stories.