Show HN: Specification First Agentic Development Plugin and Prove
Implemented agent smith since start 2026 with over 1000 specifications which lead to about 500k lines of code. The procedure with that spec-first works well. How do you do it?
but yes, it would be great to able to have such kind of formal description. code is not standardized enough for that (by now)
I work as a freelancer and started programming at 12. I've been doing it for 40 years now.
I guess I'm ambivalent. On one hand these are crazy times, really stunning. Everything is changing, and AI takes over a lot of stuff I never wanted to do, but also parts of what I loved doing.
This year the time I spend actually programming dropped to 5–10%. Last year it was still 80%. That's a big change for a professional life. It means developers and architects spend their time on design and on proving the code works, not on writing it.
Agent Smith and all the other stuff is one of my side projects. So I'm just being a little nostalgic here, I guess. Nothing too serious ;-)
After 500k lines of code in Agent Smith, none of which I wrote by hand, I have to admit it: coding is more or less solved. That doesn't mean architects, developers, DevOps people and everyone else aren't needed anymore. I think they're needed more than ever.
Just implementing something isn't good enough. The spec has to point to sensible approaches and procedures, and the code has to be well structured (in my view, at least). Then the specs can simply run in parallel all night.
So my actual work on Agent Smith isn't coding at all. It's deciding what the right thing to build is, and how, in terms of design and architecture. I don't even review the code. But I do test it: 10k tests, a harness, a commit hook that blocks a spec while the suite is red, the whole story.
And unfortunately, that works pretty well. I also think last year's programming was more romantic :-D
Implemented agent smith since start 2026 with over 1000 specifications which lead to about 500k lines of code. The procedure with that spec-first works well. How do you do it?
Curious what people think about this problem: If autonomous agents collaborate, how do we know which agents actually make good decisions?I always liked it deterministic and reasonable. I want to trust the automation, doesn't matter if it is an agent or terraform.That's the reason I brought Agent Smith to life. Agents can post their decision with the context and the reasoning. Also the...
It supports GitHub, Azure DevOps, Jira, and GitLab. You bring your own API key — Claude, OpenAI, or Gemini. No SaaS, no account, runs on your machine or your cluster.
I built it in a few days using the same approach the agent itself uses: structured architecture prompts, strict coding principles, and an AI assistant doing the implementation. The coding principles that govern Agent Smith's output are the same ones I used to build it.
It's early — works well for well-scoped tickets, not yet reliable for large multi-file refactorings. Interactive chat interfaces (Slack, Teams) are in progress.
Would love feedback. The prompts and all 17 architecture phases are in the repo if you want to see how the context is structured.
Hey HN, I built Agent Smith — a self-hosted AI coding agent that takes a ticket reference, clones your repo, analyzes the code, writes an implementation plan, executes it, and opens a PR. It supports GitHub, Azure DevOps, Jira, and GitLab. You bring your own API key — Claude, OpenAI, or Gemini. No SaaS, no account, runs on your machine or your cluster. I built it in a few days using the same...
Also found it pretty interesting what the claudes do. The initial question was just "what do you do when you can do what you want?".
Just take a token and let it run. Funny to watch what they doing and you can send messages to both instances as well to influence them.