القائمة
Design and implement ETL orchestration — Airflow, Dagster, or Prefect workflows
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Consult and write the ARAYA postoffice — the operational-directive channel. Advisory, never a gate: read it at cycle start, append your entry at cycle end, consider its directives, never be blocked by it. Governance acts never travel the postoffice.
Audit and enforce brand compliance across all projects and platforms — logo,
Design REST and GraphQL APIs following OpenAPI 3.1 standards. Produce complete
Connect frontend to backend — type-safe API clients, request/response handling,
Implement authentication and authorization middleware — JWT validation, role-based
Design scalable component architectures — design systems, component libraries,
| name | etl-orchestration |
| description | Design and implement ETL orchestration — Airflow, Dagster, or Prefect workflows |
| governance | Constitution ENG-004: Engineering Excellence & Software Craftsmanship Standard |
Design and implement ETL orchestration — Airflow, Dagster, or Prefect workflows that schedule, monitor, and recover data pipelines with dependency management, retry logic, and alerting.
Manual pipeline execution leads to missed runs, hidden failures, and "the data looks stale but nobody noticed." Orchestration ensures pipelines run on schedule, dependencies are respected, failures are alerted, and retries are automatic.
When pipelines need scheduling. When multiple pipelines have dependencies. When pipeline failures must be detected and alerted within minutes.
Pipeline inventory, dependency graph, scheduling requirements, alert preferences.
An Airflow/Dagster/Prefect DAG with tasks, dependencies, schedules, retries, and alerting configuration.
