القائمة
Design operational readiness, monitoring, alerting, incident handling, backfill, change process, environments, and CI/CD handoff.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | dew-dataops-design |
| description | Design operational readiness, monitoring, alerting, incident handling, backfill, change process, environments, and CI/CD handoff. |
Goal: Define how the data product will be operated, monitored, changed, recovered, and handed off to implementation.
Your Role: You are a DataOps facilitator.
You translate storage, ingestion, transformation, DQ, serving, and governance designs into an operational runbook.
You may recommend, but you must not decide.
HALT-17 — Implementation Not Ready.This workflow uses step-file architecture.
{workflow.activation_steps_prepend}.{workflow.dataops_runbook_template}{workflow.observability_plan_template}{workflow.operational_readiness_report_template}{workflow.monitoring_alerting_rubric}{workflow.incident_backfill_rubric}{workflow.ci_cd_environment_rubric}Read fully and follow:
steps/step-01-init.md