How Good Programmers Use AI as a Real Pair Partner: Spec-Driven Development Meets Socratic Inquiry

There is a running joke in the developer community: “AI wrote the code, but nobody knows what it does.” The punchline lands because it is true. Programmers everywhere are pasting vague prompts into chat windows, copying the output verbatim, and shipping it straight to production. The code appears. The tests pass. The bug report arrives three hours later.

This is not an AI problem. It is a workflow problem. The developers who actually get better results with AI are not the ones who type faster. They are the ones who treat AI like a junior engineer - one who is brilliant, tireless, and has zero context - and structure their collaboration accordingly.

This article lays out a concrete workflow for that: Spec-Driven Development (SDD) combined with Socratic inquiry, anchored in real GitHub tooling and open-source patterns. If you have been using AI to code but feeling like something is off, this is probably what you have been missing.

The Core Problem: AI Amplifies Your Thinking, Not Your Silence

When you ask AI to "build a user auth system," you are doing the same thing as handing a blank sheet of paper to a contractor and saying "build me a house." You will get something. It might even look right. But you will not like the result.

AI is a pattern engine with no skin in the game. It does not know your codebase, your users, your constraints, or your trade-offs. It will confidently produce something wrong if you do not give it something to work with.

Good programmers know this. They use AI as a thinking partner, not a code vending machine. And the mechanism they use to do that is specification-first development - writing down what they want before they ask for it.

What Is Spec-Driven Development?

Spec-Driven Development is exactly what it sounds like: you write a specification first, then you write code. The spec is the source of truth, not the code.

GitHub’s official spec tool (part of the instructor family) is built for exactly this. It lets you define structured specifications - JSON schemas, pydantic models, domain objects - and have AI generate code that conforms to those specs. More importantly, it gives you a contract to validate against.

Here is the basic idea:

from pydantic import BaseModel
from typing import Optional
import instructor

# Define the spec - this is your contract with the AI
class APIResponse(BaseModel