After spending a day trying Structured Prompt-Driven Development (SPDD) , I came away thinking it is a genuinely useful addition to the AI-assisted development toolbox—but not a replacement for every kind of work. SPDD , as described by Thoughtworks and implemented in the open-source open-spdd project, treats prompts as first-class engineering artifacts. Rather than relying on a series of chats that disappear into history, you create a structured prompt, keep it under version control, use it to generate code, and update it when the code or requirements change. In principle, that sounds obvious. If prompts influence implementation, why should they be less durable than the code they produce? In practice, I found it more useful than I expected. What worked well The biggest benefit was task analysis. SPDD pushed me to think through missing parts, unclear assumptions, and potential inconsistencies before I asked the model to write code. This was valuable because the hard part was not gener...
Notes from a software engineer on technology, AI, developer productivity, side projects, and quantified self. Documenting ideas, experiments, and insights along the way.