核心亮点

OpenSpec 项目作者 @TabishBidiwale-g6h 评论:

Quote

I should have done a better job showing what sets OpenSpec apart from tools like spec-kit or Kiro (apart from being simple).

Both of those are excellent for 0→1 work, when you are building new features. But as soon as you start modifying existing ones, they become less useful. They do not show the current state of the system or how your change will update it.

That is why OpenSpec separates things into two folders:

/specs/ → the current truth of the system

/changes/ → the proposed updates waiting to be merged

This split is what makes it practical for brownfield projects, not just greenfield ones.


Believe it or not, I actually had an older version of OpenSpec that I never released which was almost exactly what spec-kit is now.

After using it myself for a week, I realized those patterns start to break down once you begin changing existing features instead of just adding new ones.

It gets even worse when those changes span multiple specs or touch cross feature logic. The whole system becomes a lot harder to manage.

That is why I never released that version haha, even though it existed about a month before spec-kit.

OpenSpec 记录系统的现状( /specs 目录),以及正在进行的功能变更( /changes 目录)。

其它