Spec first, then prompt: the one-page plan for when your AI keeps rewriting your app

GitHub says the fix for "it looks right but doesn't quite work" isn't a better prompt, it's a spec. Here's what spec-driven development means in… Aliteq Syntax · Build Editor

Spec-driven development means writing down what you're building and what "done" looks like before you ask an AI to build it, so the spec, not a one-off prompt, drives the work. GitHub made the case…

The idea — write the spec first; let it drive what gets built

GitHub's diagnosis — the problem is our approach, not the agent's ability

For you — a one-page spec works in any builder, no toolkit needed

The caveat — it's GitHub's argument for its own toolkit; we haven't run it

A vague prompt asks the AI to guess what you want. A spec tells it. Write the spec once, reuse it in every chat, and spend your effort checking the result instead of re-explaining.

Read the full story

Aliteq Spec first, then prompt: the one-page plan for when your AI keeps rewriting your app Read the full story on Aliteq