◆ Amazon DynamoDB

Develop software design specifications

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 taskWrite the software design specification for the new user authentication service. It needs to…+
Write the software design specification for the new user authentication service. It needs to cover API endpoints, data models, and security considerations, and be ready for review by the architecture team by end of day Wednesday.
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 acceptReview the design spec for the new user auth service. Make sure it clearly outlines how we'll…+
Review the design spec for the new user auth service. Make sure it clearly outlines how we'll handle concurrent requests and potential rate limiting, and flag any areas that might introduce latency or single points of failure.
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 product owner just dropped SAML support into the user auth spec. We're already tight on…+
We just got a last-minute change request for the user auth service, pushing us to support SAML in addition to OAuth.
The product owner just dropped SAML support into the user auth spec. We're already tight on time for the Wednesday review, and I'm worried about the complexity this adds to the data model and security. What's the most pragmatic way to integrate this without blowing up the timeline, and what should I flag as the biggest risks to the architecture team?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternMy design specs keep getting sent back because I miss critical edge cases and error handling…+
My software design specs often get flagged for not adequately addressing edge cases or error handling.
My design specs keep getting sent back because I miss critical edge cases and error handling scenarios. I get too focused on the happy path. What habit can I change in my design process to consistently anticipate and document these harder-to-spot failure modes before the review?
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.