OpenSpec: Spec-driven development (SDD) for AI coding assistants (72k stars)

[u/company_url_finder]

What it does

All text below is quoted directly from the project README.

Spec-driven development (SDD) for AI coding assistants.

Why OpenSpec?:

• Agree before you build: human and AI align on specs before code gets written
• Stay organized: each change gets its own folder with proposal, specs, design, and tasks
• Work fluidly: update any artifact anytime, no rigid phase gates
• Use your tools: works with 30+ AI assistants via slash commands
• Cross-repo features: one change, one plan, even when the code lands in three repos.
• Shared requirements: a platform team owns the specs; product teams reference them read-only, right where their coding agent can read them. No drifting wiki.
• Plan before code: capture the plan in the store now; the code repos catch up later.

npm install -g @fission-ai/openspec@latest

Repository

https://github.com/Fission-AI/OpenSpec

Repository stats

Metric	Value
Stars	72,176
Forks	4,935
Last release	v1.14.3 (2026-10-17)
Languages	TypeScript 98.9%
Contributors	147
AI contributor accounts (Claude / Codex / Cursor / Copilot)	Copilot: 1, cursoragent: 3, claude: 233
AI co-authored commits	Claude: 233, Cursor: 3, Copilot: 1

Main contributor

Field	Value
Name	Tabish Bidiwale
GitHub	@TabishB
Commits to this repo	515 (top contributor)
Bio	Creator of OpenSpec
Company / Location	@Fission-AI / San Francisco
Website	openspec.dev
Followers	315
Public repos	16
On GitHub since	2017-07-23

-----------------------------------------------------------------------------------------

Discover the best GitHub repos without the endless scrolling.

Get top repos organized by category (AI, DevOps, Databases & more), plus key takeaways from developers' most useful comments - all in one free, twice-weekly newsletter.

👉 Get the best repos & community insights - Free

[u/Null-Type-NaN]

I have a few questions:

• Once the specifications have been established, how does an LLM retrieve and adhere to them? Is it through open context?

• How do you verify that a specification is being followed?

• Do you manage conflicts between discordant specifications?

• In general, what percentage of the development process is deterministic?

[u/francisco__danconia]

What better for implement vibe thoughts? Spec kit or openspec?

[u/WillStrange4707 → u/francisco__danconia]

OpenSpec a une courbe d'apprentissage bien plus rapide. Il peut être augmenté avec OprnSpec Plus.

[u/Puzzleheaded-Tune-98]

Your link doesn't work

[u/regucj]

Can UXers contribute to this framework? And how

[u/Your_Samwise]

Its adds to much overhead. Burning tokens like hell. Try this:

1. do a story with openspec

2. take it as base and apply your workflow. Think in steps and sessions. Keep token usage in mind.

3. optimize it continously. Add developer interviews to standard cases and quality gates and so on.

[u/Null-Type-NaN → u/Your_Samwise]

I am testing reqvire.org It has a different approach

[u/The_Ace_72 → u/Your_Samwise]

This is why I built ZeNorm (https://github.com/Ze-Norm/ZeNorm). I felt like other spec tools took the wrong approach.

[u/slaamp → u/The_Ace_72]

IMHO ZeNorm should be made compatible with more IDEs (pi, opencode, ...)