story-readiness

Name: story-readiness
Availability: InStock
Author: polsegu

Validate story files for implementation readiness using design, ADR, and acceptance criteria.

Updated Apr 10, 2026

Search Tags:#qa #adr #manifest #sprint #gatekeeping #gdd #story-readiness

Ready to run

npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill story-readiness-polsegu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill story-readiness-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that a story file contains everything a developer needs to begin implementation — no mid-sprint design interruptions, no guessing, no ambiguous acceptance criteria.

Core Features & Use Cases

Parse arguments to scope validation (specific story file, sprint, all stories, or epic).
Load supporting context (GDD references, manifest rules, ADR statuses, and ADR registry) once per run.
Apply a comprehensive readiness checklist covering design completeness, architecture, scope, dependencies, assets, and definition of done.
Produce a clear verdict (READY / NEEDS WORK / BLOCKED) with actionable gaps for each story.

Quick Start

Run story-readiness on a specific story path to get a VERDICT with gaps and suggested fixes.

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 file is ready for implementation?▼

To check story readiness, validate the story file's design completeness, ADR references, and acceptance criteria against project governance rules. This produces a READY, NEEDS WORK, or BLOCKED verdict with actionable gaps to resolve before development begins.

What is story readiness validation in agile development?▼

Story readiness validation is the preflight process of ensuring a story file contains everything a developer needs to begin implementation. It prevents mid-sprint design interruptions by verifying design completeness, dependencies, and unambiguous acceptance criteria.

Can I validate story readiness for an entire sprint or epic scope?▼

Yes, you can validate story readiness across a specific story file, an entire epic, or a full sprint scope. The tool parses arguments to scope validation and loads supporting context like manifest rules and ADR statuses once per run.

What does a NEEDS WORK or BLOCKED readiness verdict mean?▼

A NEEDS WORK or BLOCKED verdict indicates the story file has gaps preventing implementation. NEEDS WORK highlights missing design elements or criteria, while BLOCKED tracks unresolved dependencies or missing ADR references that must be addressed first.

Do I need ADR references and manifest rules to validate a story file?▼

Yes, story readiness validation checks ADR statuses and manifest rules as defined in project governance. It loads the ADR registry and GDD references to ensure the story aligns with established architecture decisions before implementation.

How do I fix gaps found during story readiness preflight checks?▼

To fix gaps found during story readiness preflight checks, address the actionable items listed in the verdict. Update the story file's design completeness, resolve dependency blockers, and ensure all acceptance criteria and ADR references meet manifest rules.