gds-check-implementation-readiness

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.

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.

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.

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.

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.