Optivem Journal

Optivem Journal

Spec-Driven Development

Spec-Driven: Bad AI Prompts vs. Good AI Prompts

A detailed prompt can still send AI in the wrong direction.

Valentina Jemuović's avatar
Valentina Jemuović
Oct 23, 2026
∙ Paid

⚡Spec-Driven Development in Legacy Code
Hands-on work with your teams. Limited spaces for 2027.

Book a call


We often hear that getting better results from AI is a matter of writing better prompts.

Be more specific. Give the AI a role. Add context. Explain what you want.

All of that can help. But: a prompt can be detailed, well-written, and still lead you in the wrong direction.

1. Don’t ask AI to confirm your decision. Ask it to evaluate it.

❌ Treating the decision as already made

“We’ve decided to move to microservices. Outline how to split our application into services.”

What’s wrong?

The decision is presented as settled, so the AI works on the next step. It will produce a sensible-looking list of services. It won’t usually stop to ask whether you need microservices at all.

Ask a model directly “Are microservices better than a monolith?” and it will usually say “it depends”. The risk is the prompt where the decision is built in and never questioned.

This post is for paid subscribers

Already a paid subscriber? Sign in
© 2026 Valentina Jemuović, Optivem · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture