Note on Learnings From a No-Code Library: Keeping the Spec Driven Development Triangle in Sync via Drew Breunig

the Spec-Driven Development Triangle.

As each node moves forward, our job — and our tooling’s job — is to keep those nodes in sync. That’s the job. If we improve the code, we must improve the spec.

FROM:

Drew Breunig

Learnings From a No-Code Library: Keeping the Spec Driven Development Triangle in Sync

Source

This might be a good approach to addressing the problems I’ve had in taking SDD to agents in the past year. It’s a networking of the changes, not a pipeline.

Key points:

• all parts are tracked in git
• it’s a static tool, not part of the agent’s logic

I don’t think it can be a skill. Whatever tool we end up using for tracking decisions and intent, it cannot live only inside the agent. It needs to run outside. It needs to handle small commits, triggers, anything…even if you never touch the agent. A skill is a suggestion. A tool needs to be a checkpoint.