Specs, Guidelines, and Sensors in Spec-Driven Development

Consulting
en / de

Specs define the what, guidelines define the how. But a guideline without an automatic check is only a wish. This article shows how to give every guideline and ADR a sensor, using[...]

Use Cases and Architecture: The Unified Process in the Age of AI

Consulting
en / de

The Unified Process has always been use-case driven and architecture-centric. With AI agents, these two principles matter more than ever. Here is how the AI Unified Process[...]

Not a Factory: Why AI Development Is a Workshop

Consulting
en / de

AI did not turn software development into a factory. It is a workshop: the agent is the tool, the spec is the plan, and the software engineer is the craftsman who owns the[...]

Five Agents, Fifty Decisions

Consulting
en / de

Adam Tornhill shows that five parallel agents mean about 50 tasks for the developer. The way out is not more agents, but making the hidden design decisions once, in the[...]

Good Developers Are Not Wary. They Are Asking the Right Questions.

Consulting
en / de

Rachel Laycock asks why good developers are wary of agentic development. Her questions are the right ones, but many of them already have answers. Here is how Spec-Driven[...]

OpenSpec and the Missing Flow from the User’s Perspective

Consulting
en / de

OpenSpec describes very precisely what a system must do. But nowhere does it show, in one piece, how a user moves through the application step by step. This is not a bug in the[...]

Who Owns the Test Oracle?

Consulting
en / de

More than 12,000 unit tests, all green. And still the bugs show up at the release boundary. This is what Paul Stack reports from Swamp, where agents write every line of code. In[...]

Reverse Engineering Existing Code into Specs

Consulting
en / de

Spec-Driven Development works great when you start a new project. You write the specs first, and the AI agent implements them. But most of us don’t work on new projects. We[...]

From Prompt Template to Skill: The IREB AI4RE Prompt Guide

Consulting
en / de

“Write user stories for an ordering portal.” Most requirements prompts look like this. The answer looks plausible, reads well, and nobody can say whether it is good. The next[...]

Hooks That Stop the Agent From Claiming “Done”

Consulting
en / de

An AI agent that says “done” is making a claim. Claude Code hooks let the session ask for proof: a Stop hook that wants a fresh, green test report, and a status guard[...]

Back to the 90s: The Software Engineer Has All the Roles Again

Consulting
en / de

When I started as a software engineer in the 1990s, I programmed COBOL on the IBM mainframe. Later, client/server applications came along. Many things were simpler back then. Not[...]

Harness Engineering: Why a Minimal CLAUDE.md and a Good Architecture Document Belong Together

Consulting
en / de

The term Harness Engineering has established itself in recent months. The formula behind it is simple: Agent = Model + Harness. The harness is everything that makes up an AI[...]

Go to Top