Spec-driven development treats a structured specification—not the codebase—as the system of record. This post maps who does what when you work that way: from turning product intent into an agent-readable spec, through API contracts and UI rules, to validation that implementation still matches what you wrote down. Table of contents Overview Spec-driven development (SDD) is […]
Read More →AI coding agents are fast, but they cut corners. Agent Skills is an open-source project by Addy Osmani that gives agents the same structured workflows senior engineers follow, from spec to ship. This post breaks down how it works, explains the Google engineering principles it builds on (Hyrum’s Law, Chesterton’s Fence, the Beyonce Rule, Shift […]
Read More →A practitioner’s guide to knowing which one you actually need. “Spec-driven” is not one practice. It is a ladder—spec-first (write then ship, spec often rots), spec-anchored (spec and code stay checked in CI), and spec-as-truth / spec-as-source (humans edit only the spec; code is generated). This piece maps the three levels (after Birgitta Böckeler on martinfowler.com), their tradeoffs, a cheat sheet, and […]
Read More →Getting productive in an open source project usually means understanding someone else’s repository before you can ship a useful issue or PR. The default playbook is familiar: clone the repo, read whatever README or contributing guide exists, search the tree, skim recent commits, and hope the architecture becomes clear before you lose momentum. That path […]
Read More →Anthropic shipped Code Review for Claude Code on March 9, 2026. A team of agents runs a deep review on every pull request. They built it for themselves first, then opened it as a research preview for Team and Enterprise customers. The announcement from Anthropic put it plainly: Code output per Anthropic engineer is up […]
Read More →