AI-accelerated. Spec-driven. Under guardrails.
We use AI to move faster — but under discipline, with a written spec in front of it. The result is the same seriously-engineered software, delivered sooner.
The fear with AI in software is real: plausible code nobody understands, tests that were never written, bugs that surface in production. That's the slop we refuse to ship.
Our answer isn't to avoid AI — it's to keep it inside the same engineering discipline we've always worked to. We use OpenSpec: an open, spec-driven workflow where every change is thought through and written down before a line of code is generated. The AI works to an agreed spec, not a vibe, and a senior engineer owns the result.
The guardrails
Specs come first, with OpenSpec
We write the specification before the code, as an OpenSpec change — proposal, design, specs, tasks. AI builds to that spec, so the output solves the actual problem, not a plausible-looking approximation of it.
Tests wrap everything
Every change ships with its test suite. Spec-driven means the tests describe the agreed behaviour, and nothing merges that breaks them.
Coverage gates hold the line
Our CI refuses anything below 100% line and branch coverage. AI-assisted or not, code that isn't exercised by a test does not ship.
A human owns every change
A senior engineer reads, reviews and owns every line before it merges. AI is a power tool in our hands — never an author left unattended.
Four steps, from idea to shipped.
Explore
We think the problem through first — investigating the codebase, sketching options, challenging assumptions. No code yet, just clarity.
Propose
The change gets written down: a proposal, a design, specs, and a task breakdown. A reviewable plan you could read before we build a thing.
Apply
We implement task by task, each checked off against the spec. The AI moves fast; the spec keeps it honest.
Archive
The agreed behaviour folds into our living specification. The paper trail stays — every decision is auditable, long after the commit.
Speed without the slop
You get software delivered faster, with none of the compromise: specified, tested, fully covered, and reviewed by the engineer whose name is on it.
We build our own product this way, too — this very site's sitemap page went from idea to shipped through OpenSpec: explore, proposal, specs, tasks, done. Faster, and still built to last.
Start with a spec, not a guess
Tell us what you want to build. We'll show you the plan before we write the code.
Talk to a Code Bunny