skills.rest
rakhnianskii9
rakhnianskii9COMMUNITY
Explore all skills by this author →
GitHub

story-readiness

Validate story files against GDD requirements and ADR references for implementation readiness.

Updated Apr 24, 2026
Search Tags:#production#adr#story#readiness#acceptance-criteria#gatekeeping#gdd
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill story-readiness-rakhnianskii9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/story-readiness
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill story-readiness-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate story files to determine if they are implementation-ready by checking embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. This reduces mid-sprint interruptions and rework by providing a clear verdict and actionable gaps.

Core Features & Use Cases

  • GDD/ADR validation: Verifies that the story references approved GDD requirements and ADRs, or notes none if applicable.
  • Verdict generation: Outputs READY, NEEDS WORK, or BLOCKED with a structured list of gaps.
  • Contextual guidance: Aggregates engine notes, TR-ID checks, and manifest-version alignment to guide implementation.

Quick Start

Run story-readiness on a specific story file to determine READY, NEEDS WORK, or BLOCKED along with a gaps list.

Frequently Asked Questions about story-readiness

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

FAQPage Schema
How do I check if a story is ready for development?▼

To check story readiness, validate story files for GDD requirements, ADR references, engine notes, and clear acceptance criteria. This generates a READY, NEEDS WORK, or BLOCKED verdict with an actionable gap list to prevent mid-sprint interruptions.

What is story readiness validation in agile game development?▼

Story readiness validation is the process of preflighting story files to confirm they are implementation-ready. It checks embedded GDD requirements, ADR references, and acceptance criteria to produce a gating verdict, reducing mid-sprint interruptions and rework.

How do I validate acceptance criteria and ADR references for an entire epic?▼

You can validate acceptance criteria and ADR references for an entire epic by running story-readiness across the selected epic or sprint. It aggregates engine notes and TR-ID checks to output a structured readiness report with a gap list.

Does story readiness gatekeeping support GDD and manifest-version alignment checks?▼

Yes, story readiness gatekeeping supports GDD and manifest-version alignment checks. It aggregates engine notes and verifies TR-ID checks to provide contextual guidance for implementation, ensuring all dependencies are correctly referenced.

What are the limitations of automated story readiness checks?▼

Automated story readiness checks are limited to validating embedded metadata like GDD requirements, ADR references, and acceptance criteria within story files. They cannot generate missing content, only identify gaps and output a NEEDS WORK or BLOCKED verdict.

Related Skills

Explore More Product & Management Skills→
emcconnellemcconnell

create-stories

Break epics into traceable story markdown files with QA test cases.

Community
Advanced
brand6brand6

story-readiness

Validate Story files against GDD, ADR, TR-ID, and manifest requirements.

Community
Advanced
DKSangDKSang
2

des-sprint-planning

Generate a dependency-aware sprint plan from Epic and Story catalogs.

Community
Intermediate
nguyennd93nguyennd93

story-readiness

Validate story files for completeness, references, and implementation readiness.

Community
Advanced