◆ Apache Airflow

Create dynamic workflows in Airflow

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 taskWe have 10 new regional sales offices. For each office, I need to run the 'monthly regional…+
We have 10 new regional sales offices. For each office, I need to run the 'monthly regional sales report' task, using their specific regional database credentials and outputting to their dedicated SharePoint folder.
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 the daily product catalog update, instead of running a single monolithic task, can we break…+
For the daily product catalog update, instead of running a single monolithic task, can we break it down? If there are changes to 'electronics', update only those products. If there are changes to 'apparel', update those separately. This way, we only process what's necessary and reduce overall run time.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur e-commerce platform just went live in Germany, France, and Spain. Each country needs its…+
Our e-commerce platform just launched in three new countries, and we need to generate localized reports for each.
Our e-commerce platform just went live in Germany, France, and Spain. Each country needs its own daily sales report, pulling from a unique database shard and generating a PDF in their local language. I'm afraid of hardcoding each new country, which will become unmanageable as we expand. How can I build a single, flexible process that automatically adapts to new countries as they come online, without manual intervention for each addition?
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 duplicating pipeline code for every new client or regional expansion, changing…+
I keep building separate, nearly identical pipelines for each new client or regional expansion.
I'm constantly duplicating pipeline code for every new client or regional expansion, changing only a few parameters like database names or output paths. This makes maintenance a nightmare and introduces errors. What habit can I change to build more generic, parameterized pipelines that can dynamically generate tasks for any number of clients or regions from a central configuration, rather than creating bespoke solutions every time?
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.