fission-ai/openspec

README EXCERPT

The most loved spec framework. Our philosophy: [!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 Follow @0xTab on X for updates · Join the OpenSpec Discord for help and questions. See it in action What do the specs actually look like? Plain Markdown — requirements with concrete scenarios, no special syntax to learn. Here's what goes in the specs/ folder created above: Your AI writes these; you review the plan before any code is written. OpenSpec is built with OpenSpec — browse this repo's live specs and in-flight changes for real examples at scale. OpenSpec Dashboard Why teams adopt OpenSpec Solo, OpenSpec keeps you and your AI honest on a single repo. On a team, the hard part moves: a feature spans the API server, the web app, and a shared library; requirements are owned by one team and consumed by others; planning starts before any code exists. Stores are the answer — planning in a repo of its own. The same openspec/ shape you already know (specs and changes), shared by git push like anything else. One source of truth your whole team and every coding agent can read, across…

The opening of the GitHub README as stored, at most 1,200 characters. Markdown is not rendered.