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.
๐ https://t.co/Pb7hkPXmTa
#SpecDrivenDevelopment #AIUnifiedProcess #GenerativeAI #KeepITSimple
@brunoborges The solution is simple: proper funding for open source projects. But as long as companies are making money with open source and not contributing back we will keep seeing such problems. In house is not more secure than open source. In contrary.
@asm0di0@alina_yurenko Yes, this is the "modern" version. It runs on either electricity or gas. That's what you see all over Switzerland. The one with fire is much more archaic.
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
๐ https://t.co/sGjWSjo5E5
๐ 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: https://t.co/6mT3kzfWjI
#AIUnifiedProcess #SpecDrivenDevelopment #ClaudeCode #SoftwareArchitecture #AI
@nikosvg Those are all architectural decisions that come from the non functional requirements. This is not part of the example. The example is about the functional requirements.
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...