OpenAI Symphony blurs spec, code

The hot take lands: “spec-first” only feels cheaper until the spec becomes the real implementation contract, at which point you’ve just moved the complexity into a more brittle document. The post is especially convincing when it shows how these specs drift into pseudocode, hard-coded schemas, and brittle edge-case prose.

• –Precise agent instructions collapse into code-like artifacts because ambiguity is what breaks automation
• –Symphony’s SPEC.md is presented as “specification,” but much of it reads like executable pseudocode with extra steps
• –The essay’s strongest point is that verbose specs can still fail in practice, as shown by flaky generation and missing behavior
• –It also calls out the industry tendency to optimize for delivery speed, which produces “spec-shaped” slop instead of careful design
• –For teams building agentic tooling, the real lesson is that better specs demand the same rigor as good code, not less