Validate story files for implementation readiness and return READY, NEEDS WORK, or BLOCKED.
npx skills add https://github.com/dnkrow/skill --skill story-readiness-dnkrow
Please help me install this Agent Skill. Skill: story-readiness Source: https://github.com/dnkrow/skill/tree/main/claude-global/story-readiness Command: npx skills add https://github.com/dnkrow/skill --skill story-readiness-dnkrow
This Skill prevents mid-sprint surprises by validating whether a story is fully implementation-ready, with clear, testable acceptance criteria and required architecture context.
Run this skill on a single story file to receive a readiness verdict and a concrete list of what must be fixed before implementation.
High-intent search queries and answers about installing and using this skill.
Story readiness validation checks GDD requirement references, acceptance criteria testability, and architecture traceability to return a READY, NEEDS WORK, or BLOCKED verdict with precise gaps. This prevents mid-sprint surprises by ensuring developers start without guessing.
Testable acceptance criteria require clear scope and explicit test evidence expectations without unresolved design questions. Story validation assesses criteria quality by parsing GDD-linked requirements and verifying scope clarity to ensure implementation can proceed without ambiguity.
ADR traceability verification checks the status of referenced Architecture Decision Records and validates TR-ID registry entries within the story file. Readiness gating confirms these architecture references are current and valid before assigning implementation work to developers.
Sprint and epic story validation supports checking one story path, all stories in the current sprint, all production epic stories, or stories for a specific epic. The readiness gate returns individual verdicts and gaps for each validated story.
Dependency and risk gating detects missing or DRAFT dependency stories and flags unresolved design questions as blockers. The validation returns a BLOCKED status with specific gaps, ensuring these dependencies are resolved before implementation begins.
emcconnellBreak epics into traceable story markdown files with QA test cases.
striderZAValidate game story files for GDD traceability and testable acceptance criteria.
Euraika-LabsValidate story files for implementation readiness across specified Git repository scopes.
XGanQAQValidate game story markdown files for implementation readiness with GDD traceability and asset checks.
