{"id":77116,"plugin_id":"plugins_6ab424ad5b448191b8fede2ebf569333","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:12:27.148Z","digest":"8ebde6c70a19c445f9d15fd84e47c814c22728b4e50282da73846edca51ed558","against":null,"payload":{"description":"Design Airflow or other job orchestration with idempotent retries, scheduling, dependencies and safe backfills.","included_files":[],"name":"design-orchestration","skill_md_contents":"---\nname: design-orchestration\ndescription: Design Airflow or other job orchestration with idempotent retries, scheduling, dependencies and safe backfills.\n---\n\n\n# Orchestration, Airflow and retries\n**Trigger:** DAG design, retries, task failures, missed intervals, scheduling, dependencies, concurrency or Airflow backfill.\n\n1. Capture scheduler and version, data interval/time zone, external side effects, task dependencies, SLAs, concurrency and restart semantics.\n2. Make tasks restart-safe; use deterministic interval inputs, bounded fan-out, clear ownership, idempotent writes and safe retry policies.\n3. Treat clearing, re-running and historical backfills as potentially **new writes**, not harmless scheduler operations.\n4. In Airflow 3, consult current backfill API/CLI documentation for reprocessing rules, active-run limits and interval boundaries; don't apply older commands by memory.\n5. Include lineage, downstream publishing, skipped/partial failure, retries, alert thresholds and runbook.\n6. Test manual triggers, overlapping intervals, failed retries and long-running tasks before rollout.\n\nUse `../../references/orchestration-and-retries.md`, `../../templates/backfill-plan.md`.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}