Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
OpenSpec
Lightweight, brownfield-first spec layer: each change gets proposal/specs/design/tasks; archiving merges spec deltas into living specs. Works with 30+ assistants; 'Stores' share specs across repos.
v1.15.0 released 2026-10-24; repo pushed 2026-10-24; ~73k stars (checked 2026-10-25)
In Spec-driven development
Where it stands apart
- How is it mainly sustained? company or startup with a free product (no revenue yet) (0% of 18 others)
- After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) a step folds changes back into the specs (17% of 18 others)
- What format are specs written in? markdown with a required requirement syntax (e.g. EARS, SHALL/WHEN scenarios) (17% of 18 others)
- What does it offer teams beyond sharing files in git? (if both, pick the paid product) team features in the open-source tool (shared spec stores, multi-developer or multi-agent coordination) (11% of 18 others)
What it shares with most of the community
- Is it actively maintained? active (74% of 19 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (74% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (74% of 19 others)
- Who is it for? developers (100% of 19 others)
- Where do specs live? plain files in the project repository (89% of 19 others)
- Which coding agents does it work with? many agents (five or more) (78% of 18 others)
- By default, once a plan is approved, how is implementation run? the human drives it, phase by phase or task by task (50% of 18 others)
Nearest neighbors
- BMAD Method 71% of 17 shared answers match
- Agent OS 65% of 17 shared answers match
- GitHub Spec Kit 65% of 17 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT | source 2026-10-25 |
| How is it mainly sustained? | stands apart company or startup with a free product (no revenue yet) Fission AI company; MIT free tool, hosted Cloud Agent in paused early access, no pricing published. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes | source 2026-10-25 |
| Do you need an account to use it? | no account npm/brew CLI; no sign-up (anonymous opt-out telemetry only). | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Own proposal/specs/delta format; slash commands generated for 30+ tools. | source 2026-10-26 |
| Once code exists, what is the spec? | a living document kept current alongside the code /opsx:archive: 'Specs updated'; repo dogfoods live specs. | source 2026-10-25 |
| After implementation, what built-in step keeps specs and code aligned? (if several, the first that applies) | stands apart a step folds changes back into the specs Change deltas (ADDED/MODIFIED requirements) merge into openspec/specs on archive. | source 2026-10-25 |
| What format are specs written in? | stands apart markdown with a required requirement syntax (e.g. EARS, SHALL/WHEN scenarios) 'Plain Markdown' but structured: Requirement blocks with SHALL, Scenarios with WHEN/THEN, delta headers. | source 2026-10-25 |
| Where do specs live? | plain files in the project repository openspec/ folder, or a separate store repo. | source 2026-10-25 |
| Which coding agents does it work with? | many agents (five or more) | source 2026-10-25 |
| What form does it mainly ship in? | prompts, skills, or slash commands installed into an agent (even if a CLI installs them) Workflow is skills/slash commands installed into the agent; CLI mainly installs and supports them. | source 2026-10-26 |
| How is the path from idea to code structured? | no fixed phases 'fluid not rigid'; 'update any artifact anytime, no rigid phase gates'. | source 2026-10-25 |
| Does a human approve the spec or plan before code is written? | review is recommended but not enforced 'you review the plan before any code is written' - encouraged, not enforced. | source 2026-10-25 |
| By default, once a plan is approved, how is implementation run? | the human drives it, phase by phase or task by task /opsx:apply runs the tasks; user drives propose/apply/verify/archive. | source 2026-10-25 |
| What does it offer teams beyond sharing files in git? (if both, pick the paid product) | stands apart team features in the open-source tool (shared spec stores, multi-developer or multi-agent coordination) Stores (beta): planning repo shared across code repos. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/Fission-AI/OpenSpec · read 2026-10-25
- GitHub · github.com/Fission-AI/OpenSpec/releases · read 2026-10-25
- Web page · openspec.dev · read 2026-10-25
- Web page · openspec.dev/docs/stores · read 2026-10-25
- Web page · openspec.dev/docs/supported-tools · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.