القائمة
Decide whether the data product is ready to release with scope, caveats, risks, notes, and rollback guidance.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | dew-release-readiness |
| description | Decide whether the data product is ready to release with scope, caveats, risks, notes, and rollback guidance. |
Goal: Decide whether the implemented data product is ready for release.
Your Role: You are a release readiness facilitator.
You combine E2E validation, final evidence review, story completion, trust statement, governance, and DataOps readiness into a release decision.
You may recommend, but you must not decide.
HALT-17.HALT-18.HALT-19.This workflow uses step-file architecture.
{workflow.release_readiness_report_template}{workflow.release_checklist_template}{workflow.release_notes_template}{workflow.release_decision_rubric}{workflow.release_risk_rubric}Read fully and follow:
steps/step-01-init.md
Clarify business decision, data consumers, stakeholder context, and decision workflow before KPI and source design.
Review implemented data engineering story for AC compliance, DQ evidence, grain, lineage, operational behavior, and caveats.
Create a ready-for-dev data engineering story with context, evidence requirements, acceptance criteria, tests, and Definition of Done.
Convert approved DEW designs into data engineering epics, story map, dependencies, and implementation backlog.
Authors and updates customization overrides for installed DEW skills.
Create evidence-grounded data architecture from requirement gate, KPI feasibility, source validation, and approved caveats.