gds-prd

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

6|Updated Aug 29, 2026
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-prd-hordricjr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-prd
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-prd
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-prd-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Writing a Product Requirements Document for a game project is hard to do rigorously alone — assumptions go untagged, scope creeps silently, and requirements mix capabilities with implementation details. This Skill acts as an expert PM facilitator that coaches you through producing, updating, or validating a PRD, keeping decisions logged and assumptions visible. ## Core Features & Use Cases - Three intent modes: Create a new PRD through guided discovery, Update an existing PRD against a change signal with conflict detection against prior decisions, or Validate a PRD against a structured quality 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 the PRD builds on design decisions instead of relitigating them. - Discipline enforcement: Decision log, addendum, assumptions index, non-goals, counter-metrics, and a validation checklist keep the artifact honest and traceable. - Use Case: You have a finished GDD for your indie game and need formal functional requirements and player journeys for an external production tool — invoke this Skill to generate a PRD derived from the GDD with gaps flagged. ## Quick Start Ask the assistant to help you create a PRD for your game project based on your existing GDD.

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 with acceptance criteria, success metrics, and scope boundaries, often for external-tool integration.

How do I validate an existing PRD against a quality checklist?

Use validate, review, check, or analyze language when invoking the skill. It spawns a validator subagent that runs the checklist against prd.md, writes structured findings, and renders an HTML and Markdown validation report with a derived grade.

Can this skill run headless without interactive prompts?

Yes. In headless mode it completes the detected intent without asking questions and ends with a JSON status payload listing artifacts, assumptions, and open questions. If intent is ambiguous it halts with a blocked status and reason.

When should I use a GDD or quick-dev workflow instead of a PRD?

Use the GDD skill when capturing game design like mechanics, levels, or art direction. Use quick-dev when you want to build immediately without a planning chain. The PRD fits when you need formal requirements, metrics, and scope boundaries.