메뉴
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.