Post

We have reached a moment where instead of releasing software you simply release the detailed spec for software and tell people to prompt their agent to build it themselves From the README of OpenAI’s new Symphony orchestrator: github.com/openai/symph...

Maggie Appleton

@maggieappleton.com

5 Mar

The spec is really good - detailed, comprehensive: github.com/openai/symph... Implementations are now easy. Writing excellent specifications becomes the core skill.

This is gathering chatter so I need to clarify: neither openAI nor I is suggesting everyone prompts their own version. Obvs wasteful. Theres a canonical implementation! The important line is “in your programming language of choice”. Where lang could be any number of design prefs and variables.

Maggie Appleton

@maggieappleton.com

IF you want to adapt software to fit your needs, run in your pref lang, change the architectural decisions, etc. rather than forking and editing source code, you can adjust at a higher level. Specs are a concise, directionally correct design ref with less complexity than the implementation code.

5/3/26, 7:49 pm0 reposts5 likes

Sam Rose

@samwho.dev

5 Mar

I like the idea conceptually, have you tried it in practice? I’m a bit concerned at how well a spec will actually be followed, especially as it increases in size and complexity.

Stork

@eightxeroxedbutts.bsky.social

6 Mar

Fred "the documentation is the spec" Brooks could get the test of all tests, seeing if System/360 can be generated from its docs. Also a test of the AI, I s'pose.