◆ Apache Airflow

Make custom macros expand other macros

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
See the prompt↓All Apache Airflow tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskI need these custom macros to expand other macros inside the data pipeline for the Q3 sales…+
I need these custom macros to expand other macros inside the data pipeline for the Q3 sales report. It's Friday and the executive team expects accurate numbers by end of day.
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 acceptBefore I push these macro changes to production, make sure they expand correctly within each…+
Before I push these macro changes to production, make sure they expand correctly within each other. The finance team will be scrutinizing the Q3 sales report, and any miscalculation will cause a serious delay for the executive presentation.
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 Q3 sales report is showing inconsistent numbers after I updated the macros, and I can't…+
The Q3 sales report is showing inconsistent numbers after I updated the macros.
The Q3 sales report is showing inconsistent numbers after I updated the macros, and I can't tell if it's a data issue or if the macros aren't expanding correctly. Priya in finance is already asking questions. I'm afraid of pushing a bad report that gets flagged in the executive meeting. What's the fastest way to diagnose if the macro expansion is the problem and what's my best next step to get reliable numbers?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep losing time debugging macro interactions in complex data pipelines, especially when they…+
I keep losing time debugging macro interactions in complex data pipelines.
I keep losing time debugging macro interactions in complex data pipelines, especially when they need to expand other macros. This always pushes back our reporting deadlines and makes me look unprepared. What habit can I change to proactively ensure these complex macro dependencies work as expected before they cause a fire drill?
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.