story-readiness

You can validate story readiness across a single file, all stories in the current sprint, or every story in the production epics folder. The skill checks GDD references, ADR status, acceptance criteria, asset existence, estimates, and dependencies to return a verdict.

To check acceptance criteria and ADR status, apply the readiness checklist to the story file. The skill verifies these elements alongside GDD references and asset existence, then returns specific gaps to enable quick triage before sprint planning.

Story readiness validation is the process of verifying that a story file has complete design references, clear acceptance criteria, and proper asset links before implementation. You need it during development planning to prevent mid-sprint delays and rework.

Yes, you can check all stories in a sprint at once by applying the skill to the sprint scope. It evaluates every story file in that range and returns individual READY, NEEDS WORK, or BLOCKED verdicts along with specific gaps for quick triage.

Story implementation gets blocked mid-sprint when files lack complete GDD references, clear acceptance criteria, or proper asset links. Validating story readiness before development planning identifies these specific gaps early to prevent delays and rework.

Story readiness validation works flexibly on individual story paths, all stories in the current sprint, or every story in the production epics folder. It processes each scope to return comprehensive verdicts and specific gaps for quick triage.