des-story-readiness-check

Story readiness evaluation assesses clarity, acceptance criteria, test expectations, and epic mapping before development begins to prevent vague stories from entering build. It verifies scope and required refinement routing for safe sprint commitment.

Story readiness evaluation is a pre-development verification process that checks traceability to DES artifacts, dependency status, data contract rules, and governance security alignment. It ensures implementation stories have required clarity before entering the build phase.

Verify traceability by checking that each story maps to the correct DES planning and implementation artifacts by story type, including ingestion, bronze, silver, gold, serving, and CI/CD layers. This confirms specification coverage before development begins.

Yes, safety guardrails flag missing or conflicting requirements for quality, contract, governance, and security constraints. They also identify unresolved dependencies, blockers, and story size problems to avoid unsafe or non-implementable work.

Use story readiness checks to evaluate clarity, acceptance criteria, test expectations, and data contract rules before sprint planning. This produces an actionable readiness report and identifies required refinement routing for unsafe stories.

Yes, the readiness check requires existing story-catalog and sprint-plan artifacts already produced by prior skills. It uses these inputs to generate a comprehensive story-readiness-report for the selected implementation stories.