Post

Egor Tarasenko
@dataish.bsky.social

OpenSpec sat in my feed for 4 months. I kept scrolling -- I've watched too many "spec-driven" frameworks become folders nobody opens. Then I had 3 people and an agent in one dbt repo and nobody could say what our models were even supposed to do. So I finally tried it.

openspec.devOpenSpec — A lightweight spec‑driven frameworkOpenSpec is a lightweight, spec‑driven framework for coding agents and CLIs — universal, open source, and no API keys or MCP required.
Egor Tarasenko
@dataish.bsky.social

Simpler than the hype. Two folders in git: specs/ is the truth, changes/ is work in flight like a feature branch. What won me over: spec review is separate from code review. A spec diff shows what behavior changed -- readable in seconds, not a 600-line PR at 2am.

openspec.devOpenSpec — A lightweight spec‑driven frameworkOpenSpec is a lightweight, spec‑driven framework for coding agents and CLIs — universal, open source, and no API keys or MCP required.
Egor Tarasenko
@dataish.bsky.social

The catch: it only knows about changes that go through it. The second a teammate edits a model and merges to main, the spec doesn't move -- your source of truth quietly starts lying. So: how do you handle manual vs agent changes in one repo? openspec.dev

openspec.devOpenSpec — A lightweight spec‑driven frameworkOpenSpec is a lightweight, spec‑driven framework for coding agents and CLIs — universal, open source, and no API keys or MCP required.

0 reposts0 likes

No replies yet.