Fetching from the wire…
01
02
03
04
05
06
07
08
OSS2026-06-18 · source-backed
OpenSpec enforces a three-phase state machine, proposal then apply then archive, before any code gets written, turning executable specs into validation gates instead of docs. It works because the spec, not the chat history, becomes the durable source of truth the agent and reviewer share. For agent-written code that has to survive real use, this beats ad-hoc prompting. (Augment Code)
Each link below shares sources, entities, or timing with this story.
OpenSpec supports Windsurf / Shared topic / Tension
Linked by a graph relationship (OpenSpec supports Windsurf); overlapping topics (agent, code); pushes against this story (but).
Linked by a graph relationship (OpenSpec supports Windsurf); overlapping topics (agent, code); pushes against this story (vs).
OpenSpec supports Cursor / Shared topic / Tension
Linked by a graph relationship (OpenSpec supports Cursor); overlapping topics (agent, code); pushes against this story (but).
Linked by a graph relationship (OpenSpec supports Cursor); overlapping topics (agent, code); pushes against this story (but).
OpenSpec supports GitHub Copilot / Shared topic / Tension
Linked by a graph relationship (OpenSpec supports GitHub Copilot); overlapping topics (agent, code); pushes against this story (vs).
Linked by a graph relationship (OpenSpec supports GitHub Copilot); overlapping topics (agent, code); pushes against this story (vs).
OpenSpec supports Cursor / Shared topic
Linked by a graph relationship (OpenSpec supports Cursor); overlapping topics (agent, code, spec).
OpenSpec supports Windsurf / Shared topic
Linked by a graph relationship (OpenSpec supports Windsurf); overlapping topics (agent, chat, code).