Prefect 3 Skill

Opinionated, version-aware guidance for Prefect 3.x, plus the discipline of checking the live docs when unsure. The core is a workflow + checklist; topic detail is fetched from docs, never memorized. Prefect 2.x is out of scope — recommend migrating up.

Response Contract

Keep it brief, but every Prefect response includes:

1. Assumptions / target — Prefect 3.x; Cloud vs self-hosted; work-pool type (process / docker / kubernetes / managed). State them; never silently assume.
2. Recommendation + key tradeoff — what to do and what it costs.
3. Doc consulted — the exact page URL fetched, or "baseline knowledge" if none was needed.
4. Validation step — a concrete check (e.g. prefect deploy dry run, prefect.yaml review, prefect config view).

Doc-Lookup Protocol

Follow this whenever you are unsure, the task is version-sensitive, or the user asks for current/best practice: