gds-check-implementation-readiness

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game projects often enter production with planning documents that contradict each other, miss functional requirements, or contain epics with broken dependencies. This Skill audits your GDD, UX, architecture, and epic documents before implementation starts, catching gaps and misalignments while they are still cheap to fix. ## Core Features & Use Cases - Document Discovery and Inventory: Systematically finds GDD, architecture, epics, and UX documents, flags duplicates between whole and sharded versions, and requires user confirmation before proceeding. - Requirements Traceability: Extracts every FR and NFR from the GDD and builds a coverage matrix against the epics document, listing each uncovered requirement with impact and remediation notes. - Epic Quality Enforcement: Validates epics against best practices such as player-value focus, epic independence, no forward story dependencies, and testable acceptance criteria, then compiles a final readiness report with an overall READY/NEEDS WORK/NOT READY verdict. - Use Case: Before starting Phase 4 implementation of a game, run this Skill to produce an implementation-readiness report that lists critical planning defects, missing FR coverage, and recommended next actions. ## Quick Start Ask the assistant to check implementation readiness for the 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 readiness workflow, which discovers your GDD, architecture, epics, and UX documents, extracts all functional and non-functional requirements, and verifies each one is covered by an epic. It produces a report with an overall readiness status and recommended fixes.

What does an implementation readiness review check in epics and stories?

It validates that epics deliver player value rather than technical milestones, that each epic is independent of later epics, that stories have no forward dependencies, and that acceptance criteria follow testable Given/When/Then structure. Violations are ranked as critical, major, or minor.

Can the readiness check handle sharded planning documents?

Yes. The discovery step searches for both whole documents and sharded folder versions with an index file. If both formats exist for the same document type, it flags the duplicate and requires you to choose one version before continuing.

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 no document exists, it records a warning in the report rather than silently skipping the alignment check.

Does the readiness workflow modify my planning documents?

No. It only reads the planning artifacts and writes a separate implementation-readiness report to the planning artifacts folder. Your GDD, epics, and architecture files remain unchanged.