What problem does it solve?
This Skill prevents mid-sprint design interruptions by checking whether a story file includes all required GDD/ADR context, testable acceptance criteria, clear scope boundaries, and required evidence hooks so implementation can start immediately.
Core Features & Use Cases
- Readiness verdicts for story files: Produces READY / NEEDS WORK / BLOCKED with a specific gap list for each non-ready story.
- Flexible scope selection: Validates a single story path, the current sprint, all production epics, or sprint/epic-derived sets.
- System and governance validation: Verifies GDD requirement references, ADR status (Accepted vs Proposed), TR-ID registry validity, manifest version currency, and required engine/control manifest notes.
- Implementation readiness checks: Ensures estimates, in/out of scope boundaries, dependencies, no unresolved TBD markers, and a clear Definition of Done with minimum evidence per story type.
- Asset reference existence checks: Detects referenced asset paths and confirms they exist (existence-only), flagging missing assets as NEEDS WORK.
Quick Start
Use the story-readiness skill to validate a specific story file at production/epics/your-epic/story-001.md.