Fission-AI/OpenSpec: README-based editorial guide

Fission-AI/OpenSpec describes itself in the README as "Spec-driven development (SDD) for AI coding assistants.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "README", the README says: > [!TIP] > New workflow now available! We've rebuilt OpenSpec with a new artifact-guided workflow. > > Run /opsx:propose "your idea" to get started. → Learn more here. That establishes the project's stated boundary, not a production test.

The README's "Why teams adopt OpenSpec" section gives a useful starting point for deciding whether the project fits: 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.. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Cross-repo features , one change, one plan, even when the code lands in three repos.. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "See it in action". The source evidence includes: Plain Markdown , requirements with concrete scenarios, no special syntax to learn. Here's what goes in the specs/ folder created above:. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: npm install -g @fission-ai/openspec@latest When the README contains no runnable command, this article does not invent one. Open its "Why teams adopt OpenSpec" section and confirm system dependencies, default ports, and first-run initialization before using a public server.