gds-check-implementation-readiness

Validates GDD, UX, architecture, and epic alignment before game implementation begins.

1|Updated Sep 18, 2026

Search Tags:#game development #requirements traceability #readiness check #gdd #epic validation #planning audit

Ready to run

npx skills add https://github.com/PastaSus/egg-defender --skill gds-check-implementation-readiness-pastasus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-check-implementation-readiness
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/gds-check-implementation-readiness
Command: npx skills add https://github.com/PastaSus/egg-defender --skill gds-check-implementation-readiness-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game projects often enter production with gaps between the Game Design Document, architecture, UX plans, and epics, causing missed requirements and rework. This Skill audits all planning artifacts for completeness, traceability, and alignment before implementation starts. ## Core Features & Use Cases - Document Discovery: Inventories GDD, architecture, epics, and UX documents, flagging duplicates and missing files for user resolution. - Requirements Traceability: Extracts all FRs and NFRs from the GDD and validates epic coverage with a coverage matrix. - Epic Quality Review: Enforces best practices such as player-value epics, no forward dependencies, and testable acceptance criteria. - Use Case: Before starting Phase 4 implementation, run the readiness check to produce a report listing missing FR coverage, UX alignment gaps, and epic quality violations with actionable recommendations. ## Quick Start Ask the assistant to check implementation readiness for the current game project planning documents.

Frequently Asked Questions about gds-check-implementation-readiness

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

FAQPage Schema

How do I check if my game design document is ready for implementation?▼

Run the readiness check workflow, which discovers your GDD, architecture, epics, and UX documents, extracts all FRs and NFRs, and validates epic coverage. It produces a report with an overall readiness status and recommended actions.

How to validate epic coverage against GDD requirements?▼

The workflow extracts every functional requirement from the GDD and compares it against the FR coverage claimed in the epics document. It builds a coverage matrix showing which FRs are covered and flags any missing requirements with impact and recommendations.

What documents are required for the implementation readiness check?▼

The workflow searches for GDD, architecture, epics and stories, and UX documents in the planning artifacts folder, supporting both whole files and sharded folder formats. Missing documents generate warnings, and duplicates must be resolved before proceeding.

What epic quality issues does the readiness check detect?▼

It flags technical epics with no player value, forward dependencies between stories, epics that depend on future epics, vague acceptance criteria, and data structures created before they are needed. Each violation is documented with severity and remediation guidance.

What happens if my project has no UX design document?▼

The workflow checks whether UX is implied by the GDD, such as HUD, menus, or player-facing screens. If UX is implied but missing, it adds a warning to the report rather than blocking the assessment.