skills.rest
JunnnnyWon
JunnnnyWonCOMMUNITY
Explore all skills by this author →
GitHub

story-readiness

Validate software story files for GDD references, ADR status, and acceptance criteria.

Updated Aug 27, 2026
Search Tags:#adr#acceptance-criteria#gdd#story-readiness#tr-id#manifest-version
One-click install
npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill story-readiness-junnnnywon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/JunnnnyWon/Codex-Game-Studios/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill story-readiness-junnnnywon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story readiness validation ensures engineering teams start work with complete, unambiguous guidance by checking that a story references approved GDD items, ADRs, engine notes, and measurable acceptance criteria, preventing late design questions.

Core Features & Use Cases

  • GDD and ADR validation: ensures the story links to a specific requirement and that ADRs exist and are current.
  • Acceptance criteria clarity: checks that testable and objective criteria are provided.
  • Scope and dependencies: requires explicit in-scope and out-of-scope definitions and lists dependencies.
  • Manifest and TR-ID alignment: verifies manifest version and TR-ID references are current and valid.

Quick Start

Provide a story file path to validate its readiness and receive a verdict (READY / NEEDS WORK / BLOCKED) with detailed gaps.

Frequently Asked Questions about story-readiness

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

FAQPage Schema
How do I verify story readiness before starting software implementation?▼

Story readiness validation checks individual story files or entire sprints for approved GDD references, ADR status, manifest compatibility, TR-ID validity, and measurable acceptance criteria, returning a READY, NEEDS WORK, or BLOCKED verdict.

What is software story readiness validation and when do I need it?▼

Story readiness validation is the process of ensuring engineering teams start work with complete, unambiguous guidance. You need it to prevent late design questions by enforcing GDD references, ADR status, and measurable acceptance criteria.

How do I check if a story file has the correct ADR status and GDD references?▼

You check ADR status and GDD references by pointing the validation process at a story file path. It verifies the story links to a specific requirement and that ADRs exist and are current, returning gaps if missing.

Does story readiness validation enforce explicit acceptance criteria and scope definitions?▼

Yes, story readiness validation enforces testable, objective acceptance criteria. It also requires explicit in-scope and out-of-scope definitions and lists dependencies to ensure complete implementation guidance.

Can I validate story readiness for an entire sprint or all production epics?▼

Yes, you can validate story readiness across individual story files, the current sprint, or all stories under production epics. It checks manifest version compatibility and TR-ID validity across all provided stories.

Related Skills

Explore More Software Engineering Skills→
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
AmiraultAmirault
1

implement

Executes validated software specifications with automated build and test cycles.

Community
Advanced
LordKuperLordKuper

create-stories

Decomposes epics into actionable story files (.md format) based on ADRs and TR-registry data.

Community
Advanced
laraxotlaraxot
26

gds-check-implementation-readiness

Validate GDD, UX, architecture, and epics alignment for game project implementation readiness.

Official
Advanced