gds-check-implementation-readiness

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

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-check-implementation-readiness-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-check-implementation-readiness
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-check-implementation-readiness
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-check-implementation-readiness-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game projects often enter implementation with planning documents that contain gaps: functional requirements missing from epics, UX needs unsupported by architecture, or stories with forward dependencies. This Skill runs a structured readiness audit that catches these planning failures before production starts. ## Core Features & Use Cases - Document Discovery: Inventories GDD, architecture, epics, and UX documents, flags duplicates between whole and sharded versions, and requires user confirmation before proceeding. - Requirements Traceability: Extracts all FRs and NFRs from the GDD and builds a coverage matrix against epics, documenting every uncovered requirement. - Epic Quality Review: Enforces best practices such as player-value-focused epics, story independence, no forward dependencies, and testable acceptance criteria. - Use Case: Before starting Phase 4 implementation of a game, run the readiness check to produce a report listing critical gaps, coverage percentages, and a READY/NEEDS WORK/NOT READY verdict. ## Quick Start Ask the assistant to check implementation readiness for the game project planning documents in the planning artifacts folder.

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 implementation readiness workflow, which discovers your GDD, architecture, epics, and UX documents, extracts all functional and non-functional requirements, and validates epic coverage. It produces a report with an overall READY, NEEDS WORK, or NOT READY status.

How to validate that epics cover all GDD requirements?

The workflow extracts every FR from the GDD, reads the epics document for its FR coverage mapping, and builds a coverage matrix. Any requirement not traced to an epic is documented as a gap with impact and remediation recommendations.

What makes a good game development epic versus a bad one?

Good epics deliver player or user value and function independently of later epics. The review flags technical milestones like database setup as violations, catches forward dependencies between stories, and verifies acceptance criteria follow testable Given/When/Then structure.

Does the readiness check work if there is no UX document?

Yes. The workflow searches for UX documentation and, if none exists, assesses whether UX is implied by the GDD, such as HUD, menus, or player-facing screens. Missing but implied UX is recorded as a warning in the report.

What happens when duplicate planning documents are found?

Duplicate whole and sharded versions of a document are treated as critical issues. The workflow halts and requires the user to remove or rename one version before continuing, preventing assessments based on conflicting sources.