check-readiness

Analyze project artifacts to validate architectural readiness for engineering.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/igot-ai/os-twin --skill check-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-readiness
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/game-architect/check-readiness
Command: npx skills add https://github.com/igot-ai/os-twin --skill check-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that upstream design artifacts (GDD, UX design, architecture, epics & stories) are complete, aligned, and sufficient for the engineering team to begin implementation without designer clarification.

Core Features & Use Cases

  • Comprehensive artifact discovery and gap reporting across required docs (GDD, UX design, architecture, epics & stories)
  • Epic/story coverage verification and readiness scoring to guide engineering focus
  • Generates a formal readiness verdict with recommended actions for blocks and enablers

Quick Start

Provide your project context and run the readiness check to generate a formal report.

Frequently Asked Questions about check-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate architectural readiness before starting engineering?

To validate architectural readiness, analyze project artifacts to check presence, completeness, and epic coverage. This process gates engineering readiness across GDD, UX design, and epics, producing a formal readiness verdict with a plan.

What is engineering readiness and why does it matter?

Engineering readiness ensures upstream design artifacts like GDD, UX design, architecture, and epics are complete and aligned. This prevents implementation delays by ensuring engineering teams can build without needing designer clarification.

How do I check if my epics and stories have sufficient coverage for engineering?

Check epic and story coverage by verifying their alignment with project artifacts. Readiness scoring guides engineering focus by identifying gaps in required documentation and generating a formal readiness verdict with recommended actions.

Do I need a Game Design Document to check project readiness for engineering?

A Game Design Document (GDD) is required to validate comprehensive readiness. The readiness check discovers and reports gaps across required docs including GDD, UX design, architecture, and epics to ensure sufficient coverage.

What does a formal readiness report include for engineering teams?

A formal readiness report includes artifact discovery results, gap reporting, readiness scoring, and a formal verdict. It provides recommended actions for blocks and enablers to guide engineering teams in resolving design gaps.

When should I run an architecture readiness check?

Run an architecture readiness check during early-stage architecture reviews. It gates engineering readiness by validating that upstream design artifacts are complete and sufficient before implementation begins.