gds-check-implementation-readiness

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

Updated May 7, 2026

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

Ready to run

npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-check-implementation-readiness-jgabriellima

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-check-implementation-readiness
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/gds-check-implementation-readiness
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-check-implementation-readiness-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game projects often enter production with planning documents that contradict each other, miss requirements, or contain epics that cannot be built independently. This Skill audits your GDD, UX design, architecture, and epics/stories before implementation starts, catching gaps and misalignments while they are still cheap to fix. ## Core Features & Use Cases - Document Discovery: Inventories all planning artifacts, detects duplicate whole/sharded document versions, and resolves conflicts with user confirmation. - Requirements Traceability: Extracts every Functional and Non-Functional Requirement from the GDD and validates each one is covered by an epic or story. - Epic Quality Review: Enforces best practices such as player-value-focused epics, no forward dependencies, proper story sizing, and testable acceptance criteria. - Use Case: Before starting Phase 4 implementation of your game, run this Skill to produce a readiness report listing missing FR coverage, UX/architecture misalignments, and epic quality violations with remediation recommendations. ## Quick Start Ask the agent to check implementation readiness for my game project before we start production.

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 this readiness workflow, which discovers your GDD, architecture, UX, and epics documents, extracts all functional and non-functional requirements, and verifies each requirement is covered by an epic or story. It outputs a readiness report with a READY, NEEDS WORK, or NOT READY status.

How to validate epics and stories against best practices?▼

The epic quality review step checks that epics deliver player value rather than technical milestones, that epics are independent with no forward dependencies, and that stories have testable Given/When/Then acceptance criteria. Violations are documented by severity with remediation guidance.

What documents are required for an implementation readiness check?▼

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

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.

Can the readiness check handle sharded planning documents?▼

Yes, the document discovery step detects both whole markdown files and sharded folder structures with index.md files. If both formats exist for the same document, it flags the duplication and requires you to choose one version before continuing.