story-readiness

Validate game story markdown files for implementation readiness with GDD traceability and asset checks.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill story-readiness-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill story-readiness-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story readiness checks prevent mid-sprint surprises by verifying that a story’s requirements, architecture references, scope, and acceptance criteria are specific enough to implement and test without guesswork.

Core Features & Use Cases

  • Implementation readiness validation: Produces a READY / NEEDS WORK / BLOCKED verdict with a concrete gap list for any story that’s not ready.
  • Architecture & traceability checks: Verifies GDD requirement references, ADR status (Accepted vs Proposed), TR-ID validity, manifest version currency, and required engine/control-manifest notes.
  • Plan-proof execution support: Validates estimates, dependencies, out-of-scope boundaries, unresolved question markers, and referenced asset existence via path scanning.
  • Use cases: Run it before starting a story, before committing sprint work, or when asking whether a story is safe to implement from the documentation alone.

Quick Start

Use the story-readiness skill on a single story file path to get an implementation-ready verdict and a list of exactly what must be fixed.

Frequently Asked Questions about story-readiness

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

FAQPage Schema
How do I validate if a game story is ready for implementation?

A story readiness check prevents mid-sprint surprises by verifying requirements traceability, architecture references, scope boundaries, and testable acceptance criteria. It ensures stories are specific enough to implement and test without guesswork before development begins.

How to check ADR status and GDD traceability for sprint planning?

Check ADR status by verifying references show Accepted rather than Proposed, and validate GDD traceability by confirming TR-ID validity and manifest version currency. This ensures architecture decisions and requirements are stable before committing sprint work.

Can I run batch readiness checks on all epic stories in production?

Yes, story readiness validation applies to single-story checks, sprint-wide batch checks, and all-production epic story audits. It enforces deterministic readiness gating by requiring references and statuses like ADR, TR, and manifest versions across multiple files.

What acceptance criteria are needed for game development story validation?

Story validation requires testable acceptance criteria that are specific enough to implement and test without guesswork. It enforces existence-only asset verification via path scanning and checks for unresolved question markers before implementation begins.

What limitations exist when checking missing asset dependencies in story files?

Asset dependency checking is limited to existence-only verification via path scanning within the story markdown files. It does not validate asset content, quality, or runtime behavior, only confirming that referenced file paths and required manifests are present.