EN
Back to the archive

The archive · Developer & Business Tools · Product decision · 2025–2026

OpenSpec: the spec-driven bet that coding agents need plans, not prompts

YC W26 startup OpenSpec bets AI coding fails from underspecification; its open-source spec framework hit 27k+ GitHub stars in under six months.

OpenSpec (Fission AI)

The betThat underspecification, not model quality, is AI coding's bottleneck — so OpenSpec built an open-source spec layer where agents and humans agree before code.Live

What the business is

OpenSpec is an open-source spec-driven development (SDD) framework: an openspec/ folder with a spec library and a changes system (proposal, design, tasks, spec deltas) that AI coding assistants read and update via slash commands, with integrations for 30+ tools.

Starting capitalYC W26; ROSS Index lists Y Combinator as investor (amount undisclosed).

How it started

Tabish Bidiwale, a former team lead at a quantum computing startup, saw that managing coding agents is like managing a team: things break when there's no alignment on what is being built and why. He founded OpenSpec (Fission AI) in Sydney in 2025 and built a spec framework that captures what, why and how before the agent writes code, with integrations for Claude Code, Cursor, Windsurf and Copilot.

What happened

The repo went viral in the AI-coding community: the ROSS Index logged 18.5x star growth in Q1 2026 (18.5K stars by 2026-01-21), and by YC's W26 launch (2026-08-23) OpenSpec reported 27k+ stars in under six months. Y Combinator backed the company; OpenSpec rebuilt its workflow around artifact-guided proposals (/opsx:propose) and opened Stores for team and multi-repo planning in beta.

How it ended up

Still running and scaling: the repo is live and maintained under MIT with 30+ tool integrations, and team Stores/Workspaces are in beta; no revenue model, shutdown or sale reported as of 2026-09-02.

Background

OpenSpec is an open-source spec-driven development (SDD) framework from Sydney startup Fission AI: it adds an openspec/ folder to a codebase with a spec library (living documentation of how the system works) and a changes system (proposal, design, implementation tasks and spec deltas per feature). Everything is Markdown, checked into Git, and readable by AI coding assistants from Claude Code and Cursor to Copilot.

The bet is that the bottleneck in AI-assisted development is underspecification, not model quality: code is cheap now, but correctness is expensive because agents don't reliably know what was wanted. OpenSpec makes humans and agents agree on what, why and how before any code is written, pushing teams from code review toward plan review.

The repo went viral: ROSS Index logged 18.5x star growth in Q1 2026, and by YC W26's launch (2026-08-23) OpenSpec reported 27k+ GitHub stars in under six months. Y Combinator backed the company, and OpenSpec kept shipping — an artifact-guided workflow (/opsx:propose), 30+ tool integrations, and Stores for team/multi-repo planning in beta.

The company is still early and tiny — founder Tabish Bidiwale built it from a team-lead insight at a quantum computing startup — but the open-source repo has become the distribution channel, with Fondo and YC's launch page repeating the same 27k-star traction figure in 2026.

What has to be true

  • Agents are powerful but unpredictable when requirements live only in chat history; specs persist across sessions.
  • Specs are cheap to write and review compared with diffs, so teams shift from code review to plan review.
  • Git-native Markdown works everywhere — no new platform, no lock-in — which is why adoption spread across 30+ tools.
  • A viral open-source repo gave a tiny startup distribution that a sales team could not have bought.

What can be applied

In AI coding the scarce skill is specifying intent, not writing code: a git-native spec layer rides the agent wave on 'plan review beats code review,' and a viral OSS repo substitutes for sales.

Aftermath

As of 2026-09-02, OpenSpec is live and actively maintained: the Fission-AI/OpenSpec repo (MIT license) continues to grow, the CLI and slash-command workflows work across 30+ AI assistants, and the team is building Stores/Workspaces for team and multi-repo planning in beta. The company remains YC W26-backed with no reported revenue model, shutdown or acquisition; its traction claim of 27k+ stars in under six months stood at the YC launch on 2026-08-23.

Sources

spotted an error? The archive wants to know.

Your turn

You just read one. Describe what you are building, and see who is betting on the same thing.

Free account · 3 free questions · no card

Related cases