spec-editor Pro is in early access. Request access

Solutions

For founders and small product teams

Tell your agents what to build in a form that stays true as the product changes.

Who this is for

In your terms

You build a product with a small team and AI agents. The agent forgets what you said last week, and the notes you wrote for it grow until nobody reads them.

You want one place that says what the product does now, and a way to know that a change did what you asked.

Today

What you get today

  • The product described as it is now, one Markdown file per requirement, in your repository next to the code.
  • Acceptance criteria inside each requirement: a command with an expected result, or a check by a judge.
  • A criterion can be marked for a visual check of a screenshot.
  • The MCP server hands your coding agent only the requirements it needs.
  • A web interface to browse the tree, read an element and see the trace map.
  • Free open core under Apache-2.0, installed from GitHub; no external database.
  • Reengineer: restore a model from the code you already have.Pro
  • A delivery team that turns what you write into plans, code and checks.Pro
  • A fast path for one-line edits, and roles that learn from finished runs.Pro
  • Runs on your own Claude Code subscription, without an API key.

Coming soon

What is coming

  • Hosted view of a model coming soon

Next step

Start with the open core

Install the open core, write the first few requirements, and run spec-editor validate. Pro is in early access.