gds-check-implementation-readiness

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

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

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, architecture, and epics/stories documents to catch gaps and misalignments before implementation starts. ## Core Features & Use Cases - Document Discovery & Inventory: Systematically finds GDD, architecture, epics, and UX documents, flags duplicates between whole and sharded 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, producing a coverage matrix. - Epic Quality Enforcement: Checks epics against best practices such as player-value focus, independence from future epics, no forward story dependencies, and proper acceptance criteria. - Use Case: Before starting Phase 4 implementation of a game, run this Skill to generate an implementation readiness report listing critical issues, missing FR coverage, and actionable recommendations. ## Quick Start Ask the AI to check implementation readiness for my 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 implementation readiness workflow, which discovers your GDD, architecture, epics, and UX documents, extracts all functional and non-functional requirements, and validates that every requirement is covered by an epic or story before production starts.

How to validate epic and story coverage against GDD requirements?

The workflow extracts all FRs from the GDD, reads the epics document for its FR coverage mapping, and builds a coverage matrix showing which requirements are covered and which are missing, with recommendations for remediation.

What makes a good game development epic?

A good epic delivers player or user value rather than technical milestones, functions independently of future epics, contains appropriately sized stories with no forward dependencies, and includes testable acceptance criteria in Given/When/Then format.

Does the readiness check work if I have no UX document?

Yes. The workflow checks for UX documentation and, if none exists, assesses whether UX is implied by the GDD or architecture. If UI elements are implied but undocumented, it records a warning in the readiness report.

What happens if duplicate planning documents are found?

Duplicate whole and sharded versions of a document are flagged as critical issues. The workflow halts and requires you to choose which version to use and remove or rename the other before the assessment can proceed.