What problem does it solve?
This Skill helps teams confirm that an epic/story file is truly implementation-ready so developers don’t start work and then hit mid-sprint gaps like missing GDD traces, outdated architecture rules, unclear acceptance criteria, or absent evidence requirements.
Core Features & Use Cases
- Story-readiness validation: Checks each story for required structure, testable acceptance criteria, and clear evidence expectations based on story type.
- Architecture and traceability checks: Verifies referenced ADRs (and whether they are Accepted), optional TR-IDs, and control-manifest “Manifest Version” alignment when present.
- Scope and dependency sanity: Ensures estimates exist, dependencies are declared, out-of-scope boundaries are unambiguous, and blocked/draft dependency stories are handled properly.
- Asset reference existence checks: Detects referenced asset paths and verifies they exist (existence-only), flagging missing files as gaps.
Quick Start
Use the story-readiness skill to validate a single story file at production/epics/hatchery/story-005-dragon-unlock-duplicate-xp-and-shiny-upgrade.md and get a READY/NEEDS WORK/BLOCKED verdict with a gap list.