story-readiness

Name: story-readiness
Availability: InStock
Author: NuoYan

Validate software development stories for implementation readiness and identify missing requirements.

47|12|Updated Jun 14, 2026

Search Tags:#game development #acceptance criteria #architecture review #requirements validation #agile planning #story readiness #dependency checking

Ready to run

npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill story-readiness-nuoyanruoshui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/nuoyanruoshui/GodotGameFramework/tree/main/Godot/.claude/skills/story-readiness
Command: npx skills add https://github.com/nuoyanruoshui/GodotGameFramework --skill story-readiness-nuoyanruoshui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies missing requirements, unresolved design questions, invalid dependencies, and incomplete acceptance criteria before a development story is assigned, reducing implementation delays and mid-sprint guesswork.

Core Features & Use Cases

Readiness Validation: Reviews stories for GDD requirements, ADR references, engine notes, control-manifest rules, estimates, scope boundaries, and test evidence.
Dependency and Asset Checks: Verifies referenced ADRs, technical requirements, dependency stories, manifest versions, and referenced assets.
Actionable Verdicts: Produces READY, NEEDS WORK, or BLOCKED results with specific gaps and recommended fixes for individual stories, sprints, or all production stories.
Use Case: Before assigning a combat story, use this Skill to confirm that its acceptance criteria are testable, its architecture references are approved, its dependencies are complete, and its implementation scope is clear.

Quick Start

Use the story-readiness skill to validate whether the specified story file is ready to implement.

Frequently Asked Questions about story-readiness

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

FAQPage Schema

How do I validate story readiness before starting game development implementation?▼

To validate story readiness, review individual stories for GDD traceability, accepted ADRs, technical requirements, manifest rules, dependencies, estimates, scope boundaries, and test evidence requirements to ensure they are implementation-ready.

What is story readiness validation in agile game development workflows?▼

Story readiness validation is the process of identifying missing requirements, ambiguous acceptance criteria, unresolved design issues, and invalid dependencies before a story is assigned to reduce implementation delays.

How do I check if acceptance criteria are testable for a combat story?▼

Checking acceptance criteria testability involves verifying architecture references are approved, dependency stories are complete, implementation scope is clear, and all referenced assets and technical requirements are confirmed.

Can I validate all stories in a current sprint for unresolved design questions?▼

Yes, you can validate all stories in a current sprint to identify unresolved design questions, invalid dependencies, and incomplete acceptance criteria, producing READY, NEEDS WORK, or BLOCKED verdicts with specific gaps and recommended fixes.

What do I need to check before assigning a story to a sprint?▼

Before assigning a story, check GDD requirements, ADR references, engine notes, control-manifest rules, estimates, scope boundaries, performance budgets, story types, and test evidence requirements to confirm implementation readiness.

What are the limitations of manual story readiness checks in production workflows?▼

Manual story readiness checks often miss missing requirements, ambiguous acceptance criteria, and unresolved design questions across production story collections, leading to mid-sprint guesswork and implementation delays.