spec-editor Pro is in early access. Request access

Documentation

Start with the quick start, read the concepts once, and keep the reference at hand.

Get started

  • QuickstartInstall spec-editor from the GitHub repository, create a project and a first requirement, validate it, view it, export it and connect an agent over MCP.

Concepts

  • ConceptsThe ideas behind spec-editor - elements, the folder tree, statuses, acceptance criteria, sources, code links, methodology as data, and the two axes of the interface.

spec-editor Pro

  • spec-editor ProWhat the paid plugin adds to the open core - a delivery team of roles, review stages, test stands, cost control and breakpoints - and how to ask for early access.

Editors

  • EditorsWhat the VS Code, JetBrains and Zed extensions of spec-editor do, and how to install each one from the repository.

Reference

  • CLI referenceAll 33 commands of the spec-editor command line: 26 in the open core and 7 more with spec-editor Pro.
  • MCP referenceThe 116 tools of the spec-editor MCP server in 15 groups: 72 in the open core, 44 more with spec-editor Pro.

Help

  • FAQShort answers about privacy, models, what is free and what is paid, how spec-editor differs from an AGENTS.md file or a spec kit, and where data lives.
  • ChangelogWhat the changelog of the spec-editor open core says, release by release, and where it stops.