◆ Amazon DynamoDB

Build dynamic workflow orchestration engines

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 Amazon DynamoDB tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate a new workflow step that, after an order is marked 'PAID', sends a confirmation email to…+
Create a new workflow step that, after an order is marked 'PAID', sends a confirmation email to the customer. This should be a simple, single-action step.
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 new customer onboarding flow, after a user completes their profile, we need to trigger…+
For our new customer onboarding flow, after a user completes their profile, we need to trigger a sequence: send a welcome email, then schedule a demo call with Sales, and finally assign them to a nurture campaign. If the demo call scheduling fails, the nurture campaign should still proceed, but Sales needs an immediate alert. Design this sequence to be resilient and handle partial failures gracefully.
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 'new product launch' workflow, which involves updating the catalog, notifying marketing,…+
A critical business process involving multiple steps across different services is failing intermittently, but the exact point of failure is unclear.
Our 'new product launch' workflow, which involves updating the catalog, notifying marketing, and pushing to the CDN, is failing about 10% of the time, and I can't pinpoint if it's the catalog update or a subsequent step. When it fails, the product isn't visible to customers, costing sales. I'm worried about missing the Black Friday deadline. How can I quickly diagnose where the workflow breaks down and ensure all steps are completed reliably, even if one service is temporarily unavailable?
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 building these sprawling, interdependent workflows for business processes that become…+
Building complex, multi-step business processes often results in brittle code that's hard to monitor and recover from failures.
I keep building these sprawling, interdependent workflows for business processes that become incredibly fragile and hard to debug when a single component fails. What habit should I change in how I design and implement these dynamic orchestrations to make them more observable, resilient to individual service failures, and easier to recover, so I'm not always chasing down intermittent issues and rebuilding from scratch?
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 Amazon DynamoDB'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.