66IDEAS publishes open-source software specifications - complete, buildable definitions of functionality, UX, and architecture - together with working reference implementations that prove each one.
Everybody can ask an agent to build software today. What is scarce is the idea - and the thought-through design behind truly great products. That is what you find here: the specification is the product; the code is the proof.
Functionality, UX, and architecture - complete enough that a human team or an AI agent can build the product from it.
Working software built from the spec - on whatever stack proves the point. Specs without proof are wishes.
Build it your way. Take a specification and implement it against your own technology stack - Google Firebase, SAP BTP, Microsoft Azure, or anything else. Or skip the build and run a reference implementation as-is. Everything is MIT-licensed and free.
Every product is a pair: the specification, and the reference implementations built from it. The number in the name is the idea's number.
A complete CRM - sales, service, deal rooms, AI briefings, gamification - fully specified, with four implementations on completely different stacks. Try the live demo in your browser.
A native, read-only Markdown reader for macOS 26 - rich rendering, outline, search, bookmarks, themes, and publication-quality HTML and PDF export. Fully specified, Swift implementation.
A tiling window manager for macOS, driven by the mouse: windows never overlap, drag one onto another to swap or split. No shortcuts to learn, no config file. Fully specified, Swift implementation.
More ideas are queued. Each one ships when it is finished, not before.
Deploy or install a reference implementation. Done.
Hand the specification to your team - or your AI agent - and implement it on the stack you already trust.
Issues are welcome everywhere; pull requests are welcome on the specifications. The reference implementations follow the specs. No CLA, no paperwork.
Design decisions, spec deep-dives, and what building with AI agents actually looks like.
What changes when implementation stops being the scarce resource.
Three CRM systems, two decades - the story behind the name.
Five lessons on what a spec needs so an agent can build from it.