◆ Apache Airflow

Pass parameters to dependent tasks

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskThe `process_new_users` task needs the `signup_date` from the `fetch_user_data` task. Pass that…+
The `process_new_users` task needs the `signup_date` from the `fetch_user_data` task. Pass that date as a parameter.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptFor our campaign tracking, the `generate_report` task needs to know which `campaign_id`…+
For our campaign tracking, the `generate_report` task needs to know which `campaign_id` successfully completed processing from the `process_campaign_data` task. If multiple campaigns run, I need the report to reflect all of them, so the marketing team gets a complete picture.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe daily summary report is showing incomplete data, and I just found out the…+
The `daily_summary` report is showing incomplete data because a downstream task isn't getting the correct filtered list of transactions.
The daily summary report is showing incomplete data, and I just found out the `calculate_metrics` task isn't getting the correct filtered list of transactions from `extract_transactions`. I'm worried about the report's accuracy for the board meeting tomorrow. What's the most reliable way to pass that filtered list, ensuring data integrity, and what's the quickest check I can do now to confirm the data flow?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly debugging data discrepancies because parameters aren't correctly passed between…+
I often find myself debugging data discrepancies because parameters aren't correctly passed between dependent tasks.
I'm constantly debugging data discrepancies because parameters aren't correctly passed between dependent tasks, leading to inaccurate reports and wasted time. This reactive fix-it cycle is draining. What habit can I change to ensure robust and transparent parameter passing, so I can trust the data flowing through our pipelines?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Airflow's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.