What problem does it solve?
This Skill validates whether a development story file is ready for implementation by checking that design requirements, acceptance criteria, architecture references, asset links, estimates, dependencies, and open questions are complete and unambiguous so engineers can start without mid-sprint design interruptions.
Core Features & Use Cases
- Comprehensive readiness checks: Verifies GDD references, testable acceptance criteria, ADR status, TR-ID validity, manifest version alignment, engine notes, and control manifest considerations.
- Scope and dependency analysis: Confirms estimates, in-scope/out-of-scope boundaries, listed dependencies, and whether dependency stories exist or are in DRAFT.
- Asset verification and verdicts: Globs referenced assets for existence and emits a per-story verdict (READY / NEEDS WORK / BLOCKED) with explicit gap descriptions and blockers; supports single-file, sprint, or all-epics scopes and sprint escalation alerts.
- Collaboration and gating: Produces outputs formatted for QA review, honors review-mode settings, and can spawn director gates for full review when configured.
Quick Start
Validate the story at production/epics/combat/story-001-basic-attack.md and report READY, NEEDS WORK, or BLOCKED with specific gaps and fixes.
