story-readiness

Validates story documents for completeness and adherence to game dev guidelines.

Updated May 24, 2026
One-click install
npx skills add https://github.com/LeKay/ai-game --skill story-readiness-lekay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/LeKay/ai-game/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/LeKay/ai-game --skill story-readiness-lekay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of implementing a story without proper planning and documentation, leading to mid-sprint design interruptions and confusion among developers.

Core Features & Use Cases

  • Story Validation: Checks for required elements like GDD requirements, ADR references, clear acceptance criteria, and no open design questions.
  • Verdict Generation: Provides a verdict (READY / NEEDS WORK / BLOCKED) along with specific gaps.
  • Review Mode: Offers flexibility through different review modes (full, lean, solo) at startup.
  • Output: Delivers a detailed summary of each story's readiness status, highlighting specific areas needing improvement.
  • Collaborative Protocol: Ensures a non-editing, read-only approach that guides users on how to address gaps.

Quick Start

Run the story-readiness skill with a specific story file path to check its readiness.

Frequently Asked Questions about story-readiness

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

FAQPage Schema
How do I validate game development story readiness before implementation?

Story readiness validation checks story documents for completeness, verifying references to GDD requirements, ADRs, and control manifest. It outputs a READY, NEEDS WORK, or BLOCKED verdict with specific gaps to prevent mid-sprint design interruptions.

What is story validation in game design and development?

Story validation is the process of checking game development story documents for clear acceptance criteria, GDD requirements, ADR references, and no open design questions. It ensures documentation completeness before implementation begins.

How do I check story documents for open design questions and missing ADR references?

Run a readiness check on your story file path to scan for missing ADR references, GDD requirements, and open design questions. The check identifies gaps and outputs a readiness verdict detailing specific areas needing improvement.

Can I use different review modes for checking story requirements?

Yes, story readiness checks offer flexible review modes including full, lean, and solo options at startup. Each mode delivers a detailed summary of the story's readiness status, highlighting specific gaps for improvement.

What's the best way to ensure acceptance criteria are clear before implementing a game story?

Use a story readiness validation tool to verify clear acceptance criteria, GDD requirements, and ADR references. This collaborative protocol uses a read-only approach to guide users on addressing gaps without editing the documents directly.

Why does my story readiness check return a BLOCKED verdict?

A BLOCKED verdict occurs when story validation finds missing requirements like GDD references, ADRs, control manifest links, or clear acceptance criteria, or identifies open design questions. The output details specific gaps blocking implementation.