OpenSpec

“I've recently adopted openspec for one of our repos and it's worked great.”

“I personally like using openspec for this, because it makes the model iteratively ask you architectual decisions”

“I have personally been leaning into spec driven development, which I have found success with.”

“Plan mode is not dead, it just moved to OpenSpec and other similar tools.”

“it is one of the simpler frameworks for SDD, versus eg speckit”

“I like the overall idea of this, but the writing of the spec to me is more like building the thing than the implementation itself”

“The whole point about OpenSpec is that you create a new change, with a new spec, and then the LLM modifies the code accordingly.”

“the OpenSpec change process is super valuable for keeping agents on track”

“The documentation is entirely about how to use it, how to manage the skills and configure it.”

“it changes bit by bit in every meeting and before you know your specs are not aligned”

“I use it at a much smaller scale. I think that's also the right place, because its a CLI tool + skills that generate md files.”

“every change, medium or larger, turns into a large set of multiple markdown documents, each that need review”

“Using OpenSpec keeps things as constrained as possible with the side effect of recording what your system does.”

“I think it has the most sane ceremony and its model fits my mental model really well.”

“it can validate the shape without having to spend tokens reading the files”

“All the docs here are the templates rather than the actual file”

“It works fairly well, and it is definitely less heavy than SpecKit.”

“I like it because it explicitly captures my reasoning in the documents it produces”

“to be useful for raising my interface to projects up a layer of abstraction”

“having the intent develop alongside the code in the repository seems to have ensured that agents have a more holistic view of the project”

“Every time I look at those spec files it's somehow exhausting.”

“find the more time I put iterating/scrutinizing the spec artifacts before I let the agent implement the better understanding I have and the better results I get”

“the Workflow is not too heavy while execution still churning good result given the spec is done well”

“I've only exceptionally rarely seen claude do something wrong based on spec docs when it's fully spec'd out.”

“I enjoy the OpenSpec format but I think maintaining the main specs is not worth it.”

“I use open spec to negotiate requirements before the handoff, it's helped me a lot.”

“I'm experimenting with openspec with my team now on a brownfield project and have some good results.”

“I use openspec to create context and a sequential task list that I feed to ralph loops”

“I like openspec, it lets you tune the workflow to your liking and doesn’t get in the way.”

“for small things it does work for me, but there is still something left for LLMs to truly capture major issues”

“One of my frustration with openspec is the number of files that are generated from the proposal”

“they can also largely be mitigated by using frameworks such as Openspec or Spec-Kit”

“Strangely, taking the time to lay out the steps in a large task helps immensely.”

“You work high level, create a spec and break it down into beads (small tasks).”

“If you want a system that actually stays stable, use OpenSpec”

“As soon as the project grows to 'relevant' size of complexity, maintaining specs is just as hard as whatever other methodology offers.”

“I find it works far better to have a proposal and a list of tasks the ai stays more focused.”

“It uses deterministic AST parsing and static analysis for the core spec generation.”

“With a more disciplined way of creating and persisting locally the specs for the work”

“Works pretty great for me, especially Spec-driven development using OpenSpec”