Creator of the AI Unified Process. Java Champion, Vaadin Champion, Oracle ACE Pro, Author, Speaker, Programming Architect, and Lecturer.
Erlach, Schweiz
Joined April 2009
- Tweets28.8K
- Following1.7K
- Followers10K
- Likes22.7K
Pinned Tweet
Surprise! My book arrived two weeks before the official release date. 🎉
"Spec-Driven Development: From Specs to Code with AI Agents" (Apress Pocket Guides) is now available, both as softcover and eBook.
It is a compact guide on how to make specs the contract between you and your AI agents, based on the AI Unified Process (AIUP). Requirements, use cases, entity models, and a complete case study, all in about 150 pages.
I hope it helps you bring more structure into AI-assisted development.
👉 link.springer.com/book/10.10…
#SpecDrivenDevelopment #AIUnifiedProcess #GenerativeAI #KeepITSimple
🚀 AI Unified Process Marketplace 3.0 is here!
The marketplace has a new architecture: one plugin per technical layer instead of one plugin for an entire technology stack.
Why? Because every project is different, and your development workflow should reflect that.
With Marketplace 3.0, you can:
🔹 Combine plugins for your specific technology stack
🔹 Reuse the core for implementation, testing and coverage analysis
🔹 Add new technologies without building an entire stack plugin
🔹 Keep things modular and use only what your project needs
The marketplace now separates the process from the technology stack. The AI Unified Process stays the same, while the plugins provide the technology-specific capabilities.
Less duplication. More flexibility. Easier to extend.
As always, I build this to solve real problems in real projects. Eat your own dog food!
👉 Explore the new architecture: unifiedprocess.ai/layer-plug…
#AIUnifiedProcess #SpecDrivenDevelopment #ClaudeCode #SoftwareArchitecture #AI
🤖 Made with AI
Simon Martinelli retweeted
If you really think that frameworks and libraries don't matter "because we don't look at the code anymore", then take a plain Java JDK and have your agent write a web application not using any framework or library. Probably not very token efficient...
Reverse Engineering Existing Code into Specs
martinelli.ch/reverse-engine…
Simon Martinelli retweeted
We're donating Agent Skills to the Agentic AI Foundation (@AgenticAIFdn), the same foundation we donated MCP to.
Since December 2025, 70+ agent platforms have integrated the standard, including ChatGPT, Cursor, GitHub Copilot, and VS Code.
Here's what that means for you:
Simon Martinelli retweeted
You can laugh at PHP and Node now, but your tech will be next. AI knows about all the security flaws and nothing is safe.
Start by scanning all your dependencies and using good AI models to review your code for security holes
Tell Claude/Codex to do penetration testing
Simon Martinelli retweeted
Artificial Intelligence company Anthropic recorded a $80 BILLION net loss in the first half of 2026
From Developer to Builder: A Spec Driven Development Deep Dive
The recording from Devoxx 2026 is available on YouTube.
youtube.com/watch?v=z8lal-Yt…
Simon Martinelli retweeted
Says @simas_ch: “Write the use case before you prompt: write the actors, the main scenario, the alternative flows & the business rules in a simple Markdown file. Give that file to your AI agent and let it implement the feature and the tests from it."
🔗 ow.ly/4rR550ZR08w
I highly recommend this conference 👇
I had the privilege to be a speaker at the London edition this spring.
London sold out. NYC is next.
AI DevCon New York, 2–4 Nov, Brooklyn: 700+ engineers on agents after the demo.
On the agenda:
→ @GoogleDeepMind: stop babysitting your agents
→ @SpaceXAIMemphis: PRs written end to end by agents
→ @datadoghq: is your agent rollout working?
→ @temporalio : when agents run their own tools
Workshop seats are limited: aidevcon.io
Simon Martinelli retweeted
What if your specs became the foundation for code, tests, and validation? Learn from @simas_ch how a spec-first approach reduces guesswork, improves alignment, and helps teams build software more efficiently. #SoftwareDevelopment #DevOps #Engineering
🔗 ow.ly/evz250ZW0HX
Simon Martinelli retweeted
Long ago it was a developer rite of passage to create a web framework. Last year creating an agent framework was the rite of passage. This year it is agent harness. Get out there and build yourself a harness! You’ll learn a lot and might even create something exceptional.
Vaadin is AI native. And it's an amazing fit for Spec-Driven Development.
Vaadin 25.3 is built for AI coding agents that work on Java UIs:
✅ A dev loop that works like an IDE for your agent
✅ A self-hosted MCP server with the full Java API (even air-gapped)
✅ Browserless tests, so the agent gets fast feedback without a browser
✅ An Observability Kit insights endpoint your agent can read
Why does this matter for Spec-Driven Development?
With Vaadin, the UI is plain Java. No JavaScript, no REST layer, no second tech stack. The agent works in one language and one codebase. That makes it much easier to go from the spec to running code, and to check with tests that the code still matches the spec.
Specs give the direction. Vaadin keeps the path short.
🎥 Watch the 5-minute overview: youtube.com/watch?v=WnkI6xA9…
📣 Want to see it live? Next week I speak at Vaadin Create 2026 in Barcelona (27-28 October): "Spec-Driven Development - Why Vaadin Is the Perfect Fit"
AI can generate code. The hard part is to keep it aligned with the system you really want to build. I will show how specifications and architectural guardrails guide a full-stack Java application while it grows.
See you in Barcelona! 🇪🇸
vaadin.com/vaadin-create-202…
#Vaadin #Java #SpecDrivenDevelopment #AIUP #AI #VaadinCreate
Leanpub Book LAUNCH 🚀 Writing Use Cases for AI by Simon Martinelli #book... youtu.be/O9mdf34ibD0?is=zNkX…
Simon Martinelli retweeted
If you silently correct the mistakes you junior coworkers makes, without telling him what was wrong and why it was wrong, you deprive them from learning and they're going to make the same and similar mistakes again.
Same with your AI coding agent.
Postgres Just Went Realtime | Neon Changelog youtube.com/shorts/6HQrNMQ8P…
Simon Martinelli retweeted
Says @simas_ch: “Write the use case before you prompt: write the actors, the main scenario, the alternative flows & the business rules in a simple Markdown file. Give that file to your AI agent and let it implement the feature and the tests from it."
🔗 ow.ly/4rR550ZR08w
I never liked the idea of PRs in business applications. Overall reviews are way more accurate to share knowledge. Which is also important in times of AI
Why are you still using pull requests?
Is it for code review?
If so, do you really think your or your colleagues catch bugs and mistakes that an Opus 5.5 or Fable or Astra won't find? You can literally spawn all three of them and have them check four times each.
(Also, don't tell me you don't have a "stamp plz" Slack channel or group chat somewhere.)
Is it for knowledge sharing?
Surely there's better ways for that now than the PR, no? We have models that can generate explainer videos, presentations, podcasts, games, quizzes, walkthroughs, ... for any piece of code it can reach.
Is CI the reason?
Well ackshually, CI means continuous integration and its original meaning is the *opposite* of having long-lived branches and PRs.
But, leaving that aside, your agents are hopefully already running the tests before they push something, and hopefully they can run as long as they want and don't block you so they can run the whole test suite and generate "irrefutable proof" and end-to-end demo videos and so on... And so they run the tests and confirm and then you push to a branch and everything runs again and then you merge and then it runs again? That doesn't make sense, does it?
Maybe you work in open source and you accept contributions, in which case I can't speak to the value of pull requests. It's been 2 years since my last OSS contribution. But from what I heard, the time of the PR is coming to an end in OSS too?
I honestly don't get why people still stick to PRs.
With agents you can now move 10x faster, you can finally do real continuous integration, and get more confidence in the changes the agent made.
Don't slow yourself down by having all the changes pile up in a PR.
Simon Martinelli retweeted
Why are you still using pull requests?
Is it for code review?
If so, do you really think your or your colleagues catch bugs and mistakes that an Opus 5.5 or Fable or Astra won't find? You can literally spawn all three of them and have them check four times each.
(Also, don't tell me you don't have a "stamp plz" Slack channel or group chat somewhere.)
Is it for knowledge sharing?
Surely there's better ways for that now than the PR, no? We have models that can generate explainer videos, presentations, podcasts, games, quizzes, walkthroughs, ... for any piece of code it can reach.
Is CI the reason?
Well ackshually, CI means continuous integration and its original meaning is the *opposite* of having long-lived branches and PRs.
But, leaving that aside, your agents are hopefully already running the tests before they push something, and hopefully they can run as long as they want and don't block you so they can run the whole test suite and generate "irrefutable proof" and end-to-end demo videos and so on... And so they run the tests and confirm and then you push to a branch and everything runs again and then you merge and then it runs again? That doesn't make sense, does it?
Maybe you work in open source and you accept contributions, in which case I can't speak to the value of pull requests. It's been 2 years since my last OSS contribution. But from what I heard, the time of the PR is coming to an end in OSS too?
I honestly don't get why people still stick to PRs.
With agents you can now move 10x faster, you can finally do real continuous integration, and get more confidence in the changes the agent made.
Don't slow yourself down by having all the changes pile up in a PR.